Skip to content

release: prepare Agent Switch 0.3.0 - #12

Merged
JNHFlow21 merged 1 commit into
mainfrom
codex/release-v0.3.0
Aug 12, 2026
Merged

release: prepare Agent Switch 0.3.0#12
JNHFlow21 merged 1 commit into
mainfrom
codex/release-v0.3.0

Conversation

@JNHFlow21

Copy link
Copy Markdown
Owner

Summary

  • prepare Agent Switch 0.3.0 as the next alpha release
  • synchronize CLI, package, native app, MCP server, README, and citation versions
  • document the bilingual UI, safer repository metrics, Homebrew onboarding, and trust boundaries
  • replace provider-shaped test secrets with unmistakably synthetic fixture values

Verification

  • 79 unit tests passed
  • integration reconcile test passed
  • privacy scan passed
  • source archive built
  • universal macOS app built for arm64 and x86_64, ad-hoc signature verified
  • Gitleaks/Open Source Launch strict audit: 0 errors, 0 warnings

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 17fe1fe72c

ℹ️ 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".

"X_API_SECRET=sk-secret000000000004",
"X_ACCESS_TOKEN=sk-secret000000000005",
"X_ACCESS_TOKEN_SECRET=sk-secret000000000006",
"TAVILY_API_KEY=fixture-tavily-secret",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Check the replacement fixture values for leakage

After these fixtures stop using the sk-secret prefix, the assertion at the end of this test still checks only self.assertNotIn("sk-secret", combined). Consequently, leaking any of the new credential values into a reconciled client configuration or the doctor report would no longer fail this integration test. Check every replacement value (or retain a shared sentinel) so the test continues guarding against secret disclosure.

Useful? React with 👍 / 👎.

@JNHFlow21
JNHFlow21 merged commit 31a750e into main Aug 12, 2026
7 checks passed
@JNHFlow21
JNHFlow21 deleted the codex/release-v0.3.0 branch August 12, 2026 02:20
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