feat: release 1.0.0 with a rewritten README and pinnable release versions - #60
Merged
Merged
Conversation
…ions The file format has been stable at schema v5 since 0.6.x and fifty-three releases have shipped without a breaking change on disk, so the version number should say so. Two things stood between here and 1.0.0: - The deploy workflow always computed the next version as a patch bump, which made any minor or major release unreachable without publishing by hand. next-version now honours an explicit version written into the changelog's Unreleased heading, where the notes it describes already live. The pin may only move the version forward, so it cannot undo the "never fails with version already exists" guarantee the rest of that function exists to provide. - The README led with a slogan and never said plainly what the extension is. It now opens with the idea, shows the whole design in one diagram, states the reasons to use it as outcomes, and documents the logical-only setup for people who do not use dbt. Its images move off the stale external assets repo onto this one, so the icon on GitHub and the Marketplace can no longer disagree with the one that ships in the package. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014ywafwDpxdWWBt26Q1keiP
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.
Summary
scripts/release.mjs next-versiononly ever patch-bumped, so 1.0.0 was unreachable without publishing by hand. It now honours an explicit version in the changelog's## Unreleasedheading (## Unreleased — 1.0.0) and releases exactly that. The pin may only move the version forward, so a pin at or below anything already published is ignored in favour of the patch bump.media/onmain. The README-only images are excluded from the.vsix, since packaging rewrites those links to absolute URLs and a bundled copy is never read.Test plan
npm run compile— clean on both tsconfigsnpm run test— 1403 tests, 60 files, all passing (31 inrelease.test.ts, 9 of them new)npx @vscode/vsce packagesucceeds;vsce lslists 12 files (limit 60)github.comURL, so the Marketplace renders itrelease.mjs next-versionagainst a simulated marketplace payload prints1.0.0, loggingchangelog pins v1.0.0; releasing that instead of v0.6.54v1.0.0tag and GitHub Release with the.vsixattached🤖 Generated with Claude Code
https://claude.ai/code/session_014ywafwDpxdWWBt26Q1keiP