Skip to content

RespondKit 0.6.1 — attachments on the hosted API and aligned composer controls

Choose a tag to compare

View all tags
@lhr0909 lhr0909 released this 14 Oct 13:49
v0.6.1
7d20d33
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

RespondKit 0.6.1

Release notes

A patch release for two problems found on SubPorter's web widget with 0.6.0.

  • Attachments work on the hosted API. The production Worker had no ATTACHMENTS R2 binding, so every upload answered "Attachments are not configured." (and email ingress could not store raw mail). apps/api/wrangler.jsonc now binds ATTACHMENTS to the respondkit-attachments-staging bucket in the staging environment (api.respondkit.dev) and respondkit-attachments by default. Uploads and downloads both pass through the Worker (PUT /v1/attachments/:id/parts/:part, GET /v1/files/:token), so the bucket stays private and needs no CORS rule.
  • Web composer alignment. The attach button was 36px (icon-lg) beside the 44px message box and send button, and the row bottom-aligns, so the paperclip sat low. It now has the same 44px box, and neither button shrinks.

Upgrade and compatibility

Use 0.6.1 for the npm packages. No API or protocol change; 0.6.0 clients work against the fixed API.

Operator checklist

  1. Create the bucket once: cd apps/api && pnpm exec wrangler r2 bucket create respondkit-attachments-staging.
  2. Deploy the API: cd apps/api && pnpm exec wrangler deploy --env staging, then upload a file from a test widget and open its download link.
  3. Publish GitHub release v0.6.1, which runs the npm publish workflow.
Assets 2
Loading