Conversation
The publish pipeline was failing because stale changeset files from a prior release were never cleaned up after CI consumed them. This caused `changeset version` to produce version numbers already on npm, so the build-and-check step found nothing to publish. Fix: - Remove 8 stale changeset .md files that described already-published work - Sync all 4 package.json versions to match npm (core@0.2.0, cli@0.3.0, mcp@0.4.0, opencode@0.5.1) - Update internal dependency references (kibi-core: ^0.2.0, kibi-cli: ^0.3.0) - Add 3 fresh changesets covering unpublished work since last release: typed facts & snip discovery bundle (minor), bug fixes & snip compatibility (patch), code quality refactors (patch)
There was a problem hiding this comment.
Pull request overview
This PR unblocks the release workflow by aligning workspace package versions with what’s already published on npm and replacing stale Changesets entries that were causing changeset version to propose already-released versions.
Changes:
- Sync published versions across workspace packages (
kibi-core,kibi-cli,kibi-mcp,kibi-opencode) and update internal dependency ranges accordingly. - Remove stale
.changeset/*.mdfiles that described already-published work. - Add three fresh changesets to capture unpublished work since the last release.
Reviewed changes
Copilot reviewed 15 out of 15 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| packages/core/package.json | Bump kibi-core version to match npm (0.2.0). |
| packages/cli/package.json | Bump kibi-cli version to match npm (0.3.0) and update kibi-core dependency range. |
| packages/mcp/package.json | Bump kibi-mcp version to match npm (0.4.0) and update kibi-cli / kibi-core dependency ranges. |
| packages/opencode/package.json | Bump kibi-opencode version to match npm (0.5.1). |
| .changeset/typed-facts-and-discovery.md | New changeset capturing typed facts + discovery bundle work (minor/patch bumps). |
| .changeset/bugfixes-and-compatibility.md | New changeset capturing bugfixes + Node 24 compatibility work (patch bumps). |
| .changeset/code-quality-refactors.md | New changeset capturing internal refactors (patch bumps). |
| .changeset/typed-fact-schema-sync.md | Removed stale changeset (already accounted for in published releases). |
| .changeset/strict-fact-adoption-guidance.md | Removed stale changeset (already accounted for in published releases). |
| .changeset/node24-import-with.md | Removed stale changeset (already accounted for in published releases). |
| .changeset/mcp-only-policy.md | Removed stale changeset (already accounted for in published releases). |
| .changeset/fix-staged-symbol-resolution.md | Removed stale changeset (already accounted for in published releases). |
| .changeset/docs-discovery-bundle-refresh.md | Removed stale changeset (already accounted for in published releases). |
| .changeset/discovery-bundle-tools.md | Removed stale changeset (already accounted for in published releases). |
| .changeset/code-gardening-2026-03-26.md | Removed stale changeset (already accounted for in published releases). |
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.
The publish pipeline was failing because stale changeset files from a prior release were never cleaned up after CI consumed them. This caused
changeset versionto produce version numbers already on npm, so the build-and-check step found nothing to publish.Fix: