Skip to content

chore: bump version to 0.1.10 - #45

Merged
echobt merged 8 commits into
mainfrom
chore/bump-version-0.1.10
Sep 8, 2026
Merged

chore: bump version to 0.1.10#45
echobt merged 8 commits into
mainfrom
chore/bump-version-0.1.10

Conversation

@echobt

@echobt echobt commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Automated version bump from 0.1.9 to 0.1.10 (intro.gif LOCK GO via #44).

Merge this PR (do not push to main). version-bump.yml then tags v0.1.10; release.yml builds artifacts and publish-r2.yml publishes to software.cortex.foundation.

@greptile-apps

greptile-apps Bot commented Sep 7, 2026

Copy link
Copy Markdown

Greptile Summary

Summary

  • The CLI release version is updated to 0.1.10, but the SDK package metadata remains at 0.1.9.
  • The SDK version-consistency test fails because those values differ.
  • This change is not safe to merge until the SDK package version is synchronized.

Confidence Score: 4/5

Not safe to merge: the SDK version-consistency test fails until packages/sdk/package.json matches the CLI release version.

A reproduced test failure shows that the release version sources are inconsistent.

Files Needing Attention: packages/sdk/package.json

T-Rex T-Rex Logs

What T-Rex did

  • Ran locked Cargo metadata resolution on both the parent and updated commits and confirmed both runs succeeded with the same Cargo.lock checksum.
  • Created a proof for a posted P1 finding and linked it to the corresponding review comment.
  • Executed the locked-release validation script and observed the before/after outputs; the lock SHA stayed the same, cortex-cli updated from 0.1.9 to 0.1.10, and no tracked files were modified.
  • Generated a second proof for another posted P1 finding and linked it to the corresponding review comment.
  • Compared the SDK version contract between PR-state and a temporary fix and proposed bump to 0.1.10; this is a P1 issue and not a security issue.

View all artifacts

T-Rex Ran code and verified through T-Rex

Comments Outside Diff (1)

  1. General comment

    P1 SDK package version was not updated with VERSION_CLI

    • Bug
      • VERSION_CLI contains 0.1.10, while packages/sdk/package.json declares 0.1.9. The contract test at packages/sdk/test/client.test.mjs:106-109 fails with AssertionError: '0.1.9' !== '0.1.10' (exit 1). In a temporary untracked SDK copy, setting only the metadata version from the copied VERSION_CLI makes the exact same test pass (exit 0).
    • Cause
      • The version-bump commit changed the CLI/Rust version sources but omitted the SDK package metadata version.
    • Fix
      • Update packages/sdk/package.json:3 from "0.1.9" to "0.1.10" and retain the existing consistency test.

    T-Rex Ran code and verified through T-Rex

Reviews (1): Last reviewed commit: "chore: bump version to 0.1.10" | Re-trigger Greptile

Comment thread VERSION_CLI
cursoragent and others added 6 commits September 7, 2026 23:50
Keep @cortexlm/sdk on VERSION_CLI and use the full 40-col
budget so v0.1.10 still shows the mid splash hints.

Co-authored-by: Mathis <echobt@users.noreply.github.com>
Co-authored-by: Mathis <echobt@users.noreply.github.com>
Ellipsize v{version} instead of dropping @ files · ! shell
so 40x12 chrome stays complete for v0.1.10 and later.

Co-authored-by: Mathis <echobt@users.noreply.github.com>
Move version-width splash helpers into splash_chrome.rs so lock_boards.rs
and lock_proof.rs stay at or below the QUALITY_BASE sizes.

Co-authored-by: Mathis <echobt@users.noreply.github.com>
v0.1.10 plus the mid legend is exactly 40 columns; only a longer
version is shortened.

Co-authored-by: Mathis <echobt@users.noreply.github.com>
@echobt
echobt merged commit 3035361 into main Sep 8, 2026
16 checks passed
@echobt
echobt deleted the chore/bump-version-0.1.10 branch September 8, 2026 00:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants