chore: back-merge main after v0.19.1 - #608
Merged
Merged
Conversation
chore(release): promote 0.20.0
Co-authored-by: Tomás Maritano <tomymaritano@gmail.com>
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
tomymaritano
marked this pull request as ready for review
August 25, 2026 17:08
tomymaritano
marked this pull request as ready for review
August 25, 2026 17:08
8 tasks
github-actions Bot
pushed a commit
that referenced
this pull request
Aug 25, 2026
<!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Summary #608 was squash-merged by auto-merge, so `e8bea28` (`v0.19.1`) is still **not** an ancestor of `develop`. This PR is a real merge commit (`eaa3405` parents: `cbf0e5b` + `e8bea28`). **Merge commit only. Do not squash.** Squashing this PR would fail the same way #608 did. ## Type of Change - [ ] Bug fix - [ ] New feature - [ ] Breaking change - [x] Documentation update Topology only. No product or `package.json` changes. ## Checklist - [x] I've read [CONTRIBUTING.md](../CONTRIBUTING.md) - [ ] Tests pass locally (`pnpm test`) — no code changes - [ ] Build succeeds (`pnpm build`) — no code changes - [x] PR targets `develop` branch (not `main`) ## Merge instructions `gh pr merge --merge` (merge commit). After merge, `git merge-base --is-ancestor e8bea28 origin/develop` must be true. <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-7ed11e95-3857-4f12-bd9c-e1fd773d4ba5?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-7ed11e95-3857-4f12-bd9c-e1fd773d4ba5&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com>
8 tasks
github-actions Bot
pushed a commit
that referenced
this pull request
Aug 25, 2026
<!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Summary Release back-merges must be **merge commits** so `main` becomes an ancestor of `develop`. Auto-merge only skipped `chore/backmerge-*`. Cloud Agent branches have to use `cursor/`, so #608 and #609 were squash-merged and `e8bea28` (`v0.19.1`) is still missing from `develop`. Skip `cursor/backmerge-*` the same way. ## Type of Change - [x] Bug fix - [ ] New feature - [ ] Breaking change - [ ] Documentation update ## Checklist - [x] I've read [CONTRIBUTING.md](../CONTRIBUTING.md) - [ ] Tests pass locally (`pnpm test`) — workflow YAML only - [ ] Build succeeds (`pnpm build`) — not required - [x] PR targets `develop` branch (not `main`) Squash-merge is correct for this PR. <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-7ed11e95-3857-4f12-bd9c-e1fd773d4ba5?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-7ed11e95-3857-4f12-bd9c-e1fd773d4ba5&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div> Co-authored-by: Cursor Agent <cursoragent@cursor.com>
8 tasks
Contributor
|
🎉 This PR is included in version 0.19.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Summary
sync-developwas skipped when Build & Publish failed to undraft v0.19.1.main(e8bea28, tag v0.19.1) is not an ancestor ofdevelop, so the next promote would sit at BEHIND.This PR merge-commits
mainintodevelop. Merge commit only. Do not squash. A squash replays the content as a new commit and does not establish ancestry.Type of Change
Not a product change — topology only (
chore(release): merge main into develop).Related Issues
Follow-up after v0.19.1 publish. PR #607 (publish-by-id) is already on develop.
Checklist
pnpm test) — no code changespnpm build) — no code changesdevelopbranch (notmain)Merge instructions
Use a merge commit (
gh pr merge --merge). Do not squash. After merge,git merge-base --is-ancestor e8bea28 origin/developmust be true.