fix: complete follow-up corrections for v0.46.1 - #199
Open
rrrodzilla wants to merge 21 commits into
Open
rrrodzilla wants to merge 21 commits into
rrrodzilla wants to merge 21 commits into
Conversation
rrrodzilla
marked this pull request as ready for review
September 25, 2026 21:16
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.
Related display labels, derived collection IDs, and export labels now apply target schema, record, operator, and field permissions before enrichment. Authorization uses complete target rows before redaction. Relation-valued display fields resolve through at most three authorized target hops, with safe fallback for missing, denied, or cyclic targets.
PostgreSQL adds literal defaults inline so existing rows receive them. Optional-to-required changes backfill before enforcing the constraint, and checked plans refuse required changes without a usable literal default. Stored/derived inverse collection transitions are destructive and require review; single-schema API updates cannot silently change sibling storage. Matching SurrealDB and MSSQL migration behavior is included.
Generated relation-only and file-only pages omit unused helpers. Primary relation cells and relation pickers use display labels. New coverage includes populated-table migrations, authorization across nested relations and exports, TypeScript compilation, and browser rendering.
This prepares v0.46.1. The signed v0.46.0 source tag is preserved; its binary publication was cancelled. Validation uses targeted local
cargo checkand full CI tests, Clippy, generated-site builds, lint, and browser tests.Closes #195
Closes #196
Closes #197
Closes #198