Version Packages - #38
Merged
Merged
Conversation
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@tskm/core@0.2.1
Patch Changes
dfcb2a7: Add an opt-in, experimental compiled validation fast path (Tier-0, no eval).
safeParseCompiledcompiles a schema into a closure tree at construction time, with noeval,new Function, or codegen, so it runs under a strict CSP and on edge runtimes (Cloudflare Workers, Deno Deploy, Vercel Edge) where JIT codegen is blocked.safeParseon both success and error paths.~run, and specialization dispatches on factory identity (schema.reference), so a foreign schema with a collidingtypestring keeps running its own~run.safeParseCompiled,getCompiledValidate, and theCursorandSteptypes. A bare top-level primitive should keep usingsafeParsedirectly.@tskm/example-advanced@0.0.3
Patch Changes
@tskm/example-basic@0.0.3
Patch Changes
@tskm/example-ssot@0.0.3
Patch Changes
@tskm/playground@0.0.1
Patch Changes