Repository navigation
chore(release): align all @comvi/* packages to v0.2.0 - #14
Conversation
Manual override of changesets output: drop the `fixed` group from .changeset/config.json (it escalated minor → major in 0.x — see changesets/changesets#1011 for related), add an aligning changeset that bumps every @comvi/* package as minor, then run `pnpm changeset version`. Three plugins (plugin-fetch-loader, plugin-in-context-editor, plugin-locale-detector) still escalated to 1.0.0 because changesets treats peer-dep `workspace:*` as exact-match (assemble-release-plan line 283), so a minor bump on @comvi/core is "out of range" and forces consumer major. The flag onlyUpdatePeerDependentsWhenOutOfRange doesn't help here for the same reason. Manually corrected those three: package.json version 1.0.0 → 0.2.0, CHANGELOG `## 1.0.0` → `## 0.2.0`, and one stale dep reference (`@comvi/[email protected]` → `0.2.0` inside plugin-in-context-editor's 0.2.0 section). Historical 1.0.0 entries in older sections of CHANGELOGs are left untouched — those are real prior versions. Result: all 12 @comvi/* packages now ship as 0.2.0. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (31)
💤 Files with no reviewable changes (6)
📝 WalkthroughWalkthroughThis PR coordinates a 0.2.0 release across all ChangesCoordinated 0.2.0 Release
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
…onfig RC review #14. Nothing validated `pull.emptyDir`, and a JSON string is truthy, so `"emptyDir": "false"` enabled the clear that deletes the local catalog — the option set to the exact opposite of what the file said. The same mistake in `strictParams` silently re-enabled strict parameters. Both must now be a boolean or absent, and the `pull` / `push` sections must be objects. Validation happens in ConfigLoader.load, before a command opens a socket or touches the translations directory, and the message names the key and the type received. `push.forceMode` already had its own check against the four allowed modes. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01XCpEDJzjm499ShssuoimHb
Summary
Manual release of v0.2.0 across all 12
@comvi/*packages, bypassing the bot release PR (#6) because changesets' default behaviour produced unintended1.0.0versions.What changed
pnpm changeset version(withfixed: []and a synth changeset bumping every@comvi/*as minor).1.0.0due to a known changesets quirk: peer-depworkspace:*is treated as exact-match (assemble-release-plan source line 283, related issue #1011), so any minor bump of@comvi/coreis "out of range" and forces peer consumers to major. The escape-hatch___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.onlyUpdatePeerDependentsWhenOutOfRange: truedoesn't help here for the same reason.plugin-fetch-loader,plugin-in-context-editor,plugin-locale-detector): version1.0.0 → 0.2.0inpackage.json,## 1.0.0 → ## 0.2.0in CHANGELOG, plus one stale cross-reference insideplugin-in-context-editor's 0.2.0 section.1.0.0entries in older CHANGELOG sections are left untouched — those reflect real prior versions.Result
All 12 packages now ship at exactly
0.2.0:@comvi/cli,@comvi/core,@comvi/next,@comvi/nuxt,@comvi/react,@comvi/solid,@comvi/svelte,@comvi/vue,@comvi/vite-plugin@comvi/plugin-fetch-loader,@comvi/plugin-in-context-editor,@comvi/plugin-locale-detectorWhat lands in the v0.2.0 CHANGELOG
@comvi/cli—.envauto-load,namespaces/localesconfig filters, locales/--locale rename, doc-URL fix, drop unused@comvi/coredep,ConfigLoader.create()regression fix@comvi/svelte— strip TypeScript from published.sveltefiles@comvi/vite-plugin— drop dead doc links@comvi/*— coordinated bump for version alignmentTest plan
pnpm -w run test— 23/23 task groups pass across the workspacepnpm -w run build— 12/12 build tasks succeedpnpm -w run typecheck— 29/29 packages cleanpackage.jsonversions aligned to0.2.01.0.0refs in any new## 0.2.0CHANGELOG sectionworkspace:*cross-package refs preserved (lockfile unchanged)After merge
Releasewill see no.changeset/*.mdfiles and runchangeset publishdirectly → npm publishes 12 × 0.2.0 with provenance.develop ← mainafter the publish completes so both branches converge at 0.2.0.🤖 Generated with Claude Code
Summary by CodeRabbit
Release Notes
New Features
.envfile; configure with--env-file,--no-env-file, orCOMVI_DEBUGflagspullandpushoperationsBug Fixes
Version Updates