chore: adopt release-branch model for 1.0.0#852
Merged
arbrandes merged 1 commit intoJul 9, 2026
Conversation
Adopt the ADR 0012 release-branch model: publish stable from a long-lived release/frontend-base branch (npm @latest) while the frontend-base dev branch publishes -alpha prereleases to @Alpha. - .releaserc: replace placeholder with the release/frontend-base latest-channel entry; set the frontend-base prerelease channel to alpha - release.yml: trigger on both frontend-base and release/frontend-base - bump @openedx/frontend-base peer dependency to ^1.0.0 (stable) Part of openedx#851 Co-Authored-By: Claude <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## frontend-base #852 +/- ##
================================================
Coverage ? 90.93%
================================================
Files ? 151
Lines ? 1280
Branches ? 273
================================================
Hits ? 1164
Misses ? 111
Partials ? 5 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
This adopts the release-branch model from ADR 0012 (amended in openedx/frontend-base#274) so that this repo can publish its first stable release,
1.0.0, to npm@latest. Part of #851.Today the rewrite publishes
1.0.0-alpha.*to@latest. The target model is that stable is published from a long-livedrelease/frontend-basebranch (npm@latest), while thefrontend-basedev branch publishes-alphaprereleases to@alpha..releasercreplaces theplaceholderentry with therelease/frontend-baselatest-channel entry and sets thefrontend-baseprerelease channel toalpha(without it, semantic-release would default the dist-tag to the branch name and land prereleases on@frontend-base).release.ymlnow triggers on bothfrontend-baseandrelease/frontend-base. The@openedx/frontend-basepeer dependency is bumped from^1.0.0-alphato^1.0.0, the released stable.The
release/frontend-basebranch has already been cut from the currentfrontend-basetip, so this config can land safely. Once merged,release/frontend-basewill be fast-forwarded up tofrontend-baseto publish1.0.0to@latest.LLM usage notice
Built with assistance from Claude models (mostly Opus 4.8).