Our Current Project Automation
Utilizing Azure Pipelines (azure-pipelines.yml) for ci/cd automation, we have a configuration segment dedicated to finalizing the project versioning process before publishing to Azure Artifacts. Our goal is to seamlessly update the existing version number in package.json, all while avoiding unnecessary triggers of new pipelines within Azure DevOps.
The significant excerpt from our azure-pipelines.yml file is outlined below:
- script: |
git config --global user.email "<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="8de8e0ece4e1cde8f5ece0fde1e8a3eee2e0">[email protected]</a>"
git config --global user.name "User name"
npm version patch -m "Bump version to %s [skip ci]" --force
displayName: 'Bump release version'
- script: |
npm pack
displayName: 'Package package'
While this process effectively deploys the package to our Azure Artifacts feed, it falls short when it comes to updating the current version in package.json.
In our package.json, the following setup can be found:
"release": {
"plugins": [
"@semantic-release/commit-analyzer",
"@semantic-release/release-notes-generator",
"@semantic-release/changelog",
[
"@semantic-release/npm",
{
"npmPublish": false
}
],
[
"@semantic-release/git",
{
"assets": [
"dist/",
"package.json",
"CHANGELOG.md"
],
"message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
}
]
]
}
Seeking Assistance
How can we modify the script to ensure that the version attribute in package.json receives an update without initiating a cyclical chain of pipeline executions?