Repository navigation
Release 1.5.0 - #9
Merged
Merged
Conversation
Vanilla mode has been on main since 1 September but never shipped: the release workflow only publishes when package.json carries a version whose tag does not exist yet, and that merge did not bump it. So npm has served 1.4.0 without the feature for a week. Also fixes two stale changelog links that predate this release. There was no link reference for 1.4.0 at all, and Unreleased still compared from v1.3.0.
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.
Ships vanilla mode, which has been on
mainsince 1 September but never reached npm.Why it did not ship
The release workflow publishes only when
package.jsoncarries a version whose tag does not exist yet. The vanilla mode merge (b900aee) did not bump the version, so the job skipped and npm has served 1.4.0 without the feature for a week.Measured:
npm view @rousan/ccal versionreturns1.4.0, published 2026-08-07, and its tarball contains no file mentioning vanilla.What is in it
--vanilla, already written and merged, unchanged by this PR[Unreleased]section promoted to[1.5.0][1.4.0]at all, and[Unreleased]still compared fromv1.3.0Minor rather than patch because it carries a new feature, and not major because it is additive - existing agentic behaviour is unchanged.
Verification
pnpm typecheckandpnpm buildboth clean. There is no test suite in this repo, so I ran the feature instead: two servers from the built output, one normal and one with--vanilla, and comparedGET /v1/models.supported_parameters: ["tools", "reasoning"]--vanilla:supported_parameters: ["reasoning"]Which is what the changelog entry claims the mode does.
What merging this does
Publishes
@rousan/ccal@1.5.0to npm and creates the tag and GitHub Release. That is irreversible. It also triggers the unconditional Pages deploy of the landing page, as every push tomainhere does.