mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-18 16:00:07 +00:00
* fix(aws-lambda): the handler ZIP installs its runtime from a committed lockfile with scripts off build-zip.ts ran `npm install --no-package-lock` in the publish job, so transitive versions floated at release time and any dependency's install script ran beside the release credentials. The ZIP now runs `npm ci --ignore-scripts` from runtime-lock/<source>/package-lock.json (versions and integrity for every package), and the build fails if that lock disagrees with bun.lock instead of falling back to a range or "latest". `bun packages/aws-lambda/scripts/lock-runtime.ts` regenerates it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(aws-lambda): check only direct runtime versions against bun.lock; Renovate refreshes the rest The runtime lock's transitive tree is npm's own resolution, not bun.lock's (modern-tar 0.8.6 there vs 0.8.4 in bun.lock), so the parity claim now covers puppeteer-core and @sparticuz/chromium only. Renovate's weekly lockFileMaintenance refreshes the transitive tree; its direct-version bumps are off for these dirs because those follow bun.lock. — Rames Jusso Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(aws-lambda): keep the maintainer-only lock-runtime script out of the package Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
9 lines
145 B
JSON
9 lines
145 B
JSON
{
|
|
"name": "hyperframes-aws-lambda-bundled",
|
|
"version": "0.0.0",
|
|
"private": true,
|
|
"dependencies": {
|
|
"puppeteer-core": "25.11.0"
|
|
}
|
|
}
|