`openai-python` `v2.34.0` adds Admin API Key support and env-based headers

Project and user admin fields expanded, and auth paths were cleaned up. Upgrade if you automate admin flows or juggle multiple credentials; otherwise this is mostly a stability release.

[ KEY POINTS ]

projects gets external_key_id, and users adds email and metadata params, which reduces custom wrappers around admin provisioning flows.
Per-endpoint Admin API Key support landed with related auth fixes, including no bearer fallback and preserved selected credentials during requests.
OPENAI header configuration via env is now supported, useful for shared deploy setups where runtime header injection was previously manual.
Type and transport fixes cover Response timestamps, prompt_cache_retention, Azure auth headers, and multipart file array field names.

Originalgithub.com/openai/openai-python/releases/tag/v2.34.0Read original →

// related

#0001
#0001Other GeekNews2 hours ago
`Bambu Studio` Faces Broad AGPLv3 Compliance Challenge
40radar
Bambu Studio3D printing slicer — based on PrusaSlicer
Copyleft obligations can reach bundled dynamic libraries and install info. If you fork AGPLv3 software, partial source drops are not enough.
- AGPLv3 Corresponding Source covers code needed to generate, install, run, and modify the work, not just visible app changes.
- A tightly coupled proprietary networking library may need source disclosure if it is dynamically linked into the modified app.
- Forking strong-copyleft projects for commercial software demands release-process checks before binaries ship.
Source: news.hada.io/topic?id=29694Read original →
FIG-0011:1
40radar
FIG-0011:1
#0002
#0002Other GeekNews2 hours ago
What's New in `Chrome` from Google I/O 2026
50radar
The web is shifting from human clicks to agent-driven browsing and AI-assisted development. Worth tracking before specs turn into defaults.
- Paul Kinlan, who leads Chrome DevRel, framed the last 6 months as a fast reset for web development workflows.
- One axis is preparing sites for agents that browse on users' behalf. Structured, machine-readable UX will matter more.
- Another axis is developer tooling. Chrome is positioning DevTools around AI-assisted debugging and building, not just inspection.
- The source is short and lacks API-level details, so this is a watchlist item rather than something to implement today.
Source: news.hada.io/topic?id=29693Read original →
FIG-0021:1
50radar
FIG-0021:1
#0003
#0003Other GeekNews5 hours ago
JavaScript Debloating: Complexity, Libraries, and the WASM Trade-off
40radar
Small browser UIs can become heavy fast. WebAssembly helps, but async bridging to the JavaScript event loop keeps the payoff situational.
- Nested syntax and callbacks make JavaScript complexity grow quickly; bundle size is often a design outcome, not just tooling noise.
- Small UI surfaces can still pull in many libraries. Dependency defaults deserve review before reaching for another package.
- WebAssembly opens the browser to other languages, but Pyodide-style async event-loop integration adds real coordination cost.
Source: news.hada.io/topic?id=29675Read original →
FIG-0031:1
40radar
FIG-0031:1

`openai-python` `v2.34.0` adds Admin API Key support and env-based headers

// related

`Bambu Studio` Faces Broad AGPLv3 Compliance Challenge

What's New in `Chrome` from Google I/O 2026

JavaScript Debloating: Complexity, Libraries, and the WASM Trade-off