Skip to content

CI: Fix prepare-release version output for shrinkwrap sync#2971

Merged
rebeccahum merged 1 commit into
trunkfrom
ci/fix-version-output
Jul 13, 2026
Merged

CI: Fix prepare-release version output for shrinkwrap sync#2971
rebeccahum merged 1 commit into
trunkfrom
ci/fix-version-output

Conversation

@rebeccahum

Copy link
Copy Markdown
Contributor

Description

https://github.com/Automattic/vip-cli/actions/runs/29278478408/job/86913465276

Silence npm lifecycle banners in the prepare-release workflow so the vip-actions release script captures only the version string from npm version.

The version lifecycle script still syncs npm-shrinkwrap.json, but its npm banner output no longer pollutes the generated release branch name.

@rebeccahum rebeccahum requested a review from Copilot July 13, 2026 19:30
@github-actions

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@sonarqubecloud

Copy link
Copy Markdown

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adjusts the npm-prepare-release GitHub Actions workflow so the release automation can reliably capture only the version string from npm version, avoiding polluted release branch names while still allowing the version lifecycle script to update npm-shrinkwrap.json.

Changes:

  • Sets NPM_CONFIG_LOGLEVEL: silent for the Automattic/vip-actions/npm-prepare-release step to suppress npm lifecycle banner output.
  • Adds inline comments explaining why loglevel is being overridden for this workflow step.

@rebeccahum rebeccahum merged commit 9782aa5 into trunk Jul 13, 2026
21 checks passed
@rebeccahum rebeccahum deleted the ci/fix-version-output branch July 13, 2026 19:33
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.

2 participants