Release Open Receipt v0.2.1 - #8
Merged
Merged
Conversation
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
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.
Summary
Synchronize the standalone public repository to the already-published Open Receipt 0.2.1 package and current public specification.
Why
@receiptprotocol/open-receipt@0.2.1is already published and current, while this standalone repository still presented v0.1. The public source and release history should match the published package without republishing npm.Validation
bun run check— 57 tests passed; typecheck and build passednpm pack --dry-runinspected 17 intended public package fileslatestand exact version0.2.1No npm publication, deployment, production mutation, application server code, migrations, operator tooling, private data, or secrets are included.