devops: point the README badges at @highflame/codeoid - #293
Merged
Conversation
The install commands moved to the scoped package when it was renamed, but the three npm badges did not — they still read the unscoped `codeoid`, which is frozen at 0.3.4. The version badge would have advertised 0.3.4 forever while the project shipped 0.4.x, and the downloads badge tracked a package nobody should be installing. Also corrects the rename note, which claimed the predecessor packages were "deprecated on npm". They are not: `npm view codeoid deprecated` is still empty, because deprecating them needs the personal account that owns them. Say only what is true today — the old package is frozen and gets no further releases — which stays accurate once they are deprecated. Adds the consequence a reader actually needs: this is a new package, not a transfer, so no update path carries anyone across. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
akashjavelin
approved these changes
Aug 13, 2026
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
3 participants
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.
The rename PR moved the install commands to
@highflame/codeoidbut left the three npm badges pointing at the unscopedcodeoid, which is frozen at0.3.4.0.3.4forever while the project shipped0.4.xAll three now point at
@highflame/codeoid. Verified live: both shields endpoints return 200 and rendernpm: v0.4.1/downloads: 66/month, matchingnpm view @highflame/codeoid version.Also corrects the rename note. It claimed the predecessor packages were "deprecated on npm" — they are not;
npm view codeoid deprecatedis still empty, since deprecating them requires the personal account that owns them. The note now says only what is true today (frozen at0.3.4, no further releases), which stays accurate after they are deprecated, and adds the consequence a reader needs: this is a new package rather than a transfer, so no update path carries anyone across.Still outstanding, unchanged by this PR: actually running
npm deprecateoncodeoid,@codeoid/protocol, and@codeoid/corefrom the owning account.