Skip to content

ci: migrate to release-please-action v5 - #2

Merged
Spikeysanju merged 1 commit into
mainfrom
ci/release-please-v5
Jul 14, 2026
Merged

ci: migrate to release-please-action v5#2
Spikeysanju merged 1 commit into
mainfrom
ci/release-please-v5

Conversation

@Spikeysanju

Copy link
Copy Markdown
Contributor

Summary

  • Switch google-github-actions/release-please-action@v4googleapis/release-please-action@v5 (active maintainer, Node 24)
  • Add issues: write permission required by current release-please docs
  • Document why publish is skipped when no release is cut
  • Make docs commits user-facing so README changes can produce a patch release

Why publish was skipped

Expected. After PR #1 merged, release-please reported no user-facing commits, so release_created != true and publish correctly no-op'd. No bad publish risk.

GitHub merge commits also aren't conventional commits, and default release-please treats docs: as non-user-facing unless configured.

Test plan

  • CI green on this PR
  • After merge to main, Release workflow uses googleapis/release-please-action@v5 without Node 20 / deprecated-org warnings
  • release-please opens a patch release PR for docs work (or is ready for the next user-facing commit)
  • publish still skipped until a release PR is merged (release_created == true)

Replace deprecated google-github-actions org action (Node 20) with
googleapis/release-please-action@v5 (Node 24). Treat docs commits as
user-facing so README changes can open a patch release PR.
@Spikeysanju Spikeysanju self-assigned this Jul 14, 2026
@Spikeysanju
Spikeysanju merged commit ac6d165 into main Jul 14, 2026
2 checks passed
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