docs: reflect 0.16.8-sqd.1 as npm latest (README matrix + dist-tag note fix)#141
Merged
Conversation
…on dist-tag note) 0.16.8-sqd.1 is now the npm 'latest' dist-tag. Update the README Ponder- versions matrix (add the 0.16.8 latest row; 0.16.7-sqd.1 is now published but has no dist-tag; seam range → 0.15.17-0.16.8) and correct the versions.json note, which #138 wrongly said 0.16.7-sqd.1 'keeps its ponder-0.16.7 dist-tag' — no such tag exists (npm view dist-tags shows only latest, ponder-0.16.6, ponder-0.15.17). 0.16.7-sqd.1 stays installable by exact version; a ponder-0.16.7 tag would have to be added deliberately. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The 0.16.7-sqd.1 note still read 'As the newest ponder version it publishes with --tag latest', now stale: 0.16.8-sqd.1 took over latest. Bring it in line with the 0.16.6/0.15.17 rows' dist-tag-status convention. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
What
@subsquid/ponder@0.16.8-sqd.1is now the npmlatestdist-tag. This makes the docs match that reality and fixes a factual error from #138.0.16.8 → 0.16.8-sqd.1 → latestrow; the0.16.7-sqd.1row moves from latest topublished · pin exact (no dist-tag); the seam-stable range →0.15.17–0.16.8.ponder-0.16.7dist-tag" — that tag does not exist.npm view @subsquid/ponder dist-tagsshows onlylatest(0.16.8-sqd.1),ponder-0.16.6, andponder-0.15.17. 0.16.7-sqd.1 waslatestand is now superseded; npm does not auto-retag a superseded version, so it currently has no dist-tag (still installable by exact version).Note for maintainers
If we want each supported non-latest version reachable by a
ponder-<version>dist-tag (as 0.16.6 / 0.15.17 are),0.16.7-sqd.1needs aponder-0.16.7tag added deliberately (npm dist-tag add). Flagging rather than doing it — it's a registry-mutation decision.Gates
Pure docs. JSON valid;
biome checkclean; secret-scan clean.