fix: configure semantic-release to auto-publish the 2.x branch#122
Merged
Merged
Conversation
Point the release config and workflow trigger at 2.x so the maintenance line publishes on its own channel. Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Enables semantic-release to auto-publish the
2.xmaintenance line. Previously the release config listed onlymainas a release branch, so a run triggered on2.xwould recognize the branch as unconfigured and skip publishing entirely.This points the
.releasercbranchesentry and the release workflow trigger at2.x. Because the branch is namedN.x, semantic-release classifies it as a maintenance branch with range>=2.0.0 <3.0.0and its own2.xchannel, so it will pick up from the last v2 tag (v2.0.11) and cut the next patch/minor without touching thelatestdist-tag, which continues to come from thereleasebranch.Note that this branch publishes under the pre-rename package name
@edx/frontend-plugin-notifications, which is correct: that is the package the v2.x line has always shipped to, and it is independent of the renamed@openedx/frontend-app-notificationsused by the 3.x line. semantic-release computes versions purely from git tags, so the differing package name does not affect version calculation. Publishing relies on npm trusted publishing, which is configured per package, so the old package needs a trusted-publisher entry for this repo and workflow.The change is committed as a
fix:so merging produces an actualv2.0.12release, validating the pipeline end to end.LLM usage notice
Built with assistance from Claude.