Skip to content

fix: Use multipart/form-data in PUT /api/v1/profile#1415

Merged
neet merged 1 commit into
mainfrom
put-api-v1-profile-formdata
May 3, 2026
Merged

fix: Use multipart/form-data in PUT /api/v1/profile#1415
neet merged 1 commit into
mainfrom
put-api-v1-profile-formdata

Conversation

@neet

@neet neet commented May 3, 2026

Copy link
Copy Markdown
Owner

related to #1413

I have not verified if this works since Mastodon 4.6.0 hasn't been officially released yet

@pkg-pr-new

pkg-pr-new Bot commented May 3, 2026

Copy link
0e6ba0c_ " data-view-component="true" class="dropdown-item btn-link"> Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/masto@1415

commit: 0e6ba0c

@github-actions

github-actions Bot commented May 3, 2026

Copy link
Copy Markdown
Contributor

size-limit report 📦

Path Size
rest 3.9 KB (+0.06% 🔺)
streaming 3.86 KB (0%)
oauth 3.9 KB (+0.16% 🔺)

@neet neet merged commit 5d57e4f into main May 3, 2026
7 checks passed
@neet neet deleted the put-api-v1-profile-formdata branch May 3, 2026 06:06
@cheeaun

cheeaun commented May 4, 2026

Copy link
Copy Markdown

FYI I've verified this works on my local dev with mastodon.social server (v4.6.0-nightly.2026-05-01), by pointing package.json to use "masto": "https://pkg.pr.new/masto@1415". Uploading an avatar, it runs masto.v1.profile.update, sent with PUT as (binary) with multipart/form-data content-type 🙇‍♂️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants