Skip to content

chore: update release-please manifest to current version 3.2.0#53

Merged
yordis merged 3 commits intomainfrom
fix/release-please-manifest
Feb 23, 2026
Merged

chore: update release-please manifest to current version 3.2.0#53
yordis merged 3 commits intomainfrom
fix/release-please-manifest

Conversation

@yordis
Copy link
Member

@yordis yordis commented Feb 23, 2026

Summary

  • Release-please manifest was stuck at 1.5.0, causing it to generate an incorrect v2.0.0 release PR (chore(main): release 3.3.0 #51)
  • Updates manifest to 3.2.0 to match the actual latest release

After merge

Remove release-type and target-branch from workflow (they're in config). Use @v4 instead of @v4.2.0. Add issues: write permission. This should fix DCO signoff for release PRs.

Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
@cursor
Copy link

cursor bot commented Feb 23, 2026

PR Summary

Low Risk
Only updates release automation metadata; no runtime code or behavior changes.

Overview
Bumps the release-please manifest version in .github/release-please-manifest.json from 1.5.0 to 3.2.0 so automated release PRs/tags reflect the current project version.

Written by Cursor Bugbot for commit a200ac0. This will update automatically on new commits. Configure here.

@coderabbitai
Copy link

coderabbitai bot commented Feb 23, 2026

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 351a518 and a200ac0.

📒 Files selected for processing (1)
  • .github/release-please-manifest.json

Walkthrough

A version number update in the release manifest configuration, incrementing the root package version from 1.5.0 to 3.2.0 to reflect the next release target.

Changes

Cohort / File(s) Summary
Release Configuration
.github/release-please-manifest.json
Updated version mapping for root package from "1.5.0" to "3.2.0".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A version bump, oh what a sight,
From 1.5.0 to 3.2.0, shining bright!
The manifest whispers of progress made,
Another release in the upgrade parade! ✨

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/release-please-manifest

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 and usage tips.

@yordis yordis force-pushed the fix/release-please-manifest branch from daa451f to a6bfb5d Compare February 23, 2026 16:57
@yordis yordis changed the title fix: update release-please manifest to current version 3.2.0 chore: update release-please manifest to current version 3.2.0 Feb 23, 2026
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

@yordis yordis force-pushed the fix/release-please-manifest branch from fb45b3d to 974e672 Compare February 23, 2026 17:00
- Update manifest version from 1.5.0 to 3.2.0
- Remove unnecessary issues:write permission
- Pin release-please-action back to v4.2.0

Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
@yordis yordis force-pushed the fix/release-please-manifest branch from 974e672 to a200ac0 Compare February 23, 2026 17:52
@yordis yordis merged commit f84091a into main Feb 23, 2026
4 of 5 checks passed
@yordis yordis deleted the fix/release-please-manifest branch February 23, 2026 17:52
@coderabbitai coderabbitai bot mentioned this pull request Feb 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant