Commit 3eaf9d1
committed
Fix post-release lockfile drift false positive
The coherence gate treated any file change from version-sync.sh as a
version drift error, but version-sync.sh always refreshes the npm
lockfile via 'npm install --package-lock-only'. When optional platform
packages are published to the registry after a release, the next CI run
resolves them in the lockfile (changing from hollow stubs to fully
resolved entries), causing a false drift failure.
Exclude npm/socket-patch/package-lock.json from the drift check since
lockfile changes don't indicate version string drift - they're just npm
re-resolving optional dependencies based on current registry state.1 parent 365924c commit 3eaf9d1
1 file changed
Lines changed: 14 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
79 | 79 | | |
80 | 80 | | |
81 | 81 | | |
82 | | - | |
83 | | - | |
| 82 | + | |
| 83 | + | |
| 84 | + | |
| 85 | + | |
| 86 | + | |
| 87 | + | |
| 88 | + | |
| 89 | + | |
84 | 90 | | |
85 | 91 | | |
86 | 92 | | |
87 | 93 | | |
88 | | - | |
| 94 | + | |
| 95 | + | |
| 96 | + | |
| 97 | + | |
| 98 | + | |
| 99 | + | |
89 | 100 | | |
90 | 101 | | |
91 | 102 | | |
| |||
0 commit comments