fix(ci): pin yarn to 4.10.3 and regenerate lockfile - #381
Merged
Conversation
The yarn.lock on main-convert was bumped to lockfile metadata `version: 9` by a local install with yarn >=4.11. The backend's V1 tracking build runs `yarn install` in immutable mode under yarn 4.10.3 (per `public/js/tracking/package.json` packageManager field), which writes `version: 8` lockfiles — triggering YN0028 and failing staging deploys. Pinning `packageManager: yarn@4.10.3` here makes the toolchain explicit and prevents future drift when contributors run install with a newer yarn. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
DmytroConvert
approved these changes
May 20, 2026
DmytroConvert
approved these changes
May 20, 2026
JosephSamirL
approved these changes
May 20, 2026
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
3 participants
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
Staging deploys for
convertcom/backendare failing on the V1 tracking build because of a lockfile-format mismatch in this submodule.Symptom — backend CI build log:
Root cause — commit
a85ad99("chore: update yarn lock") was generated with yarn >=4.11, which writes lockfile metadataversion: 9. But the backend's V1 tracking build runsyarn installin immutable mode under yarn 4.10.3 (perpublic/js/tracking/package.json'spackageManagerfield), which writesversion: 8. The backend Ant targetbuild_tracking_dist_v1doesgit submodule update --remote javascript-sdk, so it always pullsmain-convertHEAD regardless of the pinned gitlink — meaning this lockfile breaks every backend staging deploy until fixed here.Changes
package.json: add"packageManager": "yarn@4.10.3+sha512..."matching the backend tracking workspace. Locks the toolchain so future installs by any contributor don't silently drift the lockfile version.yarn.lock: regenerated with yarn 4.10.3 (the only diff vs. previous HEAD is__metadata.version: 9→8).Test plan
yarn install --immutable(what CI runs) completes with warnings only — no YN0028build_tracking_dist_v1passes