Skip to content

chore(release): prepare 0.7.11 - #177

Merged
pierreraby merged 1 commit into
mainfrom
release/0.7.11
Oct 28, 2026
Merged

pierreraby merged 1 commit into
mainfrom
release/0.7.11

Conversation

@pierreraby

Copy link
Copy Markdown
Collaborator

Summary

Release preparation for 0.7.11 (stable, latest): version bump plus a dated changelog section for the catalog refresh merged as #175 and the OMP compatibility fix merged as #176.

Content of this release:

  • capability snapshot pinned to command-code@1.88.1, which finally publishes metadata for two models the CLI left undocumented: moonshotai/Kimi-K3.1-Pro gains image input, reasoning and low/high/max efforts (it kept conservative text-only defaults since 0.7.10), and the newly advertised gpt-6.1-terra arrives with image input, reasoning and five selectable efforts. No model-specific output limit is published for either, so both keep the 65,536-token default.
  • reviewed display pricing for gpt-6.1-terra, verified against the official pricing page on 2026-10-28: $1 input / $5 output / $0.05 cache read / $1.25 cache write per million tokens up to 272K tokens, and $2 / $7.5 / $0.1 / $2.5 above that threshold. Without the entry the model displayed zero cost and the daily catalog job failed with missing-local-price; the snapshot now covers all 94 advertised models.
  • test-omp-compat.mjs no longer counts Oh My Pi's skill-description pre-passes as agent requests, so the compatibility job stays meaningful on OMP 18.13 hosts instead of failing on an unmodified main. Test-only.

No behavior, API or configuration changes in the provider itself; catalog/pricing data plus a test fix.

Verification (local, on f287b39)

  • npm test: PASS (all 21 suites, including [pi-local] and [omp-compat] against OMP 18.13.2).
  • npm run format:check: PASS. npm audit --audit-level=moderate: 0 vulnerabilities.
  • npm pack --dry-run: 32 files, 77.2 kB packed. git diff --check: clean.
  • node --test tests/test-release.mjs: 45/45, so the release rules accept the dated changelog section and the version/lockfile agreement.
  • On the data commit chore(models): refresh catalog to 1.88.1 and price GPT-6.1 Terra #175: check:commandcode-catalog Current vs 1.88.1, check:commandcode-pricing PASS, no drift.

Release plan

Merge into main, push the annotated tag v0.7.11 on the merge commit, then let the tag-triggered workflow publish through npm Trusted Publishing. Verify npm latest, registry tarball integrity, SLSA provenance and the GitHub Release afterwards. next stays on 0.7.3-next.0.

Bump the package to 0.7.11 and date the changelog section for the catalog
refresh (command-code@1.88.1 plus reviewed pricing for gpt-6.1-terra) and the
OMP skill-description pre-pass fix in the compatibility suite.
@github-actions

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@github-actions

Copy link
Copy Markdown
Contributor

Memory benchmark

Compared base e4e40bb with PR head f287b39 on the same GitHub-hosted darwin runner. Lower values are better.

Metric Base PR PR − Base Change
Stable RSS 120.3 MiB ± 1.2 MiB 121.3 MiB ± 0.5 MiB +0.4 MiB ± 0.9 MiB +0.3%
Physical footprint 66.2 MiB ± 0.2 MiB 66.3 MiB ± 0.4 MiB +0.1 MiB ± 0.6 MiB +0.1%
Physical peak 76.3 MiB ± 0.9 MiB 76.3 MiB ± 0.8 MiB +0.5 MiB ± 1.5 MiB +0.6%

Interpretation: No metric shows a clear Base-to-PR difference beyond its measured run-to-run variation.

Extension overhead above pi baseline

Metric Base overhead PR overhead Difference
Stable RSS +5.7 MiB ± 1.6 MiB +7.5 MiB ± 0.9 MiB +0.4 MiB ± 0.9 MiB
Physical footprint +4.5 MiB ± 0.6 MiB +4.8 MiB ± 0.6 MiB +0.1 MiB ± 0.6 MiB
Physical peak +5.3 MiB ± 1.2 MiB +5.1 MiB ± 0.6 MiB +0.5 MiB ± 1.5 MiB

Values are medians of 6 alternating, paired runs. The value after ± is the median absolute deviation (MAD). Each process was sampled 12 times after a 2500 ms warm-up.

Environment: pi 0.84.4, Bun 1.4.0, darwin arm64. RSS comes from ps; physical footprint and peak come from macOS footprint.

This is a comparative signal, not a pass/fail threshold. GitHub-hosted runner noise can affect absolute values.

@pierreraby
pierreraby merged commit f4ab05c into main Oct 28, 2026
15 checks passed
@pierreraby
pierreraby deleted the release/0.7.11 branch October 28, 2026 09:09
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.

1 participant