-
Notifications
You must be signed in to change notification settings - Fork 0
chore(main): release 3.0.7 #29
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
base: main
Are you sure you want to change the base?
Conversation
4563ead
to
895ffac
Compare
WalkthroughAdds a new changelog entry for v3.0.7 (2025-08-25) noting a bug fix: dependency update to googleapis/release-please-action v4.3.0 (refs #28, commit a52cee5). Only additions; no deletions or public API changes. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested labels
Suggested reviewers
Poem
Tip 🔌 Remote MCP (Model Context Protocol) integration is now available!Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats. ✨ Finishing Touches🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 1
🧹 Nitpick comments (1)
CHANGELOG.md (1)
8-8
: Optional: include an upstream release link for quick context.Consider appending a link to the upstream action’s v4.3.0 release/tag for readers skimming the changelog.
Suggested edit:
-* **deps:** update googleapis/release-please-action action to v4.3.0 ([#28](https://github.com/mykso/setup-action/issues/28)) ([a52cee5](https://github.com/mykso/setup-action/commit/a52cee52f7ca48a06155421316db643b7882c099)) +* **deps:** update googleapis/release-please-action action to v4.3.0 ([#28](https://github.com/mykso/setup-action/issues/28)) ([a52cee5](https://github.com/mykso/setup-action/commit/a52cee52f7ca48a06155421316db643b7882c099), upstream release: https://github.com/googleapis/release-please-action/releases/tag/v4.3.0)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled
- Linear integration is disabled
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
CHANGELOG.md
(1 hunks)
🔇 Additional comments (1)
CHANGELOG.md (1)
3-9
: LGTM: 3.0.7 changelog entry is consistent and correctly formatted.Date, compare link, section layout, Conventional Commit scope, and cross-links (issue + commit) align with prior entries. Nothing blocking.
@@ -1,5 +1,12 @@ | |||
# Changelog | |||
|
|||
## [3.0.7](https://github.com/mykso/setup-action/compare/v3.0.6...v3.0.7) (2025-08-25) |
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.
💡 Verification agent
🧩 Analysis chain
Verify compare and commit links resolve after tagging.
Release Please sometimes lands the changelog before tags are pushed. After the tag is created, ensure the compare URL and commit link resolve with 200s.
🏁 Script executed:
#!/bin/bash
set -euo pipefail
urls=(
"https://github.com/mykso/setup-action/compare/v3.0.6...v3.0.7"
"https://github.com/mykso/setup-action/commit/a52cee52f7ca48a06155421316db643b7882c099"
)
for u in "${urls[@]}"; do
code="$(curl -s -o /dev/null -w '%{http_code}' "$u")"
echo "$code $u"
done
# Expect 200 for both after the release tag exists.
Length of output: 816
Compare URL returns 404 – v3.0.7 tag not yet available
The compare link in CHANGELOG.md is currently returning 404, indicating that the v3.0.7
tag hasn’t been pushed to GitHub yet, while the commit link is valid.
• CHANGELOG.md (line 3):
- “v3.0.6...v3.0.7” → HTTP 404
- “a52cee52f7ca48a06155421316db643b7882c099” → HTTP 200
Please push the v3.0.7
tag and re-run the verification script to ensure both links resolve with 200s.
🤖 Prompt for AI Agents
In CHANGELOG.md around line 3, the compare URL for v3.0.7 points to
https://github.com/mykso/setup-action/compare/v3.0.6...v3.0.7 which returns 404
because the v3.0.7 tag hasn’t been pushed; push the v3.0.7 Git tag to the
repository (git tag v3.0.7 && git push origin v3.0.7 or create the tag on the
release and push) and then re-run the verification script to confirm the compare
link resolves with HTTP 200.
🤖 I have created a release beep boop
3.0.7 (2025-08-25)
Bug Fixes
This PR was generated with Release Please. See documentation.
Summary by CodeRabbit