Repository navigation
✨ (minor) Release libhal/ci with its own semantic_release.yml - #131
Merged
Merged
Conversation
Adds a semantic-release workflow for this repository, so ci releases are cut from commit subjects like every other libhal repository instead of by hand. It calls this repository's semantic_release.yml at the pushed commit, with one line for 5.x from the repository root. Merging this releases 5.25.0, the first release with semantic_release.yml (#129) and the reduced check runs (#130).
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.
Adds
.github/workflows/semantic-release.yml, so libhal/ci is released from commit subjects like the other libhal repositories. Until now, its releases (5.24.4–5.24.6) were created by hand.It calls this repository's own
semantic_release.yml(#129) with one line,{"major": 5, "dir": "."}. It passesci_ref: ${{ github.sha }}so the script runs from the same commit as the workflow.Merging this releases 5.25.0
This PR's title carries
(minor). Since5.24.6, the new reusable workflow (semantic_release.yml, #129) and the reduced check runs (#130) have been added. Neither had a keyword, so this PR supplies it. Running the script on this branch gives:Keep the
(minor)in the squash-merge subject (GitHub uses the PR title by default).Needs
SEMANTIC_RELEASEsecret must be available to this repository (the same personal access token libhal uses). I can't see the org's secrets from here. Without it, the release step fails with a missing-token error and nothing is created, so it's safe to find out on merge.README's internal workflow list now mentions it.