Repository navigation
Prepare v0.21.1 release - #394
Merged
Merged
Conversation
Contributor
Railly
approved these changes
Oct 13, 2026
This branch was successfully deployed
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
2 participants
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.
Prepare json-render 0.21.1 with fixes for dotted form values (#353), numeric validation (#389), and
s.any()type inference (#390), plus the documentation updates from #340 and #363.Synchronize all 29 public @json-render packages, add root and docs release notes, and refresh the changelog's content hashes in the docs fixture. Required package documentation is present for every public package.
Validation: frozen dependency install, version synchronization, full workspace type check, public package builds, 572 core tests, production docs build, and 122 route tests passed.