build: adopt the Node.js 24 runtime (v0.3.1)#5
Merged
Conversation
jhumel-code
commented
Jun 8, 2026
jhumel-code
commented
Collaborator
GitHub deprecates the Node 20 Actions runtime — runners default to Node 24 on 2026-06-16 and Node 20 is removed on 2026-09-16. Move `runs.using` to node24 now. No behavior change: the bundled `dist/` is byte-identical. Build CI and the `engines` field bump to Node 24 to match the runtime. Release v0.3.1.
Trustabl scan
Readiness goes from Readiness now 🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩 Projected if all findings resolved 🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩 Findings by severity
Projected headroom — estimate, not a re-scan
Projected by re-applying trustabl's own scoring with the listed findings resolved (nothing new introduced). Treat as guidance, not a guarantee.
✅ Passed scanning |
README + capabilities list the full analyzed surface (Claude/OpenAI/Google ADK/ LangChain/CrewAI/Pydantic AI/Vercel AI/AutoGen SDKs, MCP servers, and Claude subagents & skills), add a how-it-works note for the opt-in --vuln-scan, expand the detectors token list to the engine's full set, and bump install pins to v0.3.1.
jaysonsantos05
added a commit
that referenced
this pull request
Jun 9, 2026
commit 57d4363 Merge: 43e2066 fe74efa Author: Ian Jhumel Bautista <85332563+jhumel-code@users.noreply.github.com> Date: Tue Jun 9 01:11:35 2026 +0800 Merge pull request #5 from trustabl/build/node24-runtime build: adopt the Node.js 24 runtime (v0.3.1) commit fe74efa Author: Ian Jhumel Bautista <ianjhumelbautista@gmail.com> Date: Tue Jun 9 01:10:04 2026 +0800 docs: document full SDK coverage, vuln-scan, and detector tokens README + capabilities list the full analyzed surface (Claude/OpenAI/Google ADK/ LangChain/CrewAI/Pydantic AI/Vercel AI/AutoGen SDKs, MCP servers, and Claude subagents & skills), add a how-it-works note for the opt-in --vuln-scan, expand the detectors token list to the engine's full set, and bump install pins to v0.3.1. commit 685730b Author: Ian Jhumel Bautista <ianjhumelbautista@gmail.com> Date: Tue Jun 9 01:03:53 2026 +0800 build(action): adopt the Node.js 24 runtime ahead of Node 20 deprecation GitHub deprecates the Node 20 Actions runtime — runners default to Node 24 on 2026-06-16 and Node 20 is removed on 2026-09-16. Move `runs.using` to node24 now. No behavior change: the bundled `dist/` is byte-identical. Build CI and the `engines` field bump to Node 24 to match the runtime. Release v0.3.1. commit 43e2066 Merge: ad69fa2 771683a Author: Ian Jhumel Bautista <85332563+jhumel-code@users.noreply.github.com> Date: Tue Jun 9 00:30:02 2026 +0800 Merge pull request #4 from trustabl/feat/engine-v0.1.4-support feat: engine v0.1.4 support (line ranges + vuln-scan) — release v0.3.0 commit 771683a Author: Ian Jhumel Bautista <ianjhumelbautista@gmail.com> Date: Tue Jun 9 00:27:02 2026 +0800 feat(action): consume engine v0.1.4 (line ranges, vuln-scan); release v0.3.0 - Findings: read the engine's start_line/end_line range (v0.1.4 renamed the single `line` field) with a legacy `line` fallback, so inline annotations point at the right lines across engine versions and span multi-line ranges. - Add the `vuln-scan` input -> `--vuln-scan`: OSV CVE matches surface as findings (readiness/gate/annotations/SARIF) plus a dependency headline in every report (console panel, Step Summary, PR comment). - Add the `skill` scope to the typed Scope / surface-kind unions. - Set MIN_ENGINE_VERSION to v0.1.3 (first release with single-scan dual output, Code-Scanning-valid SARIF, and projected_scores). - Selftest: unpin from v0.1.2/pre-mcp to v0.1.4 + default rules (v0.1.4 supports the mcp category natively and loads newer rules leniently). - Branding: gray-dark marketplace badge; add the Trustabl banner to the README. - Release v0.3.0 (package.json, lockfile, CHANGELOG).
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.