chore(main): release 0.2.1

[e2b-generated-code-auto-fixer]

🤖 I have created a release beep boop

0.2.1 (2026-09-16)

Bug Fixes

• publish: build the image for arm64 too (#533) (8ca65cd)

---

This PR was generated with Release Please. See documentation.

[claude]

LGTM, standard release-please version bump.

What was reviewed: confirmed the diff is limited to the version bump (0.2.0 → 0.2.1) in .release-please-manifest.json and package.json, plus the corresponding CHANGELOG.md entry for the arm64 build fix (#533) — no application/source code changed.

Extended reasoning...

Overview

This PR is an automated release-please version bump: .release-please-manifest.json and package.json both update the version field from 0.2.0 to 0.2.1, and CHANGELOG.md gets a new entry documenting the already-merged bug fix (#533, arm64 image builds). No application or source code is touched.

Security risks

None. There is no logic change, no new dependencies, no permission or auth-related code involved — purely metadata/version string updates.

Level of scrutiny

Low. This is a mechanical, bot-generated release commit following an established convention (release-please). The pre-existing odd-looking "<<<<<<< Next.js" etc. keys in package.json are unchanged by this diff (verified they exist identically in both the base commit and HEAD) and are out of scope for this review.

Other factors

No CODEOWNERS restriction apparent for these root-level release files, no outstanding review comments in the timeline, and the bug hunter found no issues. This is exactly the kind of small, self-contained, unambiguous change the approval guidelines describe as approvable.

[e2b-generated-code-auto-fixer]

🤖 Created releases:

• v0.2.1

🌻