ci(release): install release-please, dependabot groups, stale workflow - #395
Merged
Conversation
|
[hermes] code review (7b63090) hermes: review unavailable — agent-box unreachable or error. Check /home/luk-server/agent-logs/hermes-pr-review-395-20260723-224542.log. Advisory only — not a blocking gate. |
📝 WalkthroughWalkthroughRelease Please automation, Dependabot grouping, and stale pull request handling were configured through repository configuration files and GitHub Actions workflows. ChangesRelease automation
Repository maintenance automation
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/release-please.yml:
- Around line 16-18: Remove the release-type input from the
googleapis/release-please-action step so the workflow uses the existing
release-please-config.json and .release-please-manifest.json in manifest mode;
leave the action reference and other workflow settings unchanged.
In @.github/workflows/stale.yml:
- Around line 8-9: Update the workflow permissions block in stale.yml to include
issues: write alongside the existing pull-requests: write permission, ensuring
actions/stale has both required write permissions.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 55cfc0c7-0d37-49d2-9300-f627ec2ed802
📒 Files selected for processing (5)
.github/dependabot.yml.github/workflows/release-please.yml.github/workflows/stale.yml.release-please-manifest.jsonrelease-please-config.json
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
All reported issues were addressed across 5 files
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
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
1 participant
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.
What
Release automation catch-up, approved by the repo owner:
release-type: simple(shell/infra repo, not an npm package).release-please-config.json+.release-please-manifest.jsonpinned at the current version 2.13.0. Triggers on push tomain.groups: minor-patch(minor+patch batched into one PR, majors stay separate) to all four ecosystems (pip, docker-compose, docker, github-actions) and normalizedopen-pull-requests-limitto 5 everywhere (was 3 for docker/github-actions). Weekly schedule, target-branchrelease, reviewers/labels unchanged.days-before-issue-*: -1), 30 days to stale, 7 days to close, no exempt labels.Operational note (no action taken, per instructions)
release-please works with the default
GITHUB_TOKEN, but two caveats apply to this repo:RELEASE_PLEASE_TOKEN) wired into the workflow'stoken:input. No secret was created here.Notes
workflow-ref-guard(mutable major tags like @v4/@v9 are flagged on PRs).v2.13.0GitHub Release was created separately (catch-up); the changelog entry for 2.13.0 already existed on main via the release-cut commit.Summary by cubic
Automates releases and housekeeping: adds
release-please, groups Dependabot minor/patch bumps, and auto-stales old PRs. This standardizes versioning from 2.13.0 and reduces PR noise.New Features
googleapis/release-please-action@v4workflow in manifest mode on push tomain; includerelease-please-config.json+.release-please-manifest.jsonpinned at 2.13.0; action SHA-pinned; set write perms for contents/issues/PRs.dependabot.yml: group minor/patch forpip,docker-compose,docker, andgithub-actions; set open PR limit to 5.actions/stale@v9workflow for PRs only: stale after 30 days, close after 7; action SHA-pinned; includeissues: writepermission.Migration
GITHUB_TOKENmay not trigger required checks. If blocked, set a PAT secret (e.g.,RELEASE_PLEASE_TOKEN) and pass it via the actiontokeninput.Written for commit 178a040. Summary will update on new commits.
Summary by CodeRabbit
New Features
Chores