Skip to content

feat: add monthly dependency release workflow#61

Merged
amcheste merged 2 commits into
developfrom
feat/monthly-dependency-release
Apr 3, 2026
Merged

feat: add monthly dependency release workflow#61
amcheste merged 2 commits into
developfrom
feat/monthly-dependency-release

Conversation

@amcheste
Copy link
Copy Markdown
Owner

@amcheste amcheste commented Apr 3, 2026

Summary

Adds a scheduled workflow that automatically opens a patch release PR on the 1st of each month when Dependabot has merged dependency updates to develop since the last tag.

How it works

  1. Detects chore: bump commits on develop since the last tag
  2. Skips if there's nothing to release, or if a release PR is already open
  3. Runs scripts/bump-version.sh patch — handles VERSION + CHANGELOG atomically, then deletes the local tag it creates (tagging happens later, after the develop→main PR merges)
  4. Opens a chore/release-vX.Y.Z PR to develop with a clear action checklist

What stays manual

Nothing is auto-merged or auto-tagged. After the PR opens you:

  1. Review and merge to develop
  2. Run /publish-release (or open the develop→main PR manually)
  3. Push the tag

Note on CI: PRs created by GITHUB_TOKEN don't auto-trigger CI workflows (GitHub security restriction). All dependency changes were individually validated by CI when Dependabot merged them to develop, so this is low risk. Trigger manually if you want a fresh run.

Test plan

  • Trigger manually via workflow_dispatch to verify the dry-run logic (no dep commits since v1.0.0 yet — should output "Nothing to release — skipping")
  • Verify it opens a PR correctly once Dependabot has merged updates

🤖 Generated with Claude Code

Opens a patch release PR automatically on the 1st of each month when
Dependabot has merged dependency updates to develop since the last tag.

Flow:
1. Detects Dependabot "chore: bump" commits since last tag
2. Skips if nothing to release or a release PR already exists
3. Runs bump-version.sh patch (deletes the local tag it creates — tagging
   happens after the develop→main PR merges, not here)
4. Opens a chore/release-vX.Y.Z PR to develop with a clear action checklist

Nothing is auto-merged or auto-tagged — the normal /publish-release review
flow handles the rest after the developer approves.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions github-actions Bot added the ci label Apr 3, 2026
@amcheste amcheste merged commit ae889c1 into develop Apr 3, 2026
7 checks passed
@amcheste amcheste deleted the feat/monthly-dependency-release branch April 3, 2026 01:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant