Uh oh!
There was an error while loading. Please reload this page.
This repository was archived by the owner on May 15, 2026. It is now read-only.
fix: bump @roo-code/types metadata version to 1.111.0 after revert regression - #11588
Merged
Merged
Conversation
hannesrudolph
approved these changes
Feb 18, 2026
hannesrudolph
marked this pull request as ready for review
February 18, 2026 22:17
hannesrudolph
requested review from
cte, daniel-lxs, jr and mrubens
as code ownersFebruary 18, 2026 22:17
ghost
force-pushed
the
fix/bump-types-metadata-version-1.112.0
branch
from
February 18, 2026 22:25
549542b to
a6c0c9aComparejr
approved these changes
Feb 18, 2026
Uh oh!
There was an error while loading. Please reload this page.
Merged
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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 revert commit 6cfa82f rolled the repo back, causing
packages/types/npm/package.metadata.jsonto regress from1.111.0to1.106.0. The current latest published version on npm is 1.111.0, so the next publish from main would attempt to bump1.106.0->1.107.0, which already exists.The publish script (
publish-npm.cjs) reads the version frompackage.metadata.json, then auto-bumps vianpm version minorbefore publishing. So the metadata file needs to reflect the last published version (1.111.0), and the script will correctly bump to 1.112.0 on the next publish.Changes
packages/types/npm/package.metadata.json:"version": "1.106.0"->"version": "1.111.0"View task on Roo Code Cloud