fix: resolve outstanding issues for v0.46.0 - #189
Merged
Merged
Conversation
rrrodzilla
changed the title
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.
This prepares v0.46.0 with fixes for database planning, query validation, migrations, listener configuration, HTTP rate-limit handling, API consistency, and generated sites. Runtime validation and webhook handling now apply consistent schema, field, and destination rules.
Upgrade notes cover explicit tenant declarations, plain JSON webhook payload version 2, and informational migration
Reviewclassifications. Webhook delivery remains best effort, with its lack of durable replay and reconciliation limits now documented.Generated sites carry the active tenant through entity and file requests, show readable customizable error feedback, support duration/map/base64 fields, and respect computed fields and role-based form restrictions. Branding is configurable with neutral defaults. Existing customized page shells remain preserved, with migration guidance for branding and error handling.
Regression coverage includes read-only PostgreSQL roles and fresh registries, literal text filtering, rejected array comparisons, complete-batch migration refusal, listener precedence, 429 retries, relation visibility, hidden field projection, API error bodies, and webhook URL validation.
Validation: targeted local
cargo check; full nextest suites, PostgreSQL/SQL Server integration, Clippy, and generated-site checks run in CI. Release artifacts will be built and signed by the tag workflow after this PR passes and merges.Closes #178
Closes #179
Closes #180
Closes #181
Closes #182
Closes #183
Closes #185
Closes #186
Closes #187
Closes #188
Closes #190
Closes #191
Closes #192
Closes #193
Closes #194