Repository navigation
Use marker-template-runtime 1.1.0 - #569
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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.
Keeps STAPLE on the same spec runtime as MARKER, which needs the v1.1.0 release so it can import STAPLE forms that use the multi-select (
checkboxes) field or option display labels (enumNames). v1.1.0 is additive: Core V1 now allows those two things and everything that was valid still is.STAPLE only uses the runtime for semantic-metadata work (
projectMetadataResponse.ts), which this release does not change, so nothing about STAPLE's behaviour changes; this is only to keep the two apps on one version. It is not needed for the MARKER fix and can wait.Notes
form-studio, because form-studio v1.1.0 pins 1.0.0 itself (used only for its semantic-binding editor). Harmless; it goes away when form-studio bumps its dependency.Testing
Typecheck (apart from the existing
getJsonSchema.test.tserrors), lint, the marker-template capability (17) and semantic (22) tests, and the full suite (321 tests) pass against the new runtime.🤖 Generated with Claude Code