release: publish npm 0.3.0 - #25
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.
What changed
Version all 12 aligned
@bidilens/*packages to 0.3.0, consume the two reviewed Changesets, regenerate package changelogs and the bundled GitHub Action, align the private demo/root/citation metadata, and update current-release documentation.Evidence
pnpm run checkat 0.3.0 (396/396 tests; build, types, lint, corpus, docs, action bundle green).pnpm run test:visualis delegated to this PR's pinned three-browser CI matrix.pnpm run npm:release:dry-run -- --version 0.3.0; all 12 tarballs passed and 0.3.0 is unused on npm.Security and language review
This release does not weaken the existing hidden-bidi-control auditing or source-preservation model. The corpus is technically reviewed and user-provided, not represented as native-speaker certification. Publication remains isolated behind the protected
npm-releaseenvironment, trusted publishing, provenance, exact version checks, immutable-version rejection, and the exact human confirmation phrase.