release: v0.5.0 - #110
Merged
Merged
Conversation
Roll the changelog into the 0.5.0 section, bump the version markers across the runtime and both SDKs, and refresh the vision status line. - CHANGELOG.md: [Unreleased] → [0.5.0] (2026-06-13) + fresh [Unreleased]; links. - internal/version: 0.4.1-dev → 0.5.1-dev (un-stamped local builds). - sdks/python: 0.4.0 → 0.5.0 (pyproject + __init__). - sdks/typescript: 0.1.0 → 0.5.0, so the tag publishes @riskkernel/sdk@0.5.0. - docs/VISION: status line → v0.5.0. Also bump the TS esbuild dev-dependency override to ^0.28.1 to clear a newly published advisory (GHSA-gv7w-rqvm-qjhr) that now covers the 0.25.x the previous override pinned. Dev/build tooling only — the published package ships no runtime dependencies — but it keeps the release tree's audit clean.
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.
Cuts v0.5.0. Headline: the TypeScript SDK lands —
@riskkernel/sdkis on npm, dependency-free, at parity with the Python SDK (governed runs, budgets, the proxy, approval gates, crash-resume, and the Vercel AI SDK adapter) — alongside the reproducible cost benchmark and the #29 crash-resume correctness fix.Version markers (per the release checklist)
CHANGELOG.md[Unreleased]→[0.5.0] - 2026-06-13+ fresh[Unreleased]+ compare linksinternal/version/version.go0.4.1-dev→0.5.1-devsdks/python(pyproject.toml+__init__.py)0.4.0→0.5.0sdks/typescript/package.json0.1.0→0.5.0docs/VISION.mdv0.5.0The TS bump means the
v0.5.0tag publishes@riskkernel/sdk@0.5.0tokenlessly via the npm workflow (npm currently only has the 0.1.0 name-claim).Also: dev-dep security
Bumps the TS
esbuildoverride^0.25.0→^0.28.1to clear a newly published advisory (GHSA-gv7w-rqvm-qjhr) that now covers the0.25.xthe previous override pinned — it surfaced as 7 high on the tree since #104/#105 CI ran. Dev/build tooling only: the published package ships zero runtime deps, so consumers are unaffected.npm auditis back to 0; typecheck/test (11)/build all pass on esbuild 0.28.1.After merge: sync main, then tag
v0.5.0→ binaries + signed image + PyPI + the first tokenless npm publish.