Skip to content

chore: release v0.14.1#22

Merged
Destynova2 merged 1 commit intodevelopfrom
release-plz-2026-03-08T10-13-14Z
Mar 8, 2026
Merged

chore: release v0.14.1#22
Destynova2 merged 1 commit intodevelopfrom
release-plz-2026-03-08T10-13-14Z

Conversation

@Destynova2
Copy link
Copy Markdown
Contributor

🤖 New release

  • grob: 0.14.0 -> 0.14.1 (✓ API compatible changes)
Changelog

0.14.1 - 2026-03-08

Fixed

  • add prompt-caching-scope-2026-01-05 beta flag


This PR was generated with release-plz.

@Destynova2 Destynova2 merged commit a418ce6 into develop Mar 8, 2026
15 checks passed
Destynova2 added a commit that referenced this pull request Mar 16, 2026
Critical:
- #9 #10: Replace hard-coded HMAC key with random session key when
  GROB_DLP_SECRET is unset (unpredictable pseudonyms by default)

High:
- #11 #12: Cap Vec::with_capacity to 1024 in OpenAI transform
  (prevents uncontrolled allocation from malicious input)
- #17 #18 #19: Add path traversal check in token_store persist()
  (reject ".." in file path)
- #6 #7 #8: Stop logging full response bodies in OpenAI provider
  (log length instead, truncate to 200 chars on parse error)
- #13 #14: Warn at construction if OAuth token_url uses plaintext HTTP
- #15 #16: Warn at construction if Gemini base_url uses plaintext HTTP
  (new warn_if_cleartext() helper in providers/mod.rs)
- #20 #21 #22: Annotate benchmark TLS cert bypass with lgtm comment
  (intentional: benchmarks use self-signed certs)
- #3: Avoid flowing API key through format string in preset info
- #4 #5: Remove secret values from test assertion messages

Medium:
- #1: Add explicit permissions block to release-plz workflow

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@Destynova2 Destynova2 deleted the release-plz-2026-03-08T10-13-14Z branch March 30, 2026 19:52
Destynova2 added a commit that referenced this pull request Apr 21, 2026
Adds the OAuth 2.0 Device Authorization Grant (RFC 8628) so machines
without a browser — CI runners, SSH sessions, containers — can complete
an OAuth flow by entering a short user_code on a second device.

* New `auth::device_code` module implements the RFC 8628 pair:
  `start()` hits the device-authorization endpoint, `poll_until_approved()`
  honors the server `interval`/`slow_down`/`expired_token` hints.
* `auto_flow::setup_oauth_interactive` now takes the device-code path
  when `GROB_OAUTH_HEADLESS=1` is set and the provider supports it
  (currently Google/Gemini). Anthropic and OpenAI Codex still use the
  browser flow; a log line explains the fallback.
* Unit tests cover interval clamping, unsupported-provider rejection,
  and env-var parsing.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Destynova2 added a commit that referenced this pull request Apr 21, 2026
Adds the OAuth 2.0 Device Authorization Grant (RFC 8628) so machines
without a browser — CI runners, SSH sessions, containers — can complete
an OAuth flow by entering a short user_code on a second device.

* New `auth::device_code` module implements the RFC 8628 pair:
  `start()` hits the device-authorization endpoint, `poll_until_approved()`
  honors the server `interval`/`slow_down`/`expired_token` hints.
* `auto_flow::setup_oauth_interactive` now takes the device-code path
  when `GROB_OAUTH_HEADLESS=1` is set and the provider supports it
  (currently Google/Gemini). Anthropic and OpenAI Codex still use the
  browser flow; a log line explains the fallback.
* Unit tests cover interval clamping, unsupported-provider rejection,
  and env-var parsing.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant