chore: release @tskm/core 0.2.1 (compiled fast path) - #37
Merged
Conversation
Bumps @tskm/core to 0.2.1 for the opt-in, experimental compiled validation fast path (safeParseCompiled / getCompiledValidate). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
commit: |
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.
What
Adds a changeset that bumps
@tskm/coreto 0.2.1 (patch).The change being released is the opt-in, experimental compiled validation fast path (Tier-0, no eval):
safeParseCompiled/getCompiledValidate, plus theCursorandSteptypes. It compiles a schema into a closure tree at construction time with noeval/new Function/ codegen, so it runs under a strict CSP and on edge runtimes, staying byte-identical tosafeParseon both success and error paths.Scope
@tskm/coreis published.@tskm/compilerand@tskm/vitehave no user-facing changes this cycle and are not bumped.@tskm/example-*and@tskm/playgroundare private and only get an internal-dependency version touch (not published).Release flow
Merging this PR makes the
versionjob open a Version Packages PR. Merging that PR triggers thepublishjob (waits forreleaseEnvironment approval), which publishes@tskm/core@0.2.1over OIDC with provenance, then tags and creates the GitHub Release automatically.🤖 Generated with Claude Code