Version Packages - #34
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@cosyte/transform@0.0.8
Patch Changes
9fdde50: No runtime impact: punctuation only, plus a new repository-internal check that keeps it that way.
The Cosyte brand voice does not use the em dash (U+2014). This package carried 659 of them across
75 of its 98 tracked files, including the README, every documentation page that publishes to the
documentation site, and the source doc comments that compile into the shipped type declarations and
render in an editor on hover. All 609 that were in scope are rewritten with a period, a colon, a
comma or parentheses, chosen by what each sentence meant rather than by one blanket substitution.
No exported name, type, issue code, fatal code or documented behaviour changed. Two strings changed
punctuation and nothing else, and both belong to developer tooling rather than to the published
package: the PHI scanner's clean-run line, and one diagnostic from the check that verifies this
repository's own contributor instructions.
Two files still carry the character and each is an exemption with a written reason. The changelog's
dated archive below its "Released before this file was generated" heading is a frozen record whose
entries are byte identical to the tarballs they shipped in, and rewriting it would destroy the
evidence a changelog exists to hold. The vendored third-party tarball under
vendor/holds thecharacter's bytes by coincidence inside a compressed stream, which no edit can remove.
The check that enforces the rule lands in the same change as the sweep, on purpose: a check arriving
before its sweep turns the build red on arrival, and a sweep arriving before its check lets the
character grow back. It reads bytes directly rather than shelling out, refuses to report a clean
result whenever it cannot prove it read its subject, and holds its own source to the same rule by
assembling every banned spelling at runtime instead of writing one down.