fix: resolve CD pipeline failure and increase release verbosity#17
Merged
fix: resolve CD pipeline failure and increase release verbosity#17
Conversation
The auto-release workflow was failing with "npm error Version not changed" because @release-it/bumper and release-it's built-in npm plugin were both trying to bump package.json, causing a conflict. Changes: - Remove package.json from bumper plugin's `out` array (root cause fix) - Add --verbose flag to all release-it invocations for better debugging - Add "Debug release-it state" step showing version, tags, dry-run output - Switch from GITHUB_TOKEN to GitHub App auth (nsheaps/github-actions) for release workflows, which provides proper permissions for pushing commits, tags, and creating releases - Apply same auth pattern to release-web.yml for gh-pages deploys https://claude.ai/code/session_01CowQd6RG8QZSDocdtEJ2dK
Contributor
Release Version Check
This version will be released automatically when this PR is merged to Changelog preview0.1.0 (2026-03-05)Features
Bug Fixes
Refactoring
Documentation
Tests
CI/CD
Chores
|
Contributor
Preview DeploymentThe web app for this PR has been deployed: Use this to verify the app works correctly, especially for dependency updates. |
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
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.
Summary
npm error Version not changedbecause@release-it/bumperplugin and release-it's built-in npm plugin were both writing topackage.json, causing a double-bump conflict. Removedpackage.jsonfrom the bumperoutarray so only the npm plugin handles the version bump.--verboseflag to allrelease-itinvocations and a new "Debug release-it state" step that logs current version, tags, recent commits, and a dry-run output before the actual release.auto-release.yml,release.yml,release-web.yml) fromsecrets.GITHUB_TOKENto the org's GitHub App auth action (nsheaps/github-actions/.github/actions/github-app-auth), which provides proper permissions for pushing commits, tags, and creating GitHub releases. This mirrors the pattern used innsheaps/github-actionsCI workflows.Files Changed
.release-it.jsonoutarray to prevent double version bump.github/workflows/auto-release.yml.github/workflows/release.yml.github/workflows/release-web.ymlRoot Cause Analysis
The CI logs showed:
This is a known issue when
@release-it/bumperhaspackage.jsonin itsoutarray — the bumper plugin updatespackage.jsonfirst, then when the npm plugin triesnpm version, it finds the version already matches and errors.Prerequisite
The
AUTOMATION_GITHUB_APP_IDandAUTOMATION_GITHUB_APP_PRIVATE_KEYsecrets must be available to this repository (either as repo secrets or inherited from the nsheaps organization). These are already used bynsheaps/github-actionsandnsheaps/.githubrepos.Test Plan
AUTOMATION_GITHUB_APP_IDandAUTOMATION_GITHUB_APP_PRIVATE_KEYsecrets are accessible fromnsheaps/cepthttps://claude.ai/code/session_01CowQd6RG8QZSDocdtEJ2dK