build(deps): consolidate weekly Dependabot bumps (2026-05-28)#137
Merged
Conversation
Squashes 11 open Dependabot PRs into one merge to reduce CI churn. npm: - @aws-sdk/client-bedrock-runtime 3.1045.0 → 3.1054.0 - @aws-sdk/client-sagemaker-runtime 3.1045.0 → 3.1054.0 - @duckdb/node-api 1.5.2-r.1 → 1.5.2-r.2 - @types/node 25.7.0 → 25.9.1 (typescript-tooling group) - astro 6.3.3 → 6.3.8 - lefthook 2.1.6 → 2.1.8 - lru-cache 11.3.6 → 11.5.0 - tsx 4.21.0 → 4.22.3 - web-tree-sitter 0.26.8 → 0.26.9 (tree-sitter group) github-actions (SHA-pinned): - github/codeql-action v4.35.4 → v4.35.5 - pnpm/action-setup v4.1.0 → v6.0.8 Held back: - license-checker-rseidelsohn 4.4.2 → 5.0.0 — v5 requires Node >= 24 but the repo's engines.node is ">=22.0.0" and CI runs both 22 and 24. Will pick up when the repo drops Node 22 support. Closes #123, #124, #125, #126, #127, #128, #129, #133, #134, #135, #136
This was referenced May 28, 2026
4 tasks
theagenticguy
added a commit
that referenced
this pull request
May 28, 2026
## Summary Fixes the v0.6.2 release-publish abort. **PR #137** bumped `web-tree-sitter` 0.26.8 → 0.26.9 in `package.json` but did not re-run `scripts/build-vendor-wasms.sh`, so: - `vendor/wasms/manifest.json` still recorded `0.26.8` - the vendored `web-tree-sitter.wasm` was still the 0.26.8 blob The `prepublishOnly` guard (`verify-vendor-wasms.mjs`) correctly caught the drift and blocked `pnpm publish` of `@opencodehub/ingestion`. Because `pnpm -r publish` runs in dependency order and ingestion is upstream of cli/mcp/pack, that abort left the **v0.6.2 npm release half-published**. ## Fix - Re-copied the real 0.26.9 runtime wasm from the installed package (sha `1ed02fe…`, was `082795b…`). - Bumped the manifest string to `0.26.9`. The 14 grammar wasms are unchanged (their pins didn't move), so no docker/emcc rebuild was needed — just the runtime blob the bump actually touched. ## Test plan - [x] `node verify-vendor-wasms.mjs` — OK (16 wasm files, manifest matches pins) - [x] `pnpm -F @opencodehub/ingestion test` — 602/602 pass against the new runtime wasm - [x] full `pnpm run check` — green, 0 failures across 16 packages - [ ] CI green ## Release recovery (after merge) v0.6.2 partially published before the abort (analysis, scanners, scip-ingest, search, storage, wiki). This fix unblocks ingestion so the remaining 10 packages (cli, mcp, pack, core-types, embedder, frameworks, policy, sarif, summarizer, cobol-proleap) can publish — completing the release and resolving the currently-broken cross-package dep graph on npm. Will be cut as the next release-please version.
2 tasks
theagenticguy
added a commit
that referenced
this pull request
May 28, 2026
) ## Summary Docs-only Compound follow-on to the v0.6.2 → v0.6.3 release recovery. Two durable ERPAVal lessons capturing the pre-existing bugs that triggering the release surfaced. - **`vendored-artifact-bump-must-revendor-in-same-pr`** — PR #137 bumped `web-tree-sitter` 0.26.8→0.26.9 without re-running the vendor script. It passed all CI (the `prepublishOnly` guard isn't a CI step) and aborted the dependency-ordered publish at release time. Re-vendor vendored-artifact deps in the same PR; ideally promote the guard into CI so the bump fails red, not the release. - **`npm-trusted-publisher-matches-entry-workflow-not-reusable`** — npm OIDC matches the **entry** workflow (`release-please.yml`), not the reusable one that runs `npm publish` (`release.yml`). Registering the wrong one 404s the token exchange; only manual `workflow_dispatch` runs ever published, so npm lagged the git tags for a full release cycle. Config is web-UI-only, passkey-gated, one entry per package (17 here). ## Test plan - [x] commitlint `docs(repo):` accepted - [x] No code changes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Consolidates the 11 open Dependabot PRs into a single merge to cut CI churn. Lockfile regenerated and full local gate (
pnpm run check— lint + typecheck + test + banned-strings) is green.npm bumps
@aws-sdk/client-bedrock-runtime@aws-sdk/client-sagemaker-runtime@duckdb/node-api@types/node(typescript-tooling group)astrolefthooklru-cachetsxweb-tree-sitter(tree-sitter group)github-actions bumps (SHA-pinned)
github/codeql-action68bde55…)9e0d7b8…)github/codeql-action(release.yml, codeql-bundle)9887d98…f4d0a7a…pnpm/action-setupa7487c7…)0e279bb…)Held back
engines.nodeis>=22.0.0and CI'snode-versionmatrix runs both 22 and 24. Pick this up when the repo drops Node 22 support. PR build(deps-dev): bump license-checker-rseidelsohn from 4.4.2 to 5.0.1 #135 stays open as a tracking marker if the user prefers; otherwise it should be closed with a comment.Closes
#123, #124, #125, #126, #127, #128, #129, #133, #134, #136
(also supersedes #135 modulo the Node 22 caveat above)
Test plan
pnpm install --no-frozen-lockfile(lockfile regen clean)pnpm run lint— biome clean across 670 filespnpm run typecheck— clean across all 19 workspace projectspnpm run test— 1959 tests, 0 failures across 16 packagespnpm run banned-strings— PASS