Conversation
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
4b330c5 to
024785b
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
WalkthroughThis PR performs a coordinated version bump across the uploadthing monorepo, incrementing patch versions for core packages ( Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
Greptile OverviewGreptile SummaryThis is an automated release PR generated by Changesets that bumps package versions and updates changelogs following the addition of wav mime type support in PR #1257. Changes:
Release process: Confidence Score: 5/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant GH as GitHub Action
participant CS as Changesets
participant PKG as Package Registry
participant REPO as Repository
GH->>CS: Trigger release workflow
CS->>REPO: Read .changeset/wet-days-happen.md
CS->>REPO: Update package versions
CS->>REPO: Update @uploadthing/mime-types 0.3.6 → 0.3.7
CS->>REPO: Update CHANGELOG.md files
CS->>REPO: Propagate version bumps
CS->>REPO: Update @uploadthing/shared 7.1.10 → 7.1.11
CS->>REPO: Update @uploadthing/react 7.3.3 → 7.3.4
CS->>REPO: Update @uploadthing/solid 7.3.3 → 7.3.4
CS->>REPO: Update @uploadthing/svelte 7.3.3 → 7.3.4
CS->>REPO: Update @uploadthing/vue 7.3.3 → 7.3.4
CS->>REPO: Update @uploadthing/expo 7.2.6 → 7.2.7
CS->>REPO: Update uploadthing 7.7.4 → 7.7.5
CS->>REPO: Update all example dependencies
CS->>REPO: Update pnpm-lock.yaml
CS->>REPO: Delete processed changeset
CS->>GH: Create release PR
Note over GH,REPO: On merge, packages will be published to npm
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
examples/minimal-expo/package.json (1)
22-44: Update to available published versions:@uploadthing/expoand uploadthing have not been released at the specified versions.
@uploadthing/expo@7.2.7anduploadthing@7.7.5do not exist on npm. The latest published versions are@uploadthing/expo@7.2.6anduploadthing@7.7.4. Update both dependencies to their actual available versions to avoid installation failures.
🤖 Fix all issues with AI agents
In `@examples/minimal-pagedir/package.json`:
- Around line 12-16: Update the example app's package.json to use published
versions of the Uploadthing packages: change the dependency entries for
"@uploadthing/react" and "uploadthing" to the actual published versions
"@uploadthing/react@7.3.3" and "uploadthing@7.7.4". Edit the dependency list
where "@uploadthing/react" and "uploadthing" are declared so installs use valid
npm versions.
In `@examples/with-clerk-pagesdir/package.json`:
- Around line 16-20: Update the invalid package versions in package.json: change
the "@uploadthing/react" dependency from "7.3.4" to the published "7.3.3" and
change the "uploadthing" dependency from "7.7.5" to the published "7.7.4" so
installs succeed; locate the dependency entries for "@uploadthing/react" and
"uploadthing" in the file and update their version strings accordingly.
In `@examples/with-clerk-react-router/package.json`:
- Around line 16-22: The package.json specifies unavailable versions for
`@uploadthing/react` and uploadthing; update the dependency entries for
"@uploadthing/react" and "uploadthing" to use the published versions 7.3.3 and
7.7.4 respectively so npm install can resolve them; locate the dependency lines
referencing "@uploadthing/react" and "uploadthing" and change their version
strings from "7.3.4" -> "7.3.3" and "7.7.5" -> "7.7.4", then run npm install to
verify.
In `@examples/with-clerk-remix/package.json`:
- Around line 17-21: The package.json lists non-existent versions for
`@uploadthing/react` and uploadthing; update the dependency entries for
"@uploadthing/react" and "uploadthing" to the published latest versions (e.g.,
set "@uploadthing/react" to 7.3.3 and "uploadthing" to 7.7.4), save
package.json, then run your package manager (npm/yarn/pnpm) install to verify
the example installs correctly and update any lockfile if present.
| "@uploadthing/react": "7.3.4", | ||
| "next": "15.5.8", | ||
| "react": "19.2.2", | ||
| "react-dom": "19.2.2", | ||
| "uploadthing": "7.7.4" | ||
| "uploadthing": "7.7.5" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check npm registry for the exact versions
npm view `@uploadthing/react`@7.3.4 version 2>/dev/null
npm view uploadthing@7.7.5 version 2>/dev/null
npm view react@19.2.2 version 2>/dev/null
npm view react-dom@19.2.2 version 2>/dev/null
npm view next@15.5.8 version 2>/dev/nullRepository: pingdotgg/uploadthing
Length of output: 85
🌐 Web query:
@uploadthing/react 7.3.4 npm release notes changelog
💡 Result:
I couldn’t find any published @uploadthing/react 7.3.4 release/changelog entry on either npm or the upstream GitHub releases/tags—the latest 7.3.x release shown is 7.3.3. [1][2]
@uploadthing/react@7.3.3 (Aug 17, 2025) — Patch changes
- Fix: CJS interop issue (PR
#1232) [1] - Dependency update:
@uploadthing/shared@7.1.10[1]
Sources: GitHub release notes [1], npm package page (shows latest as 7.3.3) [2].
[1] https://github.com/pingdotgg/uploadthing/releases/tag/%40uploadthing%2Freact%407.3.3
[2] https://www.npmjs.com/package/%40uploadthing/react
🌐 Web query:
uploadthing 7.7.5 npm release notes changelog breaking changes
💡 Result:
As of January 23, 2026, there doesn’t appear to be an uploadthing@7.7.5 published to npm—public package trackers show 7.7.4 as the latest and list no 7.7.5 in the version history. [1], [2]
Breaking changes?
If you’re looking for breaking changes in the v7 line, the major breaking changes are documented in the v6 → v7 migration guide, including (high level): env var rename UPLOADTHING_SECRET → UPLOADTHING_TOKEN, createRouteHandler return shape changes, genUploader return shape changes, logging level changes, and config/polling behavior changes. [3]
Sources:
[1] Socket “uploadthing” package page (versions / latest) (socket.dev)
[2] npm “uploadthing” versions page snippet (shows latest tag at 7.7.4) (npmjs.com)
[3] UploadThing docs: “Migrate from v6 to v7” (docs.uploadthing.com)
Citations:
- 1: https://socket.dev/npm/package/uploadthing?utm_source=openai
- 2: https://www.npmjs.com/package/uploadthing?activeTab=versions&utm_source=openai
- 3: https://docs.uploadthing.com/v7?utm_source=openai
Fix non-existent dependency versions in the example app.
@uploadthing/react@7.3.4 and uploadthing@7.7.5 do not exist on npm. The latest published versions are @uploadthing/react@7.3.3 and uploadthing@7.7.4 respectively. Update the package.json to use these actual published versions to ensure the example app can be installed and run.
🤖 Prompt for AI Agents
In `@examples/minimal-pagedir/package.json` around lines 12 - 16, Update the
example app's package.json to use published versions of the Uploadthing
packages: change the dependency entries for "@uploadthing/react" and
"uploadthing" to the actual published versions "@uploadthing/react@7.3.3" and
"uploadthing@7.7.4". Edit the dependency list where "@uploadthing/react" and
"uploadthing" are declared so installs use valid npm versions.
| "@uploadthing/react": "7.3.4", | ||
| "next": "15.5.8", | ||
| "react": "19.2.2", | ||
| "react-dom": "19.2.2", | ||
| "uploadthing": "7.7.4", | ||
| "uploadthing": "7.7.5", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@uploadthing/react 7.3.4 npm package release
💡 Result:
I couldn’t find any evidence that @uploadthing/react 7.3.4 was ever published to npm (or tagged as a GitHub release). The latest published version shown on npm and in third-party package metadata is 7.3.3. [1][2]
🌐 Web query:
uploadthing 7.7.5 npm package release
💡 Result:
No public npm release of uploadthing@7.7.5 is visible. The latest published version shown on npm (and mirrored by jsDelivr) is 7.7.4. [1] [2]
How to verify from your machine:
npm view uploadthing version
npm view uploadthing versions --json | jq '.[-10:]'Sources:
[1] (npmjs.com)
[2] (jsdelivr.com)
Citations:
- 1: https://www.npmjs.com/package/uploadthing?utm_source=openai
- 2: https://www.jsdelivr.com/package/npm/uploadthing?utm_source=openai
🌐 Web query:
uploadthing Next.js 15 compatibility
💡 Result:
UploadThing is compatible with Next.js 15, including the App Router. The main Next.js 15–specific caveat in UploadThing’s docs is:
- If you enable Next.js 15 experimental features
pprordynamicIO, you should wrap UploadThing’s<NextSSRPlugin />in<Suspense>and callawait connection()before rendering it. [1]
Also note that Next.js 15’s upgrade guidance sets React 19 as the minimum version (so dependency/peer-dep friction you hit during a Next 15 upgrade is often React 19 ecosystem-related, not UploadThing-specific). [2]
Sources: [1] UploadThing Next.js App Router setup docs, [2] Next.js “Upgrading: Version 15” guide.
Fix non-existent package versions preventing installation.
@uploadthing/react 7.3.4 does not exist on npm (latest is 7.3.3); uploadthing 7.7.5 does not exist (latest is 7.7.4). Update lines 16 and 20 to use the published versions:
Corrected versions
"@uploadthing/react": "7.3.3",
...
"uploadthing": "7.7.4",
🤖 Prompt for AI Agents
In `@examples/with-clerk-pagesdir/package.json` around lines 16 - 20, Update the
invalid package versions in package.json: change the "@uploadthing/react"
dependency from "7.3.4" to the published "7.3.3" and change the "uploadthing"
dependency from "7.7.5" to the published "7.7.4" so installs succeed; locate the
dependency entries for "@uploadthing/react" and "uploadthing" in the file and
update their version strings accordingly.
| "@uploadthing/react": "7.3.4", | ||
| "isbot": "^5.1.19", | ||
| "react": "19.2.2", | ||
| "react-dom": "19.2.2", | ||
| "react-router": "^7.0.0", | ||
| "react-router-dom": "^7.1.3", | ||
| "uploadthing": "7.7.4" | ||
| "uploadthing": "7.7.5" |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@uploadthing/react 7.3.4 npm package version release
💡 Result:
I couldn’t find any evidence that @uploadthing/react version 7.3.4 has been released/published to npm.
The latest published version I can confirm is 7.3.3 (shown as the current version on npm, jsDelivr, and Snyk). [1][2][3]
🌐 Web query:
uploadthing 7.7.5 npm package release notes compatibility React Router 7
💡 Result:
uploadthing 7.7.5 release notes
I couldn’t find any evidence that uploadthing@7.7.5 was ever published to npm. The npm “Versions / Current Tags” view shows 7.7.4 as the latest release (and 7.7.3-canary... as canary). [1]
So, there aren’t “7.7.5 release notes” to reference (because that version doesn’t appear to exist on npm).
React Router 7 compatibility
UploadThing’s Remix setup docs explicitly say the guide is for Remix v2, but that “most steps should be the same if you’ve migrated to React Router v7,” and they point to a full RR7 example. [2]
Practical guidance
For a React Router 7 (framework-mode) app, follow the Remix setup approach and install:
uploadthing@uploadthing/react
as shown in the Remix setup doc. [2]
Sources: [1], [2]
@uploadthing/react 7.3.4 and uploadthing 7.7.5 do not exist on npm—update to 7.3.3 and 7.7.4 respectively.
Version 7.3.4 of @uploadthing/react and 7.7.5 of uploadthing have not been published. The latest available versions are 7.3.3 and 7.7.4. These versions will fail to resolve during npm install.
🤖 Prompt for AI Agents
In `@examples/with-clerk-react-router/package.json` around lines 16 - 22, The
package.json specifies unavailable versions for `@uploadthing/react` and
uploadthing; update the dependency entries for "@uploadthing/react" and
"uploadthing" to use the published versions 7.3.3 and 7.7.4 respectively so npm
install can resolve them; locate the dependency lines referencing
"@uploadthing/react" and "uploadthing" and change their version strings from
"7.3.4" -> "7.3.3" and "7.7.5" -> "7.7.4", then run npm install to verify.
| "@uploadthing/react": "7.3.4", | ||
| "isbot": "^5.1.19", | ||
| "react": "19.2.2", | ||
| "react-dom": "19.2.2", | ||
| "uploadthing": "7.7.4" | ||
| "uploadthing": "7.7.5" |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@uploadthing/react 7.3.4 npm package release notes
💡 Result:
I couldn’t find any evidence that @uploadthing/react version 7.3.4 was ever published to npm, so there are no release notes for that specific version.
As of January 23, 2026, multiple package indexes report the latest published @uploadthing/react version as 7.3.3 (not 7.3.4) [1], [2]. If you meant the main uploadthing package (not @uploadthing/react), that package’s latest version is shown as 7.7.4 [3].
Sources:
[1] https://www.jsdelivr.com/package/npm/%40uploadthing/react
[2] https://security.snyk.io/package/npm/%40uploadthing%2Freact
[3] https://www.npmjs.com/package/uploadthing
🌐 Web query:
uploadthing 7.7.5 npm package release notes
💡 Result:
There don’t appear to be any release notes for uploadthing@7.7.5 because that version is not published on npm—the latest published uploadthing version shown is 7.7.4. [1][2]
If you were actually looking for npm CLI v7.7.5 (not the uploadthing package), its changelog entry is here. [3]
Sources: [1] [2] [3]
Update @uploadthing/react and uploadthing to published versions.
The specified versions do not exist on npm:
@uploadthing/react7.3.4 does not exist (latest is 7.3.3)uploadthing7.7.5 does not exist (latest is 7.7.4)
Update both to their actual latest published versions to prevent installation failures in this example.
🤖 Prompt for AI Agents
In `@examples/with-clerk-remix/package.json` around lines 17 - 21, The
package.json lists non-existent versions for `@uploadthing/react` and uploadthing;
update the dependency entries for "@uploadthing/react" and "uploadthing" to the
published latest versions (e.g., set "@uploadthing/react" to 7.3.3 and
"uploadthing" to 7.7.4), save package.json, then run your package manager
(npm/yarn/pnpm) install to verify the example installs correctly and update any
lockfile if present.
1 participant
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@uploadthing/expo@7.2.7
Patch Changes
@uploadthing/mime-types@0.3.7
Patch Changes
d20c5baThanks @ahkhanjani! - feat: Add wav mime type
support
@uploadthing/nuxt@7.1.11
Patch Changes
@uploadthing/react@7.3.4
Patch Changes
@uploadthing/shared@7.1.11
Patch Changes
[
d20c5ba]:@uploadthing/solid@7.3.4
Patch Changes
@uploadthing/svelte@7.3.4
Patch Changes
uploadthing@7.7.5
Patch Changes
[
d20c5ba]:@uploadthing/vue@7.3.4
Patch Changes
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.