Skip to content

chore: back-merge main after v0.19.1 - #609

Merged
github-actions[bot] merged 2 commits into
developfrom
cursor/backmerge-main-ancestry-4ba5
Aug 25, 2026
Merged

chore: back-merge main after v0.19.1#609
github-actions[bot] merged 2 commits into
developfrom
cursor/backmerge-main-ancestry-4ba5

Conversation

@tomymaritano

Copy link
Copy Markdown
Collaborator

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
  • Documentation update

Topology only. No product or package.json changes.

Checklist

  • I've read CONTRIBUTING.md
  • Tests pass locally (pnpm test) — no code changes
  • Build succeeds (pnpm build) — no code changes
  • 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.

Open in Web Open in Cursor 

tomymaritano and others added 2 commits August 25, 2026 10:25
chore(release): promote 0.20.0
Co-authored-by:  Tomás Maritano <tomymaritano@gmail.com>
@coderabbitai

coderabbitai Bot commented Aug 25, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@tomymaritano
tomymaritano marked this pull request as ready for review August 25, 2026 17:13
@tomymaritano
tomymaritano marked this pull request as ready for review August 25, 2026 17:13
@github-actions
github-actions Bot merged commit c18180a into develop Aug 25, 2026
19 of 20 checks passed
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>&nbsp;<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>&nbsp;</div>

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
@github-actions

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 0.19.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants