Replace changesets with bumpy v1 (#632)

* replace changesets with bumpy (our own version)

* update CI workflows for bumpy v1

- release.yaml: use BUMPY_GH_TOKEN for version branch push/PR creation,
  switch to OIDC trusted publishing (drop NPM_TOKEN), add explicit build step
- test.yaml: add bumpy ci check step to comment release plan on PRs

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* upgrade bumpy to v1 and configure vscode extension publishing

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* upgrade bumpy to v1.1, clean up vscode plugin npm publishing

- Upgrade @varlock/bumpy to 1.1.0
- Remove README.npm.md and prepack/postpack scripts (no longer published to npm)
- Revert unrelated regex change in diagnostics-core.ts
- Add $schema and comments support to bumpy config
- Update vscode settings for bumpy config file association

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* update release-preview script for bumpy v1

Replace hardcoded vscode plugin filter with generic skipNpmPublish
check from bumpy config. Add comments explaining that bumpy status
includes pending releases from main for consistent preview packages.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: theoephraim

.bumpy/README.md

@@ -0,0 +1,63 @@
+# 🐸 Bumpy
+
+This directory is used by [bumpy](https://bumpy.varlock.dev) to manage versioning and changelogs.
+
+Bumpy is a modern versioning tool for JavaScript/TypeScript projects (monorepos and single packages). It uses **bump files** — small markdown files in this directory — to declare pending version changes. These files are consumed during the release process to compute version bumps, update changelogs, and publish packages.
+
+## How it works
+
+1. When you make a change that should trigger a release, create a bump file (typically one per PR)
+2. Bump files accumulate on your main branch until you're ready to release
+3. At release time, bumpy merges all pending bumps into a release plan, updates versions and changelogs, and publishes packages
+
+## Creating bump files
+
+### Interactive
+
+```bash
+bunx bumpy add
+```
+
+### Non-interactive (useful for AI-assisted development)
+
+```bash
+bunx bumpy add --packages "package-name:minor,other-package:patch" --message "Description of changes" --name "my-change"
+```
+
+### By hand
+
+Create a `.md` file in this directory with YAML frontmatter mapping package names to bump levels (`major`, `minor`, `patch`, or `none`), and a markdown body for the changelog entry:
+
+```markdown
+---
+'package-name': minor
+---
+
+Added a new feature.
+```
+
+### From conventional commits
+
+```bash
+bunx bumpy generate
+```
+
+### Empty bump files
+
+For PRs that intentionally don't need a release (docs, CI, etc.):
+
+```bash
+bunx bumpy add --empty --name "docs-update"
+```
+
+## Keeping bump files up to date
+
+As a PR evolves, make sure its bump file stays in sync. If the scope of changes grows (e.g., a patch becomes a new feature), update the bump level and description to match. Reviewers and AI assistants should treat the bump file as part of the PR — just like tests and docs.
+
+## Files in this directory
+
+- `_config.json` — bumpy configuration
+- `README.md` — this file
+- `*.md` (other than README.md) — pending bump files
+
+📖 Full documentation: https://bumpy.varlock.dev

.bumpy/_config.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "../node_modules/@varlock/bumpy/config-schema.json",
+  "baseBranch": "main",
+  "changelog": ["github", { "internalAuthors": ["theoephraim", "philmillman"] }],
+  "packages": {
+    // this is the vscode extension
+    "env-spec-language": {
+      "skipNpmPublish": true,
+      "buildCommand": "bun run package",
+      "publishCommand": "bun run publish:vsce && bun run publish:ovsx"
+    }
+  }
+}

.bumpy/changesets-to-bumpy.md

@@ -0,0 +1,2 @@
+---
+---

…ngeset/debounce-unchanged-env-restart.md .bumpy/debounce-unchanged-env-restart.md.changeset/debounce-unchanged-env-restart.md renamed to .bumpy/debounce-unchanged-env-restart.md .changeset/debounce-unchanged-env-restart.md renamed to .bumpy/debounce-unchanged-env-restart.md

@@ -13,16 +13,16 @@ bun run lint:fix
 
 ### 2. Always Add a Changeset
 ```bash
-bun run changeset:add
+bun run bumpy:add
 ```
 - Every PR NEEDS a changeset
-- If only internal changes (docs, CI, tests, config) you can use an empty changeset
+- If only internal changes (docs, CI, tests, config) you can use an empty changeset: `bumpy add --empty`
 - IF the work affects any published packages, select them
 - Choose the correct version bump type (patch/minor/major)
 - Write a clear, user-facing description
-- **If bun fails**: Use `npm run changeset:add` as fallback
+- For non-interactive (AI/CI): `bumpy add --packages "varlock:patch" --message "description" --name "changeset-name"`
 
-Example changeset:
+Example changeset (`.bumpy/<name>.md`):
 ```
 ---
 "varlock": patch
@@ -51,7 +51,7 @@ bun run build:libs
 | Task | Command | When |
 |------|---------|------|
 | Lint & Fix | `bun run lint:fix` | After every code change |
-| Add Changeset | `bun run changeset:add` | When changing published packages |
+| Add Changeset | `bun run bumpy:add` | When changing published packages |
 | Build Check | `bun run build:libs` | Before completing any task |
 | Run Tests | `bun run test:ci` | When changing logic |
 

.changeset/scan-explicit-paths.md .bumpy/scan-explicit-paths.md.changeset/scan-explicit-paths.md renamed to .bumpy/scan-explicit-paths.md

@@ -25,22 +25,21 @@ When implementing a new feature or making significant changes, the PR should inc
   - `/reference/*.mdx` - API reference documentation
 
 ### 4. Changeset
-- **Always** create a changeset file in `.changeset/` directory
+- **Always** create a changeset file in `.bumpy/` directory
 - Use semantic versioning: `minor` for new features, `patch` for bug fixes, `major` for breaking changes
 - Include clear description of the changes, but keep it short
-- Format: Create a new `.md` file in `.changeset/` with:
+- Use non-interactive mode: `bumpy add --packages "varlock:minor" --message "description" --name "changeset-name"`
+- Or create a `.md` file in `.bumpy/` manually:
   ```markdown
   ---
   "varlock": <minor|patch|major>
   ---
-  
+
   Brief description of the change
   (or use bullet list for multiple changes)
-- An empty changeset is needed for changes that do not affect any published packages
-  ```markdown
-  ---
-  ---
   ```
+- An empty changeset is needed for changes that do not affect any published packages:
+  `bumpy add --empty`
 
 ### 5. Code Review
 - Run `bun run lint:fix` and then resolve remaining lint errors
@@ -52,12 +51,11 @@ When implementing a new feature or making significant changes, the PR should inc
 - Fix any discovered vulnerabilities
 - Include security summary in PR
 
-## Changeset Commands
+## Bumpy Commands
 
 Available commands (defined in root `package.json`):
-- `bun run changeset:add` - Interactively create a changeset (not available in CI)
-- `bun run changeset:version` - Bundle changesets into version bumps
-- `bun run changeset:publish` - Publish packages to npm
+- `bun run bumpy:add` - Interactively create a changeset
+- `bumpy add --packages "pkg:bump" --message "desc" --name "name"` - Non-interactive (AI/CI)
 
 ## Documentation Structure