fix: sync package-lock.json so npm ci (release) succeeds#17
Merged
Conversation
PR #14 added @argos-ci/cli to package.json devDependencies but did not regenerate package-lock.json. The Release workflow (.github/workflows/release.yml) runs 'npm ci', which exits non-zero when the lockfile is out of sync, so semantic-release never ran and no release has been cut since v3.1.0. Regenerate the lockfile to add @argos-ci/cli and its transitive deps. Verified with 'npm ci --dry-run' (exit 0).
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
github-actions Bot
pushed a commit
that referenced
this pull request
Jun 26, 2026
# [3.2.0](v3.1.0...v3.2.0) (2026-06-26) ### Bug Fixes * sync package-lock.json so the release workflow's npm ci succeeds ([#17](#17)) ([8f606b3](8f606b3)), closes [#14](#14) ### Features * actionable HTTP and license-file permission errors ([#16](#16)) ([91523c2](91523c2)) * moonbase_licensing JUCE 8 module with native activation UI ([#14](#14)) ([2c434a6](2c434a6)), closes [hi#contrast](https://github.com/hi/issues/contrast)
|
🎉 This PR is included in version 3.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
1 participant
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.
Problem
The automated release flow has been stuck since
v3.1.0(2026-06-16), even though a releasablefeat:commit (the JUCE module, #14) has been onmainsince 2026-06-25.Root cause: #14 added
@argos-ci/clitopackage.jsondevDependencies but never regeneratedpackage-lock.json. The Release workflow's first step isnpm ci, which hard-fails when the lockfile is out of sync:Since
npm ciexits non-zero,npx semantic-releasenever runs and no version/tag/release is produced.Fix
Regenerate
package-lock.jsonso it's back in sync withpackage.json(adds@argos-ci/cliand its transitive deps). Purely additive: 1807 insertions, 0 deletions,lockfileVersionunchanged.Verification
npm ci --dry-runnow exits 0 with no "Missing ... from lock file" errors.main, the Release workflow should passnpm ciandsemantic-releaseshould cut v3.2.0 (minor bump from the pendingfeat:commit).