Add a changeset for the @datocms/cli-utils repository field - #51
Merged
Conversation
The field itself landed in #50, but package metadata only reaches npm through a release, and a release only happens if a changeset asks for one. Without this, the fix sits on `main` indefinitely and npm keeps serving a manifest with no source link. Patch: it fixes what the published package says about itself, and adds no API surface. Claude-Session: https://claude.ai/code/session_01TbxhxyU1XBsSKtoCJXwAoD
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.
#50 gave
@datocms/cli-utilstherepositoryfield it was missing — it was theonly one of the five packages here without one. But package metadata only
reaches npm through a release, and with
changeset versiondriving theversions, a release only happens for packages a changeset asks for. So without
this file the fix sits on
mainindefinitely and npm keeps serving a manifestwith no source link.
patch, per the convention: it fixes what the published package says aboutitself, and adds no API surface.
Why it matters beyond the npm page
The
repositoryfield is also what pkg.pr.new reads — from the npm registry,not from this repo — to decide whether it can mint the short preview URL form.
Verified: the
react-datocmsrun on a commit that already had the field fixedlocally still emitted the long form, because npm's copy was stale.
So after this is released,
@datocms/cli-utilspreviews get the short URL:The long form documented in the README keeps working either way.
The rest of the metadata cleanup
Five more packages need a release for the same reason — their npm metadata still
carries a
git://URL, which GitHub stopped serving in 2022. Those repos don'tuse changesets, so there is nothing to commit there; the fix is already on their
default branches and a plain release picks it up:
react-datocms,vue-datocms,@datocms/svelte,@datocms/astro,datocms-listenEverything else across the eleven repos already has correct metadata on npm.