Commit ee679bf
fix(deps): restore published peerDependencies and resync lockfile
`yarn install --immutable` failed in CI (`pass-qa`) with YN0028: the
lockfile disagreed with the manifests.
Two defects, both mine:
1. The `yarn up` runs in the earlier commits rewrote `peerDependencies`
across all 11 published packages as a side effect - tightening ranges
like `@convertcom/js-sdk-types: ">=3.11.0"` to `">=4.0.0"` to match
current workspace majors. That is a breaking change for consumers on
older majors, and the exact opposite of what this branch claims: no
published package should change at all here. All 47 peer ranges are
restored to their `main-convert` values.
2. The lockfile was left internally inconsistent - yarn had rewritten the
`packages/js-sdk` workspace entry's peer ranges but not the other ten,
because it only rewrites entries it re-resolves. Resynced against the
corrected manifests.
Only `devDependencies` differ from `main-convert` now, which is what the
advisory work actually needed.
Verified at this commit:
- `yarn install --immutable` - passes (the CI step that failed)
- `yarn build` at the repo root - 50 bundles, exit 0
- `yarn lint` in packages/js-sdk - clean
- 546 mocha tests across 10 packages - passing
- 47 browser tests - passing
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>1 parent 15633da commit ee679bf
1 file changed
Lines changed: 11 additions & 11 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2397 | 2397 | | |
2398 | 2398 | | |
2399 | 2399 | | |
2400 | | - | |
2401 | | - | |
2402 | | - | |
2403 | | - | |
2404 | | - | |
2405 | | - | |
2406 | | - | |
2407 | | - | |
2408 | | - | |
2409 | | - | |
2410 | | - | |
| 2400 | + | |
| 2401 | + | |
| 2402 | + | |
| 2403 | + | |
| 2404 | + | |
| 2405 | + | |
| 2406 | + | |
| 2407 | + | |
| 2408 | + | |
| 2409 | + | |
| 2410 | + | |
2411 | 2411 | | |
2412 | 2412 | | |
2413 | 2413 | | |
| |||
0 commit comments