chore(main): release 2.1.0-rc.6

[github-actions]

🤖 I have created a release beep boop

2.1.0-rc.6 (2024-12-01)

Features

• add --logs command to rivet actor create (#584) (762eb98)
• add env selector (#585) (ca90737)
• allow creating actors with build tags & add durable actors (#580) (da8619a)
• pretty-print api errors (#593) (66fd193)

Bug Fixes

• actor logs base64 (#578) (31bb18b)
• correctly extend tags to builds (#581) (f5c588b)
• deno-embed: accept github token to increase rate limits (#566) (7d59328)
• fix searching for deno lockfile (#598) (0545d90)
• gracefully handle all ffi unwraps (#562) (9cb8253)
• revert back to using native cp (#569) (598d2e5)
• toolchain: disable term color by default for backend (#564) (a39d231)
• toolchain: fix backend-embed build on windows (#565) (e106174)

Chores

• add --out flag to build_cross.ts (#573) (a19b225)
• add back all platforms to cross build (#572) (3e2ec00)
• add deno uploads (#577) (8bef249)
• add manual js uploads (#576) (0bf6e5a)
• add sentry integration (#592) (d7a6508)
• add support for tar images for js (#582) (5930aa1)
• allow tailing both stdout and stderr & log when actor shuts down (#589) (1f4c38f)
• auto-open browser on login (#588) (f4a1f74)
• backend: format (#568) (ace84b7)
• bundle postgres & fix github rate limit issue (#567) (a6e373d)
• clean up cli error handling (#591) (8126ac2)
• don't prompt env selection if there's only one env (#595) (3f6cf8e)
• fix deploy progress bar (#590) (c124282)
• fix js lints (#597) (17b1561)
• impl rivet init (#594) (a5e4ac6)
• remove legacy rivet modules code (postgres, backend, etc) (#575) (d9d47f4)
• rename build patch-tags (#596) (21853b2)
• rename primary command signin -> login (#587) (37041a2)
• support ctrl c in logs (#586) (5f1f034)
• temporarily fix tag patching (#599) (59c6e2f)
• toolchain: allow hooking to existing game server process (#563) (ba8a189)
• toolchain: rename default buildx builder from rivet_cli -> rivet_toolchain (#560) (6d18ff8)
• update sdk (#579) (2899185)

---

This PR was generated with Release Please. See documentation.

[graphite-app]

Your org requires the Graphite merge queue for merging into main

Add the label “merge-queue” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.