From 1fdbb5d770d34eb24e15222cd5882d223300da8f Mon Sep 17 00:00:00 2001 From: Stefano Verna Date: Mon, 31 Aug 2026 11:17:26 +0200 Subject: [PATCH] Add a changeset for the `@datocms/cli-utils` repository field 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 --- .changeset/cli-utils-repository-field.md | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 .changeset/cli-utils-repository-field.md diff --git a/.changeset/cli-utils-repository-field.md b/.changeset/cli-utils-repository-field.md new file mode 100644 index 0000000..b6f6900 --- /dev/null +++ b/.changeset/cli-utils-repository-field.md @@ -0,0 +1,7 @@ +--- +'@datocms/cli-utils': patch +--- + +Add the `repository` field to the package manifest. It was the only package +here without one, so npm had no link back to the source, and tooling that reads +that field could not resolve the repository.