Skip to content

chore(release): prepare 0.8.4 - #219

Merged
pierreraby merged 1 commit into
mainfrom
release/0.8.4
Nov 15, 2026
Merged

pierreraby merged 1 commit into
mainfrom
release/0.8.4

Conversation

@pierreraby

Copy link
Copy Markdown
Collaborator

Summary

Prepare stable patch 0.8.4 from merged main a84f239:

Validation

  • Full npm test PASS with both hosts required and COMMANDCODE_TRANSPORT unset. Local hosts: Pi 1.5.2, OMP 18.16.0, Bun 1.4.4, Node 26.8.1. Host integration uses loopback mocks, not paid/live inference.
  • Entrypoint typecheck against installed Pi declarations PASS.
  • Release validation contract PASS for v0.8.4/latest, correct notes and contributor section; npm test includes release-rule tests.
  • Format and git diff --check PASS; npm audit: 0 vulnerabilities.
  • npm pack --dry-run: 32 files, ~85.5 kB. No packed-package installation performed locally; package/registry checks remain part of the authorized tag-triggered release workflow.
  • Latest CLI catalog check PASS (1.89.1); public live pricing check PASS for all 98 models, no unknown prices or unreviewed expired promotions.
  • No migration required; provider ID, credentials namespace and default routing unchanged. Pi only refreshes near expiry; OMP also forces refresh after 401. Known follow-up: host-level revoked-key failover integration coverage and refresh timeout budget alignment.
  • Preflight: npm latest=0.8.3, next=0.7.3-next.0; latest GitHub Release v0.8.3; npm 0.8.4 E404 and remote v0.8.4 tag absent; no active release run.

Current maintenance is being handled solo. Merged OAuth code received independent review and exact-head checks. Auxiliary workflow-hardening findings concern unchanged baseline workflows and remain separately documented, not suppressed by this PR.

Authorization boundary

This PR is preparation only. Do not merge or create/push v0.8.4 without the operator's explicit authorization. Merging alone does not publish; publication must use RELEASE.md's tag-triggered OIDC workflow. No production installation update is included.

@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 a84f239 with PR head 08c3984 on the same GitHub-hosted darwin runner. Lower values are better.

Metric Base PR PR − Base Change
Stable RSS 107.8 MiB ± 0.8 MiB 105.9 MiB ± 0.4 MiB -1.8 MiB ± 1.4 MiB -1.6%
Physical footprint 61.1 MiB ± 0.6 MiB 60.7 MiB ± 0.7 MiB -0.7 MiB ± 1.7 MiB -1.1%
Physical peak 71.7 MiB ± 0.9 MiB 72.1 MiB ± 1.2 MiB +0.2 MiB ± 1.5 MiB +0.3%

Interpretation: Differences larger than their measured MAD: Stable RSS -1.8 MiB ± 1.4 MiB.

Extension overhead above pi baseline

Metric Base overhead PR overhead Difference
Stable RSS +5.5 MiB ± 1.2 MiB +4.3 MiB ± 1.4 MiB -1.8 MiB ± 1.4 MiB
Physical footprint +3.0 MiB ± 0.6 MiB +2.7 MiB ± 0.9 MiB -0.7 MiB ± 1.7 MiB
Physical peak +3.0 MiB ± 0.5 MiB +3.0 MiB ± 1.2 MiB +0.2 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.4, 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 3b60d88 into main Nov 15, 2026
15 checks passed
@pierreraby
pierreraby deleted the release/0.8.4 branch November 15, 2026 12:12
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