fix(cli): generate projects against the 1.0 beta line; release CLI + UI as 1.0.0-beta.1 - #140
Open
abernatskiy wants to merge 5 commits into
Open
fix(cli): generate projects against the 1.0 beta line; release CLI + UI as 1.0.0-beta.1#140abernatskiy wants to merge 5 commits into
abernatskiy wants to merge 5 commits into
Conversation
`^1.0.0` excludes prereleases, and every published 1.0 version of @subsquid/pipes is one (alpha.1 .. beta.1), so the range resolved to nothing: `npm view '@subsquid/pipes@^1.0.0'` returns E404 and a freshly generated project failed to install. Use `^1.0.0-beta.1`, which takes the 1.0 betas today and the stable 1.0.0 once it ships. Verified end to end: generate -> pnpm install (resolves 1.0.0-beta.1) -> tsc --noEmit clean. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_018XHq4V964TkvPSjFtn3AwL
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_018XHq4V964TkvPSjFtn3AwL
Brings the UI onto the 1.0 beta line alongside @subsquid/pipes and @subsquid/pipes-cli. No code change; the alpha.8 build is unmodified. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_018XHq4V964TkvPSjFtn3AwL
@beta The generated README linked into `en/sdk/pipes-sdk/evm.autogenerated/...`. The docs dropped the `.autogenerated` folder suffix and both pages moved, so each link 404s in every scaffolded project: reference/pipes-ui -> guides/basic-development/pipes-ui advanced/quality-of-life#custom-metrics -> guides/advanced-topics/metrics Also pin `npx @subsquid/pipes-ui@beta`, matching the 1.0 beta line the generated project already depends on. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_018XHq4V964TkvPSjFtn3AwL
beta.1 is already published; this picks up the stable-pipe-id fix (#141) alongside the generated-dependency pin. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_018XHq4V964TkvPSjFtn3AwL
abernatskiy
force-pushed
the
fix/cli-generate-beta-projects
branch
from
July 31, 2026 20:23
85ca2a7 to
07cfdba
Compare
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
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.
Makes the CLI usable on the 1.0 beta line, and brings
@subsquid/pipes-cliand@subsquid/pipes-uionto it so all three packages ship a beta.The bug
Generated projects pinned
"@subsquid/pipes": "^1.0.0".^1.0.0excludes prereleases, and every published 1.0 version is one (1.0.0-alpha.1…1.0.0-beta.1), so the range matches nothing:Every project
pipes initgenerated therefore failed to install.The fix
^1.0.0-beta.1— a prerelease-aware range that takes the 1.0 betas today and the stable1.0.0once it ships (it does not widen to2.xprereleases).Verified end to end with a project generated from this branch:
pnpm installresolves@subsquid/[email protected]tsc --noEmitpasses against the beta APIpnpm testinpackages/pipes-cli: 289 passed, 3 snapshots updated (the pin appears in generatedpackage.jsonsnapshots)Version bumps
@subsquid/pipes-cli@subsquid/pipes-ui@subsquid/pipesis already at 1.0.0-beta.1. The UI bump is version-only; no code change.These bumps are required before tagging, since
release.ymlgatestag == package.json version. After merge, release with:Both land on the
betadist-tag (the workflow keeps prereleases offlatest, by design). The CLI tarball's own@subsquid/pipespin is rewritten at prepack to the exact workspace version,1.0.0-beta.1, which is already on npm — so the workflow's "core must be published first" gate is satisfied.Why this matters beyond the pin
The published CLI (
alpha.4, andlateststill points at the much olderalpha.1) predates the contract-first config model — it still expectssink/networkinstead ofprojectFolder/target/defaultNetwork/templates. The docs already document the new schema, so the docs describe a CLI that isn't on npm until this ships.Note that
latestfor@subsquid/pipes-cliremains1.0.0-alpha.1after this release. The docs are being updated to pin@betaexplicitly rather than relying onlatest.🤖 Generated with Claude Code
https://claude.ai/code/session_018XHq4V964TkvPSjFtn3AwL