Skip to content

chore: bump build-time esbuild 0.25.12 → 0.28.1 (clears GHSA-gv7w-rqvm-qjhr) - #4

Merged
dionmcm merged 1 commit into
mainfrom
chore/bump-esbuild-0.28
Jun 15, 2026
Merged

chore: bump build-time esbuild 0.25.12 → 0.28.1 (clears GHSA-gv7w-rqvm-qjhr)#4
dionmcm merged 1 commit into
mainfrom
chore/bump-esbuild-0.28

Conversation

@dionmcm

@dionmcm dionmcm commented Jun 15, 2026

Copy link
Copy Markdown
Member

Summary

Bumps the build-time-only esbuild dependency from 0.25.12 to 0.28.1, clearing advisory GHSA-gv7w-rqvm-qjhr (npm audit now reports 0 vulnerabilities).

Not a shipped-product vulnerability. esbuild is used only by scripts/bundle-ecl-core.mjs to bundle @aehrc/ecl-core for JavaScriptCore at build time — it ships nothing in the app and is not referenced by any Swift code. The exposure is limited to a build machine running with an attacker-controlled npm registry env. This bump is supply-chain hygiene.

Changes

  • scripts/package.json + scripts/package-lock.json: esbuild ^0.28.1
  • Codeagogo/ecl-core-bundle.js: regenerated with the new esbuild
  • CHANGELOG.md: Security entry

Verification

  • npm audit → 0 vulnerabilities
  • Regenerated bundle; all 71 ECLBridgeTests (which exercise the JS bundle) pass

Independent of #3 (branched off main).

🤖 Generated with Claude Code

…m-qjhr)

esbuild is a build-time-only dependency used by scripts/bundle-ecl-core.mjs to
bundle @aehrc/ecl-core for JavaScriptCore. It ships nothing in the app, so the
advisory does not affect end users — but bumping clears `npm audit` (now 0
vulnerabilities) for supply-chain hygiene.

Regenerated Codeagogo/ecl-core-bundle.js with the new esbuild and verified:
all 71 ECLBridgeTests (which exercise the JS bundle) pass.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@dionmcm
dionmcm merged commit 367410a into main Jun 15, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant