From 35b1b252bd7818975eb55f9f68aaf1c395a3b62b Mon Sep 17 00:00:00 2001 From: shrugs Date: Wed, 3 Jun 2026 14:10:16 -0500 Subject: [PATCH 1/2] docs: pin enscli/ensskills prerelease install refs to merged snapshot Now that #2242 is merged, point the prerelease install shim at immutable refs from that merge's snapshot publish instead of the floating @next/main: - ENSCLI_ENSSKILLS_NPM_SPEC -> 0.0.0-next-20260603190454 (published snapshot version) - ENSCLI_ENSSKILLS_GIT_REF -> 0eec193 (the main commit it was built from) Also note in the hosted-instance warning that these prerelease refs are functional against the hosted instances running snapshot.sdkVersion. Co-Authored-By: Claude Opus 4.8 (1M context) --- .../HostedInstanceVersionWarning.astro | 5 +++-- .../src/content/docs/docs/integrate/ai-llm.mdx | 2 +- .../integration-options/ensskills.mdx | 8 +++++--- .../src/data/enscli-ensskills-prerelease.ts | 18 ++++++++++-------- 4 files changed, 19 insertions(+), 14 deletions(-) diff --git a/docs/ensnode.io/src/components/molecules/HostedInstanceVersionWarning.astro b/docs/ensnode.io/src/components/molecules/HostedInstanceVersionWarning.astro index ee46dfbab..7951ccb99 100644 --- a/docs/ensnode.io/src/components/molecules/HostedInstanceVersionWarning.astro +++ b/docs/ensnode.io/src/components/molecules/HostedInstanceVersionWarning.astro @@ -44,9 +44,10 @@ npm install enskit@${VERSION} enssdk@${VERSION}`} knowledge and queries matched to the deployed API.{" "} {/* TEMP prerelease: revert to pinning both at {VERSION} at the first official release */} These two packages are newer than the deployed {VERSION} release, so until - their first official release install them from the prerelease tag— + their first official release install them from the prerelease snapshot— ensskills@{ENSCLI_ENSSKILLS_NPM_SPEC} and{" "} - enscli@{ENSCLI_ENSSKILLS_NPM_SPEC}. + enscli@{ENSCLI_ENSSKILLS_NPM_SPEC}. These prerelease refs are functional + against our hosted instances running {VERSION}. ) } diff --git a/docs/ensnode.io/src/content/docs/docs/integrate/ai-llm.mdx b/docs/ensnode.io/src/content/docs/docs/integrate/ai-llm.mdx index 45d9e343d..89d36c78c 100644 --- a/docs/ensnode.io/src/content/docs/docs/integrate/ai-llm.mdx +++ b/docs/ensnode.io/src/content/docs/docs/integrate/ai-llm.mdx @@ -39,7 +39,7 @@ npm install # symlinks the skills for your detected agents ## Quickstart (`npx skills`) -Not in a Node project? [`skills`](https://github.com/vercel-labs/skills) installs every ENS skill straight from the repo. It normally pins to the matching `v…` release tag; during the current prerelease window it tracks `main` until `enscli`/`ensskills` ship in their first official release: +Not in a Node project? [`skills`](https://github.com/vercel-labs/skills) installs every ENS skill straight from the repo. It normally pins to the matching `v…` release tag; during the current prerelease window it pins to the immutable `main` commit the prerelease snapshot was built from, until `enscli`/`ensskills` ship in their first official release: `enscli` and `ensskills` are newer than the current `v{snapshot.sdkVersion}` release, so they aren't published at that version yet. Until the first official release that includes them, the - snippets below track the `@next` npm tag and the `main` branch — they'll pin to an exact `v…` tag - like the rest of the suite at that release. + snippets below pin to a prerelease snapshot build published from `main` (an exact snapshot version + and an immutable `main` commit, functional against the hosted instances running + `{snapshot.sdkVersion}`) — they'll move to an exact `v…` tag like the rest of the suite at that + release. - Pinning to an exact version is intentional: ENS skills are version-locked to the ENSNode suite, so you always get skills that match the APIs you're targeting. With `skills-npm` that's the pinned npm version; with `npx skills` it's the `v…` release tag in the URL. Avoid pulling skills from a moving git branch — except during the prerelease window noted above, which tracks `main`/`@next` until the first official release. + Pinning to an exact version is intentional: ENS skills are version-locked to the ENSNode suite, so you always get skills that match the APIs you're targeting. With `skills-npm` that's the pinned npm version; with `npx skills` it's the `v…` release tag in the URL. Avoid pulling skills from a moving git branch — except during the prerelease window noted above, which pins to an immutable `main` commit and an exact snapshot version until the first official release. ## Skills included diff --git a/docs/ensnode.io/src/data/enscli-ensskills-prerelease.ts b/docs/ensnode.io/src/data/enscli-ensskills-prerelease.ts index 1642eb0f2..e454e5fed 100644 --- a/docs/ensnode.io/src/data/enscli-ensskills-prerelease.ts +++ b/docs/ensnode.io/src/data/enscli-ensskills-prerelease.ts @@ -3,15 +3,17 @@ * * Both packages were introduced *after* the current `v{snapshot.sdkVersion}` release, so — unlike * `enssdk`/`enskit` — they are not yet published at `snapshot.sdkVersion`. Until the first official - * release that publishes them in lockstep with the rest of the suite, docs install snippets track: - * - `ENSCLI_ENSSKILLS_NPM_SPEC`: the `@next` snapshot dist-tag (published to npm on every push to - * `main` by `release_snapshot.yml`), and - * - `ENSCLI_ENSSKILLS_GIT_REF`: the `main` branch (where `packages/ensskills/skills` lives; - * snapshot releases create no git tag to point at). + * release that publishes them in lockstep with the rest of the suite, docs install snippets pin to + * the prerelease snapshot build published from `main` (by `release_snapshot.yml`): + * - `ENSCLI_ENSSKILLS_NPM_SPEC`: the exact published snapshot version, and + * - `ENSCLI_ENSSKILLS_GIT_REF`: the `main` commit that snapshot was built from, so the + * `skills add tree/` URL is pinned to an immutable commit rather than a moving branch. * - * Remove this module at that first official release and revert the `enscli`/`ensskills` snippets in + * Both refs are functional against the hosted instances running `snapshot.sdkVersion`. + * + * Remove this module at the first official release and revert the `enscli`/`ensskills` snippets in * `ai-llm.mdx`, `ensskills.mdx`, and `HostedInstanceVersionWarning.astro` back to * `snapshot.sdkVersion` / `v${snapshot.sdkVersion}`. */ -export const ENSCLI_ENSSKILLS_NPM_SPEC = "next"; -export const ENSCLI_ENSSKILLS_GIT_REF = "main"; +export const ENSCLI_ENSSKILLS_NPM_SPEC = "0.0.0-next-20260603190454"; +export const ENSCLI_ENSSKILLS_GIT_REF = "0eec193"; From 4942cce2eee2fc75201dc1acc2d68a804bd82e88 Mon Sep 17 00:00:00 2001 From: shrugs Date: Wed, 3 Jun 2026 14:16:00 -0500 Subject: [PATCH 2/2] fix --- .../integration-options/ensskills.mdx | 23 ------------------- 1 file changed, 23 deletions(-) diff --git a/docs/ensnode.io/src/content/docs/docs/integrate/integration-options/ensskills.mdx b/docs/ensnode.io/src/content/docs/docs/integrate/integration-options/ensskills.mdx index 43a9ddbce..0b6ac6971 100644 --- a/docs/ensnode.io/src/content/docs/docs/integrate/integration-options/ensskills.mdx +++ b/docs/ensnode.io/src/content/docs/docs/integrate/integration-options/ensskills.mdx @@ -23,17 +23,6 @@ Pick the path that matches your project. Either way, **pin to an exact `ensskill Add both to your project and wire a `prepare` script: -{/* TEMP prerelease: remove this Aside at the first official release that publishes enscli + ensskills */} - - - - - - - ## Quickstart (`npx skills`) Not in a Node project? Vercel's [`skills`](https://github.com/vercel-labs/skills) tool installs the skills straight from this repo — no `package.json`, no `skills-npm`. Point it at the `packages/ensskills/skills` directory on the matching **release tag** (the `v` prefix matters): @@ -93,10 +74,6 @@ npx skills add https://github.com/namehash/ensnode/tree/${ENSCLI_ENSSKILLS_GIT_R It detects your agents and writes the skills into each (`.claude/skills`, `.cursor/skills`, …). Bump the tag in the URL to upgrade. - - ## Skills included - **`ens-protocol`** — how the ENS protocol works at a conceptual level: the nametree, normalization, namehash/labelhash, registry/resolver/registrar, forward & reverse resolution, primary names, records, and ENS across chains. Vendor-neutral, intentionally stable, with pull-as-needed reference pages. The mental model the other skills build on.