-
Notifications
You must be signed in to change notification settings - Fork 2
Update release process #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+139
−4
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
03e7f44
fix: downgrade version to 0.3.0 across all package manifests
joaovjo ec311af
fix: use env GITHUB_TOKEN for release-please
joaovjo 0ed41b6
chore: release main
github-actions[bot] d7ed393
Merge pull request #10 from joaovjo/release-please--branches--main
joaovjo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
What are the breaking changes in googleapis/release-please-action v5 compared to v4?💡 Result:
Breaking changes in googleapis/release-please-action v5 compared to v4 are: 1) Node runtime upgrade (v4 → v5) - v5.0.0 includes a breaking change: “upgrade to node24”. [1] - Therefore, if you were relying on the action running on the earlier Node version from v4, you’ll need to ensure your GitHub Actions environment/workflow is compatible with Node 24 (the action itself now targets Node 24). [1] What’s not shown as a “breaking change” for v5 itself (based on the published v5.0.0 release notes) - The v5.0.0 release notes list only the Node 24 upgrade under “⚠ BREAKING CHANGES”. [1] Context: the main breaking changes introduced when moving to v4 (not directly “v5 vs v4”, but helps explain the prior baseline) - v4.0.0 breaking changes included: removing most configuration options in favor of manifest configuration, rewriting in TypeScript, removing the command option in favor of setting release-type and skip-github-release/skip-github-pull-request, and running on Node 20. [2][3] So, the delta from v4 to v5 that is explicitly called out as breaking in the v5 release is the Node 24 upgrade. [1]
Citations:
Ensure Node 24 compatibility for release-please-action v5.
The upgrade from v4.4.1 to v5 introduces a breaking change: v5 requires Node 24 (upgraded from Node 20 in v4). Verify that your GitHub Actions environment and runners support Node 24.
🤖 Prompt for AI Agents