Skip to content

revert(CI): restore auto-release tag creation, remove release-please#1568

Merged
TheLastCicada merged 1 commit into
v2-rc2from
revert/restore-auto-release-tag-creation
Apr 7, 2026
Merged

revert(CI): restore auto-release tag creation, remove release-please#1568
TheLastCicada merged 1 commit into
v2-rc2from
revert/restore-auto-release-tag-creation

Conversation

@TheLastCicada

@TheLastCicada TheLastCicada commented Apr 6, 2026

Copy link
Copy Markdown
Contributor

Summary

Why

The core purpose of the auto-release job is to detect when package.json has a version that doesn't yet have a corresponding git tag, then generate the changelog and create the tag — which triggers the downstream build workflow. PR #1567 removed this functionality in favor of release-please-action, but the original npx conventional-changelog-cli approach works without any project devDependencies and without adding a new GitHub Actions dependency.

Test plan

  • CI passes (no runtime code changes)
  • Verify auto-release workflow YAML is syntactically valid
  • Confirm release-please.yml, release-please-config.json, and .release-please-manifest.json are removed

Note

Medium Risk
Moderate risk because it changes the release automation path (tagging/changelog generation and pushes to main), which can impact how and when releases are cut; no runtime application code is touched.

Overview
Restores the auto-release.yml workflow to auto-create a git tag and regenerate CHANGELOG.md when package.json’s version has no matching tag, then pushes the tag (and the changelog commit) to trigger the existing tag-based release pipeline.

Removes the release-please setup (.github/workflows/release-please.yml, release-please-config.json, .release-please-manifest.json), reverting away from googleapis/release-please-action and keeping dependency updates on develop as part of the post-release workflow.

Reviewed by Cursor Bugbot for commit 010c734. Bugbot is set up for automated code reviews on this repo. Configure here.

The auto-release workflow's primary purpose is to compare the version
in package.json to existing tags and create a tag + changelog when the
version is new. PR #1567 removed this core functionality in favor of
release-please-action, which adds an unnecessary external dependency.

The original approach using npx conventional-changelog-cli works fine
and doesn't require any project devDependencies (npx downloads it
on-the-fly in CI). The commit-and-tag-version devDep removal from
#1567 is intentionally kept since the auto-release workflow never
used it — it only resolves the handlebars vulnerability from #1562.

Reverts: auto-release.yml changes from #1567
Removes: release-please.yml, release-please-config.json,
         .release-please-manifest.json
@TheLastCicada TheLastCicada merged commit c235605 into v2-rc2 Apr 7, 2026
34 of 36 checks passed
@TheLastCicada TheLastCicada deleted the revert/restore-auto-release-tag-creation branch April 7, 2026 16:40
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