chore(main): release client-proxy 0.0.1

[e2b-release-please]

🤖 I have created a release beep boop

0.0.1 (2026-07-11)

Features

• Adding client-proxy and clickhouse to e2b-artifacts (#3210) (5686d88)

Bug Fixes

• added changelog file to trigger client-proxy buld (#3268) (70b0ee9)
• correct 3 CVES (#3218) (076823b)
• local-dev: rename API_GRPC_ADDRESS to API_INTERNAL_GRPC_ADDRESS in local dev env (#2589) (6c0bcb1)
• push client-proxy, dashboard-api, and docker-reverse-proxy image… (#2953) (1d930ee)
• reset artifacts (#3259) (93f7eb5)

---

This PR was generated with Release Please. See documentation.

[claude]

LGTM — standard automated release-please PR bumping client-proxy to 0.0.1 and generating its changelog. No code changes.

Extended reasoning...

Overview

This is an auto-generated Release Please PR touching only .release-please-manifest.json (version bump 0.0.0 → 0.0.1) and the new packages/client-proxy/CHANGELOG.md (populated with entries from already-merged PRs). No application code is modified.

Security risks

None. These are metadata/versioning files only, not executable code.

Level of scrutiny

Minimal scrutiny is appropriate — this is a mechanical, bot-generated release PR following an established pattern (release-please), consistent with prior releases for this and other packages in the repo.

Other factors

No outstanding review comments in the timeline, and the change is fully self-contained and reversible (just a version string and changelog text).