CHANGE @W-22462048@ Bump all 10 package versions for republish - #492
Conversation
- engine-api: 0.40.0 → 0.41.0-SNAPSHOT - eslint8-engine: 0.17.0 → 0.18.0-SNAPSHOT - eslint-engine: 0.45.0 → 0.46.0-SNAPSHOT - flow-engine: 0.39.0 → 0.40.0-SNAPSHOT - pmd-engine: 0.44.0 → 0.45.0-SNAPSHOT - regex-engine: 0.38.0 → 0.39.0-SNAPSHOT - retirejs-engine: 0.37.0 → 0.38.0-SNAPSHOT - sfge-engine: 0.23.0 → 0.24.0-SNAPSHOT - core: already at 0.52.0-SNAPSHOT (from PR #491) - apexguru: already at 0.42.0-SNAPSHOT (from PR #491) Updated all engine-api dependencies across packages to 0.41.0-SNAPSHOT (including ENGINE-TEMPLATE). This allows republishing all 10 packages with new versions to fix the broken 0.51.0/0.41.0 publishes that had SNAPSHOT dependency references.
|
Git2Gus App is installed but the |
aruntyagiTutu
left a comment
There was a problem hiding this comment.
The version bumps across the 10 package.json files are internally consistent and match the PR description well. However, package-lock.json was not updated in this PR — it still resolves @salesforce/code-analyzer-engine-api at 0.40.0-SNAPSHOT and @salesforce/code-analyzer-eslint8-engine at 0.17.0-SNAPSHOT (checked the blob on the dev-dependency-update branch directly), while the package.json files now declare 0.41.0-SNAPSHOT / 0.18.0-SNAPSHOT.
This is exactly the class of problem this PR is meant to fix — the description says the previous publish broke because of inconsistent SNAPSHOT dependency references. Merging with a stale lockfile risks the same failure mode: npm ci would resolve workspace packages against versions the lockfile doesn't have, and a fresh install could pull in mismatched or unexpected states.
Please run npm install (or equivalent) to regenerate package-lock.json against the new versions and include it in this PR before merging.
aruntyagiTutu
left a comment
There was a problem hiding this comment.
Lockfile now regenerated and matches all package.json version bumps (engine-api 0.41.0-SNAPSHOT, eslint8-engine 0.18.0-SNAPSHOT propagated everywhere, including ENGINE-TEMPLATE). Approving.
Summary
Bumps all 10 core packages to their next minor versions to allow republishing with correct non-SNAPSHOT dependencies.
Background
Previous publishes of core@0.51.0 and apexguru@0.41.0 contained broken SNAPSHOT dependency references. npm does not allow republishing the same version, so we must bump ALL package versions.
Version Changes
All inter-package engine-api dependencies updated to 0.41.0-SNAPSHOT.
Next Steps
After merge, publish all 10 packages via GitHub Actions workflow.