@jcoreio/condition-solano
Advanced tools
semantic-release plugin to check Solano CI environment before publishing.
Verify that semantic-release is running:
| Option | Description | Default |
|---|---|---|
githubToken | Required. The Github token used to authenticate with Travis API. | process.env.GH_TOKEN or process.env.GITHUB_TOKEN |
githubUrl | The GitHub Enterprise endpoint. | process.env.GH_URL or process.env.GITHUB_URL |
githubApiPathPrefix | The GitHub Enterprise API prefix. | process.env.GH_PREFIX or process.env.GITHUB_PREFIX |
The plugin is used by default by semantic-release so no specific configuration is required if githubToken, githubUrl, and githubApiPathPrefix are set via environment variable.
Always run semantic-release in a post_build hook so that it runs after all workers in the build matrix succeed.
nodejs:
version: '8.9'
hooks:
post_build: npm run semantic-release
FAQs
Check Solano CI environment before publishing
We found that @jcoreio/condition-solano 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.
Security News
Socket CEO Feross Aboukhadijeh discusses open source security challenges, including zero-day attacks and supply chain risks, on the Cyber Security Council podcast.
Security News
Research
Socket researchers uncover how threat actors weaponize Out-of-Band Application Security Testing (OAST) techniques across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.
Security News
Research
A malicious npm campaign is targeting Ethereum developers by impersonating Hardhat plugins and the Nomic Foundation, stealing sensitive data like private keys.