Skip to content

fix(ci): regenerate package-lock.json in update-pp-dev workflow - #238

Merged
sergak01 merged 2 commits into
mainfrom
develop
Aug 12, 2026
Merged

fix(ci): regenerate package-lock.json in update-pp-dev workflow#238
sergak01 merged 2 commits into
mainfrom
develop

Conversation

@sergak01

@sergak01 sergak01 commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Summary

update-pp-dev.yml bumps @metricinsights/pp-dev in the root package.json and every template-*/package.json, but never refreshed package-lock.json afterwards — so its automated PRs left the lockfile out of sync with the manifest. Since ci.yml runs npm ci (which fails hard on any lockfile/manifest mismatch), those auto-generated PRs would fail CI.

Fix

Added an npm install --package-lock-only step right after the version bump, so package-lock.json is regenerated and included in the PR the workflow opens.

Included commits

3a1d49c fix(ci): regenerate package-lock.json in update-pp-dev workflow
593bb18 chore(release): 1.1.3-beta.3 [skip ci]

Merge Request: origin/developorigin/main

Summary by CodeRabbit

  • Release

    • Published version 1.1.3-beta.3.
    • Improved package update handling to keep dependency lock information synchronized automatically.
  • Documentation

    • Added changelog details for the 1.1.3-beta.3 release.

sergak01 and others added 2 commits August 12, 2026 15:48
The workflow bumped @metricinsights/pp-dev in every package.json but never
refreshed package-lock.json, so its automated PRs left the lockfile out of
sync with the manifest and would fail npm ci in CI.
@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 42535642-6c47-44b6-ab8c-67bf179889a2

📥 Commits

Reviewing files that changed from the base of the PR and between d380dad and 593bb18.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (3)
  • .github/workflows/update-pp-dev.yml
  • CHANGELOG.md
  • package.json

📝 Walkthrough

Walkthrough

The update workflow now regenerates package-lock.json when it detects a newer @metricinsights/pp-dev version. The package version advances to 1.1.3-beta.3, with a matching changelog entry.

Changes

PP Dev lockfile release

Layer / File(s) Summary
Conditional lockfile regeneration
.github/workflows/update-pp-dev.yml
The workflow regenerates only package-lock.json with the detected dependency version before creating the pull request.
Version and changelog update
package.json, CHANGELOG.md
The package version changes to 1.1.3-beta.3. The changelog records the workflow fix.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

Suggested reviewers: semantic-release-bot, michailozdemir, maksymovvolodymyr

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main CI workflow change: regenerating package-lock.json in update-pp-dev.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch develop

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sergak01
sergak01 merged commit bf34c31 into main Aug 12, 2026
1 check 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.

3 participants