build(deps): bump esbuild and tsx

[dependabot]

Bumps esbuild to 0.28.1 and updates ancestor dependency tsx. These dependencies need to be updated together.

Updates esbuild from 0.27.3 to 0.28.1

Release notes

Sourced from esbuild's releases.

v0.28.1

• Disallow \ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

  This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \ are no longer allowed.

  Thanks to @​dellalibera for reporting this issue.

• Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

  The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

  Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

  Thanks to @​sondt99 for reporting this issue.

• Avoid inlining using and await using declarations (#4482)

  Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:

  // Original code
  {
    using x = new Resource()
    x.activate()
  }
  // Old output (with --minify)
  new Resource().activate();
  // New output (with --minify)
  {using e=new Resource;e.activate()}

• Fix module evaluation when an error is thrown (#4461, #4467)

  If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.

• Fix some edge cases around the new operator (#4477)

  Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:

  // Original code
  new (foo()`bar`)()
  new (foo()?.bar)()
  // Old output
  new foo()bar();
  new (foo())?.bar();

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.28.1

• Disallow \ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

  This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \ are no longer allowed.

  Thanks to @​dellalibera for reporting this issue.

• Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

  The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

  Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

  Thanks to @​sondt99 for reporting this issue.

• Avoid inlining using and await using declarations (#4482)

  Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:

  // Original code
  {
    using x = new Resource()
    x.activate()
  }
  // Old output (with --minify)
  new Resource().activate();
  // New output (with --minify)
  {using e=new Resource;e.activate()}

• Fix module evaluation when an error is thrown (#4461, #4467)

  If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.

• Fix some edge cases around the new operator (#4477)

  Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:

  // Original code
  new (foo()`bar`)()
  new (foo()?.bar)()
  // Old output
  new foo()bar();
  new (foo())?.bar();

... (truncated)

Commits

• bb9db84 publish 0.28.1 to npm
• 9ff053e security: add integrity checks to the Deno API
• 0a9bf21 enforce non-negative size in gzip parser
• e2a1a71 security: forbid \\ in local dev server requests
• 83a2cbf fix #4482: don't inline using declarations
• 308ad74 fix #4471: renaming of nested var declarations
• f013f5f fix some typos
• aafd6e4 chore: fix some minor issues in comments (#4462)
• 15300c3 follow up: cjs evaluation fixes
• 1bda0c3 fix #4461, fix #4467: esm evaluation fixes
• Additional commits viewable in compare view

Updates tsx from 4.21.0 to 4.22.4

Release notes

Sourced from tsx's releases.

v4.22.4

4.22.4 (2026-05-31)

Bug Fixes

• resolve CommonJS directory requires inside dependencies (#803) (1ce8463)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.22.3

4.22.3 (2026-05-19)

Bug Fixes

• decode typed loader source (dce02fc)
• preserve entrypoint with TypeScript preload hooks (68f72f3)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.22.2

4.22.2 (2026-05-18)

Bug Fixes

• preserve CJS JSON require in ESM hooks (35b700b)
• preserve named exports from CommonJS TypeScript (11de737)
• support module.exports require(esm) interop (cf8f199)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.22.1

4.22.1 (2026-05-17)

Bug Fixes

• resolve tsconfig path aliases containing a colon (#780) (6979f28)

---

This release is also available on:

• npm package (@​latest dist-tag)

... (truncated)

Commits

• 1ce8463 fix: resolve CommonJS directory requires inside dependencies (#803)
• dce02fc fix: decode typed loader source
• 68f72f3 fix: preserve entrypoint with TypeScript preload hooks
• 69455cf test: cover package exports for ambiguous ESM reexports
• 35b700b fix: preserve CJS JSON require in ESM hooks
• ef807db chore: update testing dependencies
• 3917090 test: document compatibility test taxonomy
• de8113f refactor: centralize Node capability facts
• c1f62db test: consolidate tsconfig path edge coverage
• 4e08174 test: consolidate loader hook coverage
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for tsx since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[github-actions]

Dependency Update Analysis

Summary: tsx was updated from ^4.20.5 to ^4.22.4, which pulled esbuild from 0.27.3 to 0.28.1; overall PR risk is low-to-moderate (security-positive changes, no repo-specific breaking impact found, PR-testable paths exist).

tsx ^4.20.5 → ^4.22.4

Ecosystem: npm / Node

Check	Result
Breaking changes	✅ None found for current usage
Testable in PR	✅ Yes — exercised by PR workflows

Changelog highlights (v4.20.5 → v4.22.4)

• v4.21.0 and v4.22.0 upgraded bundled/transitive esbuild.
• v4.21.1 added Node compatibility fixes (including Node 24 support), relevant to this repo’s Node 24 workflow runtime.
• v4.22.x includes module resolution/interoperability bug fixes (CJS/ESM/path alias handling).
• No CVE/GHSA/security advisory entries were published in tsx release notes for these versions.

Usage in this repository

• package.json#L7-L10: test command is tsx --test tests/unit/*.test.ts, and tsx is a direct dependency.
• .github/workflows/ci.yml#L64-L84: TypeScript tests run npm ci then npm test on pull_request.
• .github/workflows/oblt-aw-automerge.yml#L70-L86 and #L129-L145: actions/github-script jobs call require('tsx/cjs/api').register() before loading TS scripts.

Compatibility assessment (including CVE-focused security view)

• Current usage is limited to test execution and runtime TS require hooks (tsx/cjs/api) in automation scripts; no direct use of edge loader features called out as changed.
• Internal resolver/runtime fixes in tsx reduce fragility in module loading paths and do not introduce new privileged behavior in this repo’s usage pattern.
• No vulnerability advisories were disclosed for tsx in the updated range; attack surface for this repo is effectively unchanged at runtime, with lower operational risk from resolver bug fixes.

esbuild 0.27.3 → 0.28.1 (via tsx)

Ecosystem: npm / Node (transitive)

Check	Result
Breaking changes	⚠️ Upstream marks 0.28.0 as breaking, but no breaking impact found for this repo’s consumed surface
Testable in PR	✅ Yes — exercised through tsx-based test and automerge workflows

Changelog highlights (v0.27.3 → v0.28.1)

• v0.28.0: added integrity verification for fallback npm binary download path (security-hardening; may fail installs if custom registry serves mismatched binaries).
• v0.28.1: fixed Windows local dev-server path traversal issue (GHSA-g7r4-m6w7-qqqr) by disallowing \\ in request paths.
• v0.28.1: added Deno API binary integrity checks (GHSA-gv7w-rqvm-qjhr).

Usage in this repository

• esbuild is not directly imported in repo source; it is consumed transitively by tsx (package-lock.json shows node_modules/tsx depending on esbuild ~0.28.0).
• Effective execution paths are CI/test and workflow script runtime via tsx, not esbuild’s local dev server or Deno install API.

Compatibility assessment (including CVE-focused security view)

• The two advisory-linked changes are security-hardening and reduce exposure (path traversal mitigation + binary integrity checks).
• The path traversal fix targets esbuild’s local HTTP dev server; this repository does not use that server in workflows/tests, so practical exploitability here is minimal.
• Integrity-check hardening can cause install failures with tampered/mismatched mirrored binaries; that is an operational regression risk, not a security regression. In standard GitHub-hosted CI with normal npm registry behavior, this risk is low.
• No new authn/authz, permission-scope, or sandbox boundary expansions were introduced for the repo’s actual usage.

Labels Applied

• oblt-aw/ai/merge-ready — applied. Criteria met: overall risk low-to-moderate, no breaking change to consumed repo usage, npm ecosystem checks acceptable, and affected paths are PR-testable (pull_request) and CI/tooling scoped.

Note

🔒 Integrity filter blocked 1 item

The following item were blocked because they don't meet the GitHub integrity level.

• build(deps): bump esbuild and tsx #1187 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

---

What is this? | From workflow: Observability Agentic Workflow — Pull Request

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[github-actions]

Automerge skipped (dependency collection)

This pull request was classified as node-dependencies. The Observability automerge workflow does not support that dependency collection.

Collections enabled for automerge: github-actions, pre-commit, terraform, open-policy-agent

Dependency-review may still have applied oblt-aw/ai/merge-ready for risk review. Only allow-listed collections proceed to Copilot approval and merge via this workflow.

Changed files considered for classification:

• package-lock.json
• package.json