release: 0.9.0 - #187
Merged
Merged
Conversation
Bump the package and generated-project contract to 0.9.0.\n\nDocument the encrypted-column type surface so the publication documentation gate passes.
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.
Motivation
Prepare the first minor release after v0.8.1. The current main branch also fails the publication documentation gate because the encrypted-column interface members are undocumented.
Change
Testing Completed
deno task check— formatting, lint, documentation, and all 512 tests passed.deno task build— reference app production build passed.deno task publish:dry --allow-dirty— simulated@nzip/lofi@0.9.0publication passed.deno task test:golden— full generated-app browser golden passed, including passkey enrollment, recovery, local-only return, PWA, offline, and recipe flows.Responsible AI disclosure
Codex prepared the version updates, documentation fix, and release validation under maintainer direction. The maintainer remains responsible for reviewing and merging the release.