Repository navigation
chore: promote develop → main - #138
Merged
Merged
Conversation
chore(release): sync v0.31.0 back to develop
* docs(readme): update download links for v0.31.0 * ci: migrate workflows to tiered arc-k3s runners * ci: trigger CI on tiered runners * ci: use gh api for merge policy labels --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Contributor
Merge methodUse: Create a merge commit ( Warning Using the wrong merge method here can break the release pipeline.
Whydevelop → main promotion must preserve individual Conventional Commits for Release Please. Squashing collapses them into a single chore commit (stalled 0.10.0 after promotes #60/#63). HowDo not use the green merge button. Add the Policy source: |
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.
Release
Promotes
developintomain.Auto-generated by the
release-prworkflow and refreshed on every push todevelop.Merge method
Warning
Do not squash. This PR must land as a merge commit so Release Please can see individual
feat/fixcommits onmain(squashed promotes stalled 0.10.0).How: add the
promotelabel (or run thepromote-mergeworkflow). Do not use the green merge button.Policy:
Tools/Get-PRMergePolicy.ps1·docs/merge-policy.mdOther