Repository navigation
release: prepare BB VariaQ plugin 0.6.1 - #12
Conversation
- Bump package identity to 0.6.1 (package.json, package-lock.json, lib/schema.ts BB_PLUGIN_VARIAQ_VERSION, README package identity). - Add the 0.6.1 changelog section for the PR #11 maintenance fixes (structured CLI comparison errors, SECURITY.md advisory accuracy, regression coverage) and date the 0.6.0 section to its release date. - No compatibility, dependency, or functional changes; VariaQ 0.6.x, 0.8.x, and 0.8.0rc1 support is unchanged from 0.6.0.
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6c015d2fd4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Address the Codex review finding: the pre-publication checkout must not record 0.6.1 with a release date while the README states it is unreleased. The date is applied to the entry at publication time, matching the 0.6.0 release flow.
|
@codex review |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Summary
Maintenance release preparation for v0.6.1. Follows PR #11 (merged as 5825c37), which resolved the PR #10 review findings. No compatibility, dependency, or functional changes.
package.json,package-lock.json,lib/schema.ts(BB_PLUGIN_VARIAQ_VERSION), README package identity line.Local verification (all passed)
npm run typecheck— cleannpm run test:unit— 104 passed, 1 skippednpm run sdk:check— SDK pin 0.6.37, host 0.6.37npm run build— dist/server.js + server.meta.json with pluginVersion 0.6.1npm pack --dry-run— bb-plugin-variaq-0.6.1.tgz, 12 files, shasum 33d950f0…npm audit --omit=dev— 0 vulnerabilities (production)npm audit— 5 dev-only (3 high, 2 moderate), unchanged and documented in SECURITY.mdVARIAQ_TEST_PROJECT=/home/aaron/quantum-lab/variaq VARIAQ_TEST_VERSION=0.8.0): 24 passed, 2 skipped (CUDA-Q/GPU opt-in)VARIAQ_TEST_CUDAQ=1): 25 passed, 1 skipped (GPU only)plugin update, VariaQ auto-discovery works, solve/analyze/report operations verified, and the merged P2 fix is live (--compare bogusnow returns a structured error with valid-value hints)Notes
VARIAQ_TEST_GPU=1); no GPU pass is claimed.