Uh oh!
There was an error while loading. Please reload this page.
chore: release v0.9.6 - #30
Merged
Merged
Conversation
Five merges have landed since 0.9.5 and the version never moved, so the registry's staleness check could not tell an old instance from a current one — which is why two servers had to be restarted by hand rather than noticing for themselves. Version only. Publishing is a separate question: the manifest still carries upstream's package name and repository, and that name belongs to somebody else on npm. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018PkYQzbsnMihHesafWvXKs
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 freeto 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.
Five merges have landed since 0.9.5 and the version never moved, so the registry's staleness check
could not tell an old instance from a current one. That is why two servers had to be restarted by
hand today rather than noticing for themselves.
Version only, across the five manifests and the lockfile. Built and checked: the binary reports
0.9.6.
Not done: publishing
npm run release:patchwould alsonpm publish -w packages/cli, and that is a separate decisionrather than a step:
"name": "diffity"and pointsrepositoryatkamranahmedse/diffitykamranahmedsekirillgroshkovSo publishing would either be refused, or — if permissions ever allowed it — put a fork under
somebody else's public package name, for their users. Either way it is not a release of this fork.
Publishing this properly needs a name of its own,
@naturalcycles/diffityor similar, with therepository field to match. Worth deciding on purpose rather than as a side effect of a version bump.
🤖 Generated with Claude Code
https://claude.ai/code/session_018PkYQzbsnMihHesafWvXKs