feat: honor public reads and expose deployment identity (v0.40.0) - #146
Merged
Conversation
rrrodzilla
marked this pull request as ready for review
September 9, 2026 20:46
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.
Anonymous GET/HEAD entity reads now reach Cedar so explicit public-read policies work before sign-in. Supplied invalid credentials still fail authentication, and record, tenant, field, custom-policy, and related-data restrictions remain enforced. Generated authenticated-only permits exclude anonymous callers.
/metaadds the embedding binary's release version and source revision while preserving the existing runtime-component meaning ofbuild.version. Official release builds embed their checked-out source commit. Missing metadata and the public-read contract are documented.Prepares SchemaForge v0.40.0 with acton-service 0.40.0. Backend and adapter versions reflect the added optional-claims record-policy API.
Validation: 2,437 main-suite tests passed, with seven marked integration tests skipped. Another 534 PostgreSQL/backend/CLI tests passed against a disposable PostgreSQL 16 database. All-target Clippy passed with warnings denied for the default, PostgreSQL, and SQL Server configurations. Live SurrealDB and PostgreSQL binary smoke checks passed for public reads, field filtering, invalid credentials, protected reads, authenticated writes, and release metadata. All five PR checks passed: PostgreSQL conditional operations, site smoke, SQL Server 2019 and 2022, and Windows MSSQL build.
Closes #144
Closes #145