Repository navigation
👷 Release v5 and v6 as separate version lines - #113
Merged
Merged
Conversation
Releases 5.x from v5/ and 6.x from v6/ independently, using the shared semantic_release.yml from libhal/ci. It only reads (minor) and (patch) from commit subjects and has no (major) keyword, so the 6.x line starts when a maintainer publishes 6.0.0-alpha.1 by hand. deploy.yml deploys 5.* tags from v5/ and 6.* tags from v6/, and api.yml only builds API docs for 5.* releases. CONTRIBUTING.md now explains how releases are requested.
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
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.
Releases libhal-util's two version lines independently, so v6 can publish pre-releases (
6.0.0-alpha.N) for libhal-arm-mcu v2 while v5 keeps releasing as before.v5/5.x.y, as beforev6/6.0.0-alpha.Nuntil6.0.0existsChanges
semantic-release.ymlnow calls the sharedsemantic_release.ymlfrom libhal/ci (✨ Add semantic_release.yml for per-directory version lines ci#129) with lines 5 and 6:(minor)or(patch)in a commit subject (the PR title, for squash merges) asks for a release, and the highest keyword wins;(major)fails the run, because major versions are started by hand.deploy.yml:5.*tags deployv5/as before.6.*tags deployv6/with LLVM 23 and Conan 2.33.0, uploading with the trunk remote credentials.api.yml: the v5 docs job no longer runs for 6.x releases.CONTRIBUTING.md: a short "Releases" section on(minor)and(patch)in PR titles.No commit under
v5/with a release keyword is waiting since 5.10.0, so merging this won't cut a v5 release. The shared script reports the same.After merging
The 6.x line has no tag yet, so nothing releases from
v6/until a maintainer starts it by hand, e.g. after #110 and #111 merge:After that,
(minor)or(patch)PRs that changev6/cut6.0.0-alpha.2,6.0.0-alpha.3, ...