Repository navigation
docs: route releases through a PR and tag the merged main commit - #57
Merged
Merged
Conversation
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.
Fix the release skill's step ordering against the actual branch ruleset: direct pushes to main are rejected (hit in both the v0.8.4 and v0.8.5 releases), and tagging before the squash merge points the tag at a pre-merge commit that is not on main.
Changes to
.agents/skills/release/SKILL.md:chore/release-vX.Y.Z, merge after CI incl. release-gate, then align local main via tree-diff + reset).KIMI_HUD_SHOWCASE_CHANNEL=msedgefallback for hosts without Chrome; authorization section now lists PR merging as an external action.Docs-only; no behavior change.