Gathering detailed insights and metrics for semantic-release-ado
Gathering detailed insights and metrics for semantic-release-ado
Gathering detailed insights and metrics for semantic-release-ado
Gathering detailed insights and metrics for semantic-release-ado
semantic-release
Automated semver compliant package publishing
@semantic-release/github
semantic-release plugin to publish a GitHub release and comment on released Pull Requests/Issues
@semantic-release/error
errors with more than just a message
@semantic-release/npm
semantic-release plugin to publish a npm package
npm install semantic-release-ado
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
40 Stars
73 Commits
11 Forks
2 Watching
3 Branches
6 Contributors
Updated on 19 Nov 2024
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
-8.8%
2,195
Compared to previous day
Last week
1.8%
11,131
Compared to previous week
Last month
-3.2%
40,467
Compared to previous month
Last year
3.6%
497,968
Compared to previous year
1
Semantic release plugin for automatic builds on Azure DevOps pipelines.
Step | Description |
---|---|
analyzeCommits | If configured to do so, stores the current version as an Azure DevOps pipeline variable. |
verifyRelease | Stores the next version as an Azure DevOps pipeline variable availabe to downstream steps on the job. |
1$ npm install -D semantic-release-ado
The plugin can be configured in the semantic-release configuration file:
YAML
:
1plugins: 2 - @semantic-release-ado"
JSON
:
1{ 2 "plugins": [ 3 "semantic-release-ado", 4 ] 5}
The generated version number will be stored on a variable availabe to downstream steps on the job. By default this variable is named nextRelease, but the name can be configured in the plugin options. The behavior when no new release is available can be configured with setOnlyOnRelease.
Options | Desctiption |
---|---|
varName | Name of the variable that will store the next version. Defaults to nextRelease. |
setOnlyOnRelease | Bool . Determines if the variable with the new version will be set only when a new version is available. If set to false , the next version variable will store the last released version when no new version is available.Defaults to true. |
isOutput | Bool . Determines whether the version will be set as an output variable, so it is available in later stages.Defaults to false. |
The following examples store the generated version number in a variable named version.
YAML
:
1plugins: 2 - - "semantic-release-ado" 3 - varName: "version" 4 setOnlyOnRelease: true 5 isOutput: true #defaults to false
JSON
:
1{ 2 "plugins": [ 3 ["semantic-release-ado", { 4 "varName": "version", 5 "setOnlyOnRelease": true, 6 "isOutput": true //defaults to false 7 }], 8 ] 9}
Using the variable on the seme job:
1jobs: 2- job: Build 3 pool: 4 vmImage: 'vs2017-win2016' 5 steps: 6 7 - script: > 8 npx -p semantic-release 9 -p @semantic-release/git 10 -p semantic-release-ado 11 semantic-release 12 env: { GH_TOKEN: $(GitHubToken) } 13 displayName: 'Semantic release' 14 15 - script: echo $(nextRelease) 16 displayName: 'Show next version'
Below is the configuration for setting isOutput
to true, which will allow the variable to be referenced from other jobs/stages
JSON
:
1{ 2 "plugins": [ 3 ["semantic-release-ado", { 4 "varName": "version", 5 "setOnlyOnRelease": true, 6 "isOutput": true //sets version as output for later use 7 }], 8 ] 9}
1jobs: 2- job: Job1 3 pool: 4 vmImage: 'vs2017-win2016' 5 6 steps: 7 - script: > 8 npx -p semantic-release 9 -p @semantic-release/git 10 -p semantic-release-ado 11 semantic-release 12 env: { GH_TOKEN: $(GitHubToken) } 13 displayName: 'Semantic release' 14 15- job: Job2 16 dependsOn: Job1 17 pool: 18 vmImage: 'vs2017-win2016' 19 variables: 20 versionNumber: $[ dependencies.Job1.outputs['setOutputVar.versionNumber'] ] 21 22 steps: 23 - script: echo $(versionNumber) 24 displayName: 'Show next version'
1stages: 2 - stage: Stage1 3 jobs: 4 - job: Job1 5 pool: 6 vmImage: 'vs2017-win2016' 7 8 steps: 9 - script: > 10 npx -p semantic-release 11 -p @semantic-release/git 12 -p semantic-release-ado 13 semantic-release 14 env: { GH_TOKEN: $(GitHubToken) } 15 name: semantic-release 16 displayName: 'Semantic release' 17 18 - stage: Stage2 19 dependsOn: Stage1 20 #want to make sure variable is set before we continue to run the stage 21 condition: and(succeeded(), ne(dependencies.Stage1.outputs['Job1.semantic-release.version'], '')) 22 jobs: 23 - job: Job2 24 variables: 25 versionNumber: $[ stageDependencies.Stage1.Job1.outputs['semantic-release.version'] ] 26 pool: 27 vmImage: 'vs2017-win2016' 28 variables: 29 versionNumber: 30 steps: 31 - script: echo $(versionNumber) 32 displayName: 'Show next version'
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
3 existing vulnerabilities detected
Details
Reason
Found 2/7 approved changesets -- score normalized to 2
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More