Repository navigation
docs(agents): document the real release procedure and where the cloud tracker is - #1388
Merged
Merged
Conversation
… tracker is - the mandatory main->develop sync PR cannot be merged (merge commits are rejected, squash/rebase drop the -s ours merge, #1381): replace the rule with the per-release 'merge main with the develop side' branch actually used for v0.20.0 - write the release procedure end to end (pre-flight, prep PR, release branch, squash to main, tag after merge, Homebrew tap, production verify) - Cora: a real verdict is required; the job now diffs against the PR base (#1386) - uteke-cloud's tracker is Gitea, the GitHub repo is a stale mirror Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
🔍 Cora AI Code Review✅ No issues found. Code looks good! Review powered by cora-code · BYOK · MIT |
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.
What
AGENTS.md:git merge -s ours origin/mainafter provingmainhas no unique content, squash PR intomain, annotated tag only after the merge, and the post-tag steps (Homebrew tap PR,brew upgrade, crates.io/Docker checks, productionuteke verify);Why
The documented sync cannot be performed: the repository rejects merge commits and
mainonly gets squash commits (#1381 was closed for that reason), so following the old rule was impossible and every release re-derived the real procedure. This writes down what v0.20.0 actually did (#1379, #1380, tagv0.20.0), including the traps hit on the way (tag-before-merge, Cora empty result, Homebrew PR format).Testing
main, tag type and workflow trigger fromrelease.yml, the tracker location from the cloud issue work).-j 2/ disk note comes from the earlier baseline notes, not from a fresh run.