
Research
Malicious npm Packages Impersonate Flashbots SDKs, Targeting Ethereum Wallet Credentials
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
semantic-release-sfdx2
Advanced tools
semantic-release plugin for publishing an SFDX package
This is a fork of https://github.com/leboff/semantic-release-sfdx with the following changes:
You must have SFDX installed and connected to your DevHub (see Authorization in the Salesforce DX Developer Guide).
npm install -D semantic-release-sfdx2
or using yarn:
yarn add -D semantic-release-sfdx2
To enable this plugin, simply add the following to your package.json
or release configuration file.
{
"release": {
"plugins": ["semantic-release-sfdx2"]
}
}
By default this plugin uses the DevHub which is set in your defaultdevhubusername
sfdx config.
To use another DevHub, set the environment variable SFDX_DEFAULTDEVHUBUSERNAME
(see Salesforce CLI Setup Guide).
You can configure the plugin by providing an object instead of a string in the plugins
array, available options are:
codecoverage
- boolean - whether to run tests with code coveragepromote
- boolean - whether to promote the package versioninstallationkey
- string - the installation key for the packageversionCreateWait
- number - the wait time for package version creation. Defaults to 15 minutes.definitionfile
- string - the path to the definition filedevhubusername
- string - the dev hub username, if you wish to override the defaultskipvalidation
- boolean - whether to skip validationskipancestorcheck
- boolean - whether to skip ancestor checkstatic config via package.json
{
"release": {
"plugins": [
[
"semantic-release-sfdx2",
{
"codecoverage": true,
"promote": true,
"installationkey": "mysecretkey"
}
]
]
}
}
dynamic config via release.config.js
module.exports = {
plugins: [
[
'semantic-release-sfdx',
{
codecoverage: process.env.PROMOTE_PACKAGE_VERSION === 'true',
promote: process.env.PROMOTE_PACKAGE_VERSION === 'true',
installationkey: process.env.INSTALLATIONKEY,
},
],
],
}
verifyConditions
To disable the verification of your SFDX project, DevHub and installationkey:
{
"release": {
"plugins": [
"semantic-release-sfdx",
{
"verifyConditions": false
}
]
}
}
Thanks to https://github.com/carlos-cubas/semantic-release-gcp.git for kicking off point
Thanks to https://github.com/leboff/semantic-release-sfdx for creating the original package
FAQs
Set of semantic-release plugins to publish SFDX Package
The npm package semantic-release-sfdx2 receives a total of 7 weekly downloads. As such, semantic-release-sfdx2 popularity was classified as not popular.
We found that semantic-release-sfdx2 demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.