Repository navigation
Prepare interaction npm distribution and reviewed release workflow - #3
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.
Applications need validators that distinguish valid data and result formats from successful execution. This prepares @zixcel/interaction@0.10.0 for npm distribution with a tested settings example, package metadata, archive checks, and a manual reviewed release workflow.
The change contains exactly nine files: README and the usage guide, package.json and Cargo.toml, two workflows, and three validation/consumer scripts. JavaScript implementations, TypeScript declarations, Rust source, existing tests, and licensing match the source baseline. Cargo retains the zixcel-private publication restriction.
Validation:
Reviewed source tree: a16dcd777f4bb0ce13275c9fc2d92aae27b49582.
Archive SHA256: 822451535d91da92f9e48d4be60dd209ca1f484f9ef4ebcd8e70da2245fa07a4.
The ordinary CI uses read-only permissions. The release workflow verifies the exact source and archive, then publishes the archive once in a separate OIDC job and checks registry versions, integrities, and tags. It requires an existing public package; initial namespace bootstrap and trusted-publisher setup are separate prerequisites. Local checks do not establish registry availability or publication authority.