You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This test run was triggered on the branch, while semantic-release is configured to only publish from master, next, therefore a new version won’t be published.
#2925
We are running semantic release from azure pipelines. The scenario is as below:
We have a main branch where all the developers commit to and prerelease is enabled. The semantic versions generated are in format 4.1.0-beta.5.
For each prod release, we would be cherry-picking the commits and create a new branch that would reside in releases/ folder and would generate the version as: 4.1.0.0.
The problem with this is, that the release branch would change for each prod release, and I am struggling to dynamically pass the branch name to .releaserc.yml.
.releaserc.yml
branches:
name: main
channel: beta
prerelease: beta
name: releases/${nextRelease.channel}
releaseRules:
type: 'revert'
release: 'minor'
type: 'docs'
release: 'patch'
type: 'style'
release: 'patch'
type: 'chore'
release: 'patch'
plugins:
'@semantic-release/commit-analyzer'
'@semantic-release/release-notes-generator'
'@semantic-release/npm'
The message I am getting for semantic release step is:
[12:35:54 PM] [semantic-release] › ℹ Running semantic-release version 19.0.3
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/npm"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/github"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "prepare" from "@semantic-release/npm"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/npm"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/github"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "addChannel" from "@semantic-release/npm"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "addChannel" from "@semantic-release/github"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "success" from "@semantic-release/github"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "fail" from "@semantic-release/github"
[12:35:59 PM] [semantic-release] › ℹ This test run was triggered on the branch releases/<branch_name>, while semantic-release is configured to only publish from master, next, therefore a new version won’t be published.
How can I dynamically pass the branch name (from which azure pipeline was triggered) to .releaserc.yml, as it will change for prod release.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are running semantic release from azure pipelines. The scenario is as below:
main
branch where all the developers commit to and prerelease is enabled. The semantic versions generated are in format4.1.0-beta.5
.releases/
folder and would generate the version as: 4.1.0.0.The problem with this is, that the release branch would change for each prod release, and I am struggling to dynamically pass the branch name to .releaserc.yml.
.releaserc.yml
branches:
channel: beta
prerelease: beta
releaseRules:
release: 'minor'
release: 'patch'
release: 'patch'
release: 'patch'
plugins:
The message I am getting for semantic release step is:
[12:35:54 PM] [semantic-release] › ℹ Running semantic-release version 19.0.3
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/npm"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/github"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "prepare" from "@semantic-release/npm"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/npm"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/github"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "addChannel" from "@semantic-release/npm"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "addChannel" from "@semantic-release/github"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "success" from "@semantic-release/github"
[12:35:55 PM] [semantic-release] › ✔ Loaded plugin "fail" from "@semantic-release/github"
[12:35:59 PM] [semantic-release] › ℹ This test run was triggered on the branch releases/<branch_name>, while semantic-release is configured to only publish from master, next, therefore a new version won’t be published.
How can I dynamically pass the branch name (from which azure pipeline was triggered) to .releaserc.yml, as it will change for prod release.
Beta Was this translation helpful? Give feedback.
All reactions