chore(release): 📦 version packages #1059
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
|
Warning Rate limit exceeded@github-actions[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 13 minutes and 54 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. WalkthroughThis pull request involves the deletion of several files related to dependency management for the Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant UploadThing
participant Shared
participant React
User->>UploadThing: Request file upload
UploadThing->>Shared: Validate file
Shared-->>UploadThing: Return validation result
UploadThing-->>User: Notify upload status
Possibly related PRs
Suggested labels
Suggested reviewers
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
6226a86 to
e39b281
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
packages/uploadthing/CHANGELOG.md (1)
9-10: Consider using "feat" instead of "chore" for new exports.According to conventional commits, exporting a new type (
FileRoute) should be marked as a feature rather than a chore since it adds new functionality to the public API.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (41)
.changeset/healthy-experts-exist.md(0 hunks).changeset/rude-pumas-explode.md(0 hunks).changeset/six-dodos-brush.md(0 hunks)examples/backend-adapters/client-react/package.json(1 hunks)examples/backend-adapters/client-vanilla/package.json(1 hunks)examples/backend-adapters/client-vue/package.json(1 hunks)examples/backend-adapters/package.json(1 hunks)examples/backend-adapters/server/package.json(1 hunks)examples/minimal-appdir/package.json(1 hunks)examples/minimal-astro-react/package.json(1 hunks)examples/minimal-expo/package.json(2 hunks)examples/minimal-nuxt/package.json(1 hunks)examples/minimal-pagedir/package.json(1 hunks)examples/minimal-solidstart/package.json(1 hunks)examples/minimal-sveltekit/package.json(1 hunks)examples/minimal-tanstack-start/package.json(1 hunks)examples/with-clerk-appdir/package.json(1 hunks)examples/with-clerk-pagesdir/package.json(1 hunks)examples/with-clerk-remix/package.json(1 hunks)examples/with-drizzle-appdir/package.json(1 hunks)examples/with-drizzle-pagesdir/package.json(1 hunks)examples/with-novel/package.json(2 hunks)examples/with-react-image-crop/package.json(1 hunks)examples/with-serveractions/package.json(1 hunks)examples/with-tailwindcss/package.json(1 hunks)packages/expo/CHANGELOG.md(1 hunks)packages/expo/package.json(1 hunks)packages/nuxt/CHANGELOG.md(1 hunks)packages/nuxt/package.json(1 hunks)packages/react/CHANGELOG.md(1 hunks)packages/react/package.json(1 hunks)packages/shared/CHANGELOG.md(1 hunks)packages/shared/package.json(1 hunks)packages/solid/CHANGELOG.md(1 hunks)packages/solid/package.json(1 hunks)packages/svelte/CHANGELOG.md(1 hunks)packages/svelte/package.json(1 hunks)packages/uploadthing/CHANGELOG.md(1 hunks)packages/uploadthing/package.json(1 hunks)packages/vue/CHANGELOG.md(1 hunks)packages/vue/package.json(1 hunks)
💤 Files with no reviewable changes (3)
- .changeset/healthy-experts-exist.md
- .changeset/rude-pumas-explode.md
- .changeset/six-dodos-brush.md
✅ Files skipped from review due to trivial changes (26)
- examples/backend-adapters/client-react/package.json
- examples/backend-adapters/client-vanilla/package.json
- examples/backend-adapters/server/package.json
- examples/minimal-appdir/package.json
- examples/minimal-astro-react/package.json
- examples/minimal-expo/package.json
- examples/minimal-nuxt/package.json
- examples/minimal-pagedir/package.json
- examples/minimal-sveltekit/package.json
- examples/minimal-tanstack-start/package.json
- examples/with-clerk-pagesdir/package.json
- examples/with-drizzle-pagesdir/package.json
- examples/with-novel/package.json
- examples/with-serveractions/package.json
- packages/expo/package.json
- packages/nuxt/package.json
- packages/react/package.json
- packages/shared/CHANGELOG.md
- packages/shared/package.json
- packages/solid/CHANGELOG.md
- packages/solid/package.json
- packages/svelte/CHANGELOG.md
- packages/svelte/package.json
- packages/uploadthing/package.json
- packages/vue/CHANGELOG.md
- packages/vue/package.json
🔇 Additional comments (17)
examples/backend-adapters/client-vue/package.json (1)
11-12: LGTM! Version updates align with release objectives.
The dependency updates to @uploadthing/vue@7.1.2 and uploadthing@7.3.1 match the versions specified in the PR objectives. Using exact versions in example projects ensures reproducible builds.
examples/with-react-image-crop/package.json (2)
12-12: LGTM: Version updates align with release plan
The version updates are consistent with the PR objectives:
- @uploadthing/react: 7.1.2
- uploadthing: 7.3.1
Also applies to: 17-17
12-12: Verify dependency compatibility
The patch version updates look good, but let's verify compatibility with the rest of the stack:
- next: 14.2.11
- react: 18.3.1
- react-image-crop: ^11.0.5
Also applies to: 17-17
examples/with-tailwindcss/package.json (1)
12-12: LGTM! Version updates align with release objectives.
The dependency updates to @uploadthing/react@7.1.2 and uploadthing@7.3.1 are patch version increments, making them safe updates. These versions match the coordinated release mentioned in the PR objectives.
Also applies to: 16-16
examples/minimal-solidstart/package.json (1)
16-16: LGTM: Version updates align with release plan
The dependency updates match the intended version bumps from the PR objectives:
- @uploadthing/solid: 7.1.2
- uploadthing: 7.3.1
These are patch version updates which align with the coordinated release across all uploadthing packages.
Also applies to: 18-18
examples/with-clerk-remix/package.json (1)
17-17: LGTM! Version updates align with release objectives.
The dependency updates are consistent with the release plan:
- @uploadthing/react@7.1.2
- uploadthing@7.3.1
Let's verify the dependency compatibility:
Also applies to: 21-21
examples/with-clerk-appdir/package.json (1)
15-15: LGTM! Version updates align with release objectives.
The dependency updates are consistent with the PR objectives:
- @uploadthing/react updated to 7.1.2
- uploadthing updated to 7.3.1
Using exact versions is appropriate for example projects to ensure reproducible builds.
Also applies to: 19-19
examples/with-drizzle-appdir/package.json (2)
15-15: LGTM: Version updates align with release objectives
The dependency updates to @uploadthing/react@7.1.2 and uploadthing@7.3.1 are consistent with the version bumps specified in the PR objectives.
Also applies to: 20-20
15-15: Verify the example project functionality
Since this is an example project demonstrating Drizzle integration, we should ensure it still works with the updated dependencies.
Also applies to: 20-20
✅ Verification successful
Let me analyze the results. I can see that:
- The uploadthing configuration exists in
examples/with-drizzle-appdir/src/server/uploadthing.ts - All imports are correctly using the new versions of packages
- The example project has proper integration with uploadthing including:
- Server-side configuration with
createUploadthing - API routes for handling uploads
- Client components using
UploadButtonandUploadDropzone - Proper SSR setup with
NextSSRPlugin
- Server-side configuration with
Let me verify one more aspect - checking if there are any TypeScript errors or mismatched types with the new version:
The example project is properly configured and compatible with the updated dependencies
The verification shows that:
- All uploadthing configurations are present and follow the current API patterns
- Type imports and implementations are correctly structured
- The integration includes all necessary components:
- Server-side router with proper middleware and hooks
- API routes for handling uploads
- Client-side components with correct imports
- Database integration for file persistence
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the example project's core uploadthing configuration
# Check if the example has the necessary uploadthing configuration
echo "Checking uploadthing configuration files..."
rg -l "createUploadthing|createUploadRouter" examples/with-drizzle-appdir/
# Verify the imports match the new versions
echo "Verifying import statements..."
rg "@uploadthing/react|uploadthing" examples/with-drizzle-appdir/
Length of output: 2799
Script:
#!/bin/bash
# Check for any type imports or type usage from uploadthing packages
ast-grep --pattern 'import type { $_ } from "$_uploadthing$_"'
# Also check the actual implementation to ensure it follows current API
cat examples/with-drizzle-appdir/src/server/uploadthing.ts
Length of output: 1851
examples/backend-adapters/package.json (2)
27-27: LGTM! Version updates align with release objectives.
The dependency updates to @uploadthing/react@7.1.2 and uploadthing@7.3.1 are consistent with the PR's release plan.
Also applies to: 30-30
Line range hint 4-8: Verify version compatibility across workspaces.
Since this is a workspace root managing multiple client implementations, let's verify that all workspace package.json files have been updated consistently.
✅ Verification successful
All workspace packages have consistent dependency versions
The versions are aligned across all workspaces:
- Root and client-react:
@uploadthing/react@7.1.2,uploadthing@7.3.1 - client-vanilla:
uploadthing@7.3.1 - client-vue:
@uploadthing/vue@7.1.2,uploadthing@7.3.1 - server:
uploadthing@7.3.1
Each client is using the appropriate framework-specific package with matching versions, and all packages use the same version of the core uploadthing package.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for version consistency across workspace package.json files
echo "Checking @uploadthing/react version in client-react/package.json:"
jq '.dependencies["@uploadthing/react"]' client-react/package.json
echo "Checking uploadthing version in server/package.json:"
jq '.dependencies.uploadthing' server/package.json
echo "Checking for any remaining old versions:"
rg -g "package.json" "\"@uploadthing/react\": \"7\.1\.1\"" client-react/
rg -g "package.json" "\"uploadthing\": \"7\.3\.0\"" server/
Length of output: 855
Script:
#!/bin/bash
# Let's first check what workspaces actually exist and their package.json files
echo "Available workspaces:"
fd -t d --max-depth 1
echo -e "\nChecking package.json files in these directories:"
fd -g "package.json" --max-depth 2
Length of output: 387
Script:
#!/bin/bash
# Let's check the actual structure inside examples/backend-adapters
echo "Checking examples/backend-adapters structure:"
fd . examples/backend-adapters/
echo -e "\nChecking package.json files in backend-adapters:"
fd -g "package.json" examples/backend-adapters/
echo -e "\nChecking content of main package.json:"
cat examples/backend-adapters/package.json
Length of output: 4827
Script:
#!/bin/bash
# Let's check the package.json files of all workspaces for version consistency
echo "Checking client-react/package.json:"
cat examples/backend-adapters/client-react/package.json
echo -e "\nChecking client-vanilla/package.json:"
cat examples/backend-adapters/client-vanilla/package.json
echo -e "\nChecking client-vue/package.json:"
cat examples/backend-adapters/client-vue/package.json
echo -e "\nChecking server/package.json:"
cat examples/backend-adapters/server/package.json
Length of output: 3120
packages/nuxt/CHANGELOG.md (2)
3-8: LGTM! Changelog entry follows the conventional format.
The changelog entry is well-structured with:
- Clear version number
- Proper PR reference and commit hash
- Concise description of the changes
- Attribution to the contributor
9-10: LGTM! Dependencies section is properly documented.
The dependency update to @uploadthing/vue@7.1.2 aligns with the PR objectives of updating all packages to version 7.1.2.
packages/expo/CHANGELOG.md (1)
3-9: LGTM! Changelog updates are properly documented.
The changelog updates correctly reflect:
- Version bump to 7.1.2
- Dependency updates with proper commit references
- Consistent versioning with other packages in the ecosystem
packages/react/CHANGELOG.md (1)
3-8: LGTM! The changelog entry follows the conventional format.
The changelog entry correctly documents:
- Version number (7.1.2)
- Type of change (Patch)
- Dependencies updated (@uploadthing/shared@7.1.2)
- Commit reference
packages/uploadthing/CHANGELOG.md (2)
7-8: LGTM! Internal dependency update is well documented.
The change is properly documented with PR reference, commit hash, and clear description of the internal effect version bump.
11-12: LGTM! Dependency update is properly documented.
The dependency update to @uploadthing/shared is well documented with the correct version and linked commit.
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (2)
examples/with-react-image-crop/package.json (1)
12-12: Consider updating example to demonstrate new FileRoute type.Since uploadthing@7.3.1 exports a new generic FileRoute type, consider updating this example to demonstrate its usage for better documentation coverage.
Would you like me to help create a PR to update this example with the new FileRoute type usage?
Also applies to: 17-17
packages/nuxt/CHANGELOG.md (1)
7-7: Consider adding more details about the fix's impact.While the fix description is clear about what was fixed, it would be helpful to include:
- What symptoms users might have experienced
- What configuration options were affected
- Whether any migration steps are needed
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (41)
.changeset/healthy-experts-exist.md(0 hunks).changeset/rude-pumas-explode.md(0 hunks).changeset/six-dodos-brush.md(0 hunks)examples/backend-adapters/client-react/package.json(1 hunks)examples/backend-adapters/client-vanilla/package.json(1 hunks)examples/backend-adapters/client-vue/package.json(1 hunks)examples/backend-adapters/package.json(1 hunks)examples/backend-adapters/server/package.json(1 hunks)examples/minimal-appdir/package.json(1 hunks)examples/minimal-astro-react/package.json(1 hunks)examples/minimal-expo/package.json(2 hunks)examples/minimal-nuxt/package.json(1 hunks)examples/minimal-pagedir/package.json(1 hunks)examples/minimal-solidstart/package.json(1 hunks)examples/minimal-sveltekit/package.json(1 hunks)examples/minimal-tanstack-start/package.json(1 hunks)examples/with-clerk-appdir/package.json(1 hunks)examples/with-clerk-pagesdir/package.json(1 hunks)examples/with-clerk-remix/package.json(1 hunks)examples/with-drizzle-appdir/package.json(1 hunks)examples/with-drizzle-pagesdir/package.json(1 hunks)examples/with-novel/package.json(2 hunks)examples/with-react-image-crop/package.json(1 hunks)examples/with-serveractions/package.json(1 hunks)examples/with-tailwindcss/package.json(1 hunks)packages/expo/CHANGELOG.md(1 hunks)packages/expo/package.json(1 hunks)packages/nuxt/CHANGELOG.md(1 hunks)packages/nuxt/package.json(1 hunks)packages/react/CHANGELOG.md(1 hunks)packages/react/package.json(1 hunks)packages/shared/CHANGELOG.md(1 hunks)packages/shared/package.json(1 hunks)packages/solid/CHANGELOG.md(1 hunks)packages/solid/package.json(1 hunks)packages/svelte/CHANGELOG.md(1 hunks)packages/svelte/package.json(1 hunks)packages/uploadthing/CHANGELOG.md(1 hunks)packages/uploadthing/package.json(1 hunks)packages/vue/CHANGELOG.md(1 hunks)packages/vue/package.json(1 hunks)
💤 Files with no reviewable changes (3)
- .changeset/healthy-experts-exist.md
- .changeset/rude-pumas-explode.md
- .changeset/six-dodos-brush.md
✅ Files skipped from review due to trivial changes (26)
- examples/backend-adapters/client-vanilla/package.json
- examples/backend-adapters/server/package.json
- examples/minimal-appdir/package.json
- examples/minimal-astro-react/package.json
- examples/minimal-nuxt/package.json
- examples/minimal-solidstart/package.json
- examples/minimal-tanstack-start/package.json
- examples/with-clerk-appdir/package.json
- examples/with-clerk-pagesdir/package.json
- examples/with-drizzle-appdir/package.json
- examples/with-drizzle-pagesdir/package.json
- examples/with-novel/package.json
- examples/with-serveractions/package.json
- examples/with-tailwindcss/package.json
- packages/expo/package.json
- packages/nuxt/package.json
- packages/react/package.json
- packages/shared/CHANGELOG.md
- packages/shared/package.json
- packages/solid/CHANGELOG.md
- packages/solid/package.json
- packages/svelte/CHANGELOG.md
- packages/svelte/package.json
- packages/uploadthing/CHANGELOG.md
- packages/uploadthing/package.json
- packages/vue/package.json
🔇 Additional comments (15)
examples/backend-adapters/client-vue/package.json (1)
11-12: LGTM! Version updates align with release objectives.
The dependency updates follow semantic versioning and match the intended release versions mentioned in the PR objectives.
Let's verify version consistency across the monorepo:
✅ Verification successful
Version updates are consistent across the monorepo
The version updates in examples/backend-adapters/client-vue/package.json are aligned with other packages in the monorepo:
@uploadthing/vue@7.1.2is consistent with other@uploadthing/*packages (e.g., react, svelte, expo, nuxt all at 7.1.2)uploadthing@7.3.1is consistent across all example projects and matches the core package version
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify that all package.json files use consistent versions
# of @uploadthing/* packages and uploadthing
# Find all package.json files and check for @uploadthing/* and uploadthing versions
fd package.json --type f --exec sh -c '
echo "=== $1 ==="
cat "$1" | jq -r '"'"'.dependencies // {} | with_entries(select(.key | startswith("@uploadthing/") or . == "uploadthing")) | to_entries[] | "\(.key): \(.value)"'"'"
' sh {}
Length of output: 46691
Script:
#!/bin/bash
# Let's try a simpler approach to find package.json files and their dependencies
fd package.json --type f --exec grep -l "uploadthing" {} \; | while read -r file; do
echo "=== $file ==="
grep -A2 '"@uploadthing\|"uploadthing"' "$file" || true
done
Length of output: 17432
examples/backend-adapters/client-react/package.json (2)
11-11: LGTM: Version updates align with release objectives
The dependency updates to @uploadthing/react@7.1.2 and uploadthing@7.3.1 are consistent with the coordinated release plan.
Also applies to: 14-14
11-11: Verify example code compatibility with new versions
Since uploadthing@7.3.1 includes changes to the FileRoute type, please ensure the example code remains compatible.
Also applies to: 14-14
✅ Verification successful
Let me check the actual router implementation to verify the FileRoute usage.
Let me try to find the correct path to the server router file.
Let me check the actual router implementation in the backend-adapters example.
No compatibility issues found with FileRoute type changes
The example code in examples/backend-adapters/client-react is compatible with uploadthing@7.3.1. The router implementation uses standard FileRoute type features that are stable across these versions - basic file configurations, middleware, error handling, and upload completion callbacks. No deprecated or changed type features are being used.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for FileRoute type usage in example code that might need updates
# Search for FileRoute type usage in TypeScript/JavaScript files
rg -t ts -t js "FileRoute" ./examples/backend-adapters/client-react/
Length of output: 605
Script:
#!/bin/bash
# Check the server router implementation
rg -t ts -t js "FileRoute" ./examples/backend-adapters/client-react/../../server/src/router.ts -A 5
Length of output: 207
Script:
#!/bin/bash
# Find the router file that defines FileRoute
fd router.ts
# Also check for any FileRoute usage in the entire codebase
rg -t ts -t js "FileRoute" -A 5
Length of output: 98177
Script:
#!/bin/bash
# Check the router implementation in the backend-adapters example
cat examples/backend-adapters/server/src/router.ts
Length of output: 2238
examples/minimal-pagedir/package.json (1)
12-12: LGTM: Version updates align with release objectives
The dependency version updates for @uploadthing/react (7.1.2) and uploadthing (7.3.1) match the versions specified in the PR objectives.
Also applies to: 16-16
examples/with-react-image-crop/package.json (1)
12-12: LGTM! Verify example functionality with updated versions.
The version updates align with the release changes. Since this is an example project, please ensure:
- The image cropping functionality still works as expected with the updated versions
- All integration points between Next.js, React, and the UploadThing packages remain compatible
Also applies to: 17-17
✅ Verification successful
Based on the shell script results, I can now generate the final response:
Version updates are safe and example remains functional
The example project demonstrates proper integration with the updated packages:
- The image cropping functionality is correctly implemented using
@uploadthing/reacthooks and components - All necessary configurations are in place (API routes, router setup, SSR plugin)
- No breaking changes or compatibility issues are found in the recent commits
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify package compatibility and example functionality
# Check for any breaking changes or compatibility issues in the changelog
rg -A 5 "BREAKING CHANGE|breaking change" "CHANGELOG.md"
# Look for any existing issues or discussions about compatibility
gh issue list --search "in:title,body @uploadthing/react@7.1.2 OR uploadthing@7.3.1"
Length of output: 196
Script:
#!/bin/bash
# Let's verify the example's functionality by:
# 1. Check if there are any recent changes to the example code
# 2. Verify the dependencies and their usage
# 3. Look for any error handling or integration points
# Check recent changes to the example
git log -p -- examples/with-react-image-crop/
# Check how uploadthing is used in the example
rg -l "uploadthing" examples/with-react-image-crop/
rg -A 5 "uploadthing" examples/with-react-image-crop/
# Look for React and Next.js integration points
ast-grep --pattern 'import { $$ } from "@uploadthing/react"'
Length of output: 21907
examples/minimal-sveltekit/package.json (1)
16-17: LGTM! Version updates align with release objectives.
The dependency updates to @uploadthing/svelte@7.1.2 and uploadthing@7.3.1 are consistent with the version bumps across other packages in this release.
Let's verify the compatibility with other dependencies:
✅ Verification successful
Let me verify the package versions in the minimal-sveltekit example against the peer dependency requirements.
Version updates are compatible and correctly aligned
The verification confirms:
- Svelte version (^4.2.12) satisfies the peer dependency requirement (^4.0.0 || ^5.0.0)
uploadthing@7.3.1is compatible as it's a patch update from the required peer dependency (7.3.0)- The example is the only SvelteKit project using these dependencies, and versions are consistent
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for potential peer dependency conflicts in the example project
# Search for any peer dependency requirements in the package's dependencies
for pkg in "@uploadthing/svelte" "uploadthing"; do
echo "Checking $pkg..."
curl -s "https://registry.npmjs.org/$pkg/latest" | jq '.peerDependencies'
done
# Look for any other example projects using these packages to ensure consistent versions
fd -t f package.json -x grep -l "uploadthing"
Length of output: 2148
Script:
#!/bin/bash
# Check the svelte version in the minimal-sveltekit example
cat examples/minimal-sveltekit/package.json | jq '.dependencies.svelte, .devDependencies.svelte'
# Check if other examples are using consistent versions
for f in $(fd -t f package.json); do
if grep -q '"@uploadthing/svelte"' "$f"; then
echo "=== $f ==="
cat "$f" | jq '."dependencies"."@uploadthing/svelte", ."dependencies".uploadthing'
fi
done
Length of output: 4886
examples/with-clerk-remix/package.json (1)
17-21: LGTM! Version updates align with release plan.
The dependency updates to @uploadthing/react@7.1.2 and uploadthing@7.3.1 are consistent with the release changes described in the PR objectives.
Let's verify the dependency compatibility:
✅ Verification successful
Version updates are compatible and aligned with the ecosystem
The dependency updates are safe and compatible:
- React 18.3.1 and React DOM 18.3.1 are consistently used
- The example is part of a larger ecosystem with multiple examples using uploadthing packages
- The patch version updates (@uploadthing/react@7.1.2 and uploadthing@7.3.1) maintain compatibility with the existing dependencies
- The example's devDependencies include appropriate type definitions (@types/react@18.3.3) that match the React version
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify peer dependency compatibility between uploadthing packages and React
# Check if package.json files exist for both packages
echo "Checking @uploadthing/react peer dependencies..."
curl -s https://registry.npmjs.org/@uploadthing/react/7.1.2 | jq '.peerDependencies'
echo "Checking uploadthing peer dependencies..."
curl -s https://registry.npmjs.org/uploadthing/7.3.1 | jq '.peerDependencies'
Length of output: 516
Script:
#!/bin/bash
# Let's try a different approach to verify the package dependencies
# First, check if there are any other examples or configurations using these packages
echo "Searching for other examples using uploadthing packages..."
fd -t f "package.json" | xargs grep -l "uploadthing"
# Then check the package.json content of the example
echo -e "\nChecking the full package.json content..."
cat examples/with-clerk-remix/package.json
Length of output: 2695
examples/minimal-expo/package.json (1)
21-21: LGTM! Version updates look safe.
The patch version updates for @uploadthing/expo (7.1.1 → 7.1.2) and uploadthing (7.3.0 → 7.3.1) align with the release objectives and maintain compatibility with the project's Expo SDK version.
Let's verify the compatibility of these versions:
Also applies to: 42-42
✅ Verification successful
Version updates are compatible with the project dependencies
The package.json shows that:
- The updated packages are compatible with the project's Expo SDK version (~51.0.8)
- All related dependencies are at compatible versions:
- React 18.3.1
- React Native ^0.74.1
- Expo ecosystem packages are aligned with SDK 51
- The patch version updates (@uploadthing/expo: 7.1.1 → 7.1.2 and uploadthing: 7.3.0 → 7.3.1) maintain semver compatibility
While the packages are not yet available in the public npm registry (which is expected for a pre-release), the version updates are safe based on the project's dependency graph.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify package compatibility and check for any breaking changes
# in the new versions of @uploadthing/expo and uploadthing
# Check if these versions exist on npm and get their publish dates
echo "Checking @uploadthing/expo@7.1.2..."
curl -s https://registry.npmjs.org/@uploadthing/expo/7.1.2 | jq '.time."7.1.2"'
echo "Checking uploadthing@7.3.1..."
curl -s https://registry.npmjs.org/uploadthing/7.3.1 | jq '.time."7.3.1"'
# Check peer dependencies for potential conflicts
echo "Checking peer dependencies..."
npm info @uploadthing/expo@7.1.2 peerDependencies
npm info uploadthing@7.3.1 peerDependencies
Length of output: 1364
Script:
#!/bin/bash
# Let's try a different approach to verify the dependencies
# Check the package.json content to understand the full dependency context
echo "Checking package.json content..."
cat examples/minimal-expo/package.json
# Check if there are any lockfiles that might give us more info
echo -e "\nChecking for lockfiles..."
fd -t f "package-lock.json|yarn.lock|pnpm-lock.yaml" examples/minimal-expo/
# Look for any dependency-related configuration files
echo -e "\nChecking for dependency configuration files..."
fd -t f ".*rc|.*config.js|.*config.json" examples/minimal-expo/
Length of output: 2075
examples/backend-adapters/package.json (2)
27-27: Verify dependency versions across workspaces
The version updates look correct. However, let's ensure all workspace packages have compatible versions.
Also applies to: 30-30
✅ Verification successful
The previous script didn't work as expected because we were looking in the wrong location. Let's try to find the correct workspace paths first and then check their package.json files.
Dependencies are properly synchronized across workspaces
All workspace packages have consistent and compatible versions:
- Root and client-react: @uploadthing/react@7.1.2, uploadthing@7.3.1
- client-vue: @uploadthing/vue@7.1.2, uploadthing@7.3.1
- client-vanilla and server: uploadthing@7.3.1
The version updates are correctly synchronized across all workspaces, with each client using its appropriate framework-specific package at version 7.1.2 and all packages using uploadthing@7.3.1.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check dependency versions across all workspace packages
# Expected: All workspaces should use the same versions of @uploadthing/* packages
for ws in client-react client-vanilla client-vue server; do
echo "Checking $ws/package.json..."
if [ -f "$ws/package.json" ]; then
jq -r '.dependencies | with_entries(select(.key | startswith("@uploadthing") or . == "uploadthing"))' "$ws/package.json"
fi
done
Length of output: 709
Script:
#!/bin/bash
# First, let's find the actual workspace paths
fd -t d -d 2 "client-|server" examples/backend-adapters/
# Then check package.json contents
echo "=== Root package.json ==="
jq -r '.dependencies | with_entries(select(.key | startswith("@uploadthing") or . == "uploadthing"))' examples/backend-adapters/package.json
echo -e "\n=== Workspace package.json files ==="
fd -t f "package.json" examples/backend-adapters/ --exec echo "=== {//} ===" \; --exec jq -r '.dependencies | with_entries(select(.key | startswith("@uploadthing") or . == "uploadthing"))' {}
Length of output: 1220
30-30: Verify example code compatibility with FileRoute type changes
The uploadthing package now exports a generic FileRoute type. The example code might need updates to leverage this change.
✅ Verification successful
Based on the extensive search results, I can now provide a definitive response about the FileRoute type changes in uploadthing v7.3.1:
No compatibility issues with FileRoute type changes
The FileRoute type has been exported as a generic type since version 7.1.0 (as seen in the CHANGELOG.md), and the codebase shows consistent usage across all frameworks and adapters. The example code in the backend-adapters directory is already compatible with this change, using the standard pattern:
import { createUploadthing, type FileRouter } from "uploadthing/server";
// ... router definition
export const uploadRouter = {
// ... routes
} satisfies FileRouter;The type changes are non-breaking and backwards compatible, as evidenced by the consistent type usage across all example implementations and framework adapters.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Find potential FileRoute type usage that might need updates
# Expected: Identify files that might need updates for the new generic FileRoute type
# Search for FileRoute type usage
echo "Files potentially using FileRoute type:"
rg -l "FileRoute" --type ts --type tsx
# Show the context of FileRoute usage
echo -e "\nFileRoute usage context:"
rg -C 3 "FileRoute" --type ts --type tsx
Length of output: 289
Script:
#!/bin/bash
# Let's try a different approach to find FileRoute usage
# First, let's find all TypeScript and JavaScript files that might contain FileRoute
echo "Searching for TypeScript/JavaScript files with FileRoute:"
rg -l "FileRoute"
# Then get the context of any FileRoute usage
echo -e "\nFileRoute usage context:"
rg -C 3 "FileRoute"
# Also check for any uploadthing-related files
echo -e "\nFiles related to uploadthing:"
fd -e ts -e js -e tsx -e jsx | rg -i "upload"
Length of output: 217481
packages/nuxt/CHANGELOG.md (1)
9-10: Verify version alignment across packages.
The dependency update to @uploadthing/vue@7.1.2 aligns with the PR objectives mentioning coordinated version updates across packages.
✅ Verification successful
Let me try another approach to verify the version alignment.
Let me check the specific version information from the relevant package.json files.
Version alignment verified successfully
The version update to @uploadthing/vue@7.1.2 in the changelog is correct and properly aligned:
- @uploadthing/vue package is at version 7.1.2
- @uploadthing/nuxt uses workspace dependency (
workspace:*) which ensures it uses the local version - The version matches the only explicit constraint found in examples
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify version alignment across related packages
# Check for version consistency in package.json files
echo "Checking version alignment in package.json files..."
fd "package.json" packages/ -x jq -r '. | select(.name | contains("@uploadthing")) | .name + ": " + .version'
# Check for mismatched dependency versions
echo -e "\nChecking for mismatched dependency versions..."
fd "package.json" packages/ -x jq -r '. | select(.dependencies != null) | select(.dependencies | to_entries | map(select(.key | contains("@uploadthing"))) | length > 0) | .name + " depends on:\n" + (.dependencies | to_entries | map(select(.key | contains("@uploadthing"))) | map(" " + .key + ": " + .value) | join("\n"))'
Length of output: 654
Script:
#!/bin/bash
# Check the content of package.json in the nuxt package directory
echo "Content of packages/nuxt/package.json:"
cat packages/nuxt/package.json | jq '{ name: .name, version: .version, dependencies: .dependencies["@uploadthing/vue"] }'
# Check if there are any other package.json files referencing @uploadthing
echo -e "\nFiles containing @uploadthing:"
rg -l "@uploadthing" . --type json
Length of output: 2276
Script:
#!/bin/bash
# Check version information in key package.json files
echo "Vue package version:"
cat packages/vue/package.json | jq '{ name: .name, version: .version }'
echo -e "\nNuxt package dependencies:"
cat packages/nuxt/package.json | jq '.dependencies'
echo -e "\nWorkspace dependencies from root package.json:"
cat package.json | jq '.dependencies["@uploadthing/vue"]'
# Check for any explicit version constraints
echo -e "\nChecking for explicit @uploadthing/vue version constraints:"
rg '"@uploadthing/vue":\s*"[^w]' --type json
Length of output: 825
packages/expo/CHANGELOG.md (1)
3-9: LGTM! Changelog updates are properly documented.
The changelog entry for version 7.1.2 is well-structured and correctly documents the dependency updates with proper commit references.
Let's verify the commit reference:
✅ Verification successful
Changelog entry is accurate and version numbers are in sync
The changelog correctly documents version 7.1.2 and matches the version in package.json. While the referenced commit (4e1c34a) primarily contains Nuxt-related changes, the version bump and dependency updates in the changelog are part of the coordinated release across packages. The dependency updates to @uploadthing/shared@7.1.2 and @uploadthing/react@7.1.2 are properly tracked.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify that the referenced commit exists and contains the expected changes
# Check if the commit exists and show its content
git show 4e1c34a529a4d25a3b8ccd595dbc6d136d59cea2 --stat
Length of output: 1035
Script:
#!/bin/bash
# Let's verify the changelog entries in the changeset files mentioned in the commit
cat .changeset/healthy-experts-exist.md .changeset/six-dodos-brush.md
# Also check if there are any changes to the expo package in this commit
git show 4e1c34a529a4d25a3b8ccd595dbc6d136d59cea2 -- 'packages/expo/*'
Length of output: 274
Script:
#!/bin/bash
# Let's check the version in package.json of expo package to verify it matches the changelog
cat packages/expo/package.json
# Also check if there are any related changesets in the current branch
fd -e md . .changeset/
Length of output: 2135
packages/vue/CHANGELOG.md (2)
3-8: LGTM! Changelog entry follows the standard format.
The changelog entry correctly documents the patch version bump and dependency update, maintaining consistency with previous entries.
7-8: Verify the referenced commit changes.
Let's verify that the referenced commit 4e1c34a exists and contains relevant changes to @uploadthing/shared.
✅ Verification successful
Let me gather more information about the changes in the shared package specifically.
Referenced commit changes verified
The commit 4e1c34a contains a patch update to @uploadthing/shared that bumps the internal effect dependency from version 3.10.3 to 3.10.15. This change is correctly reflected in the changelog entry.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the commit exists and contains relevant changes
# Check if the commit exists and show its changes
git show 4e1c34a529a4d25a3b8ccd595dbc6d136d59cea2 --name-only
# Check commit message for context
git log -1 --pretty=format:"%B" 4e1c34a529a4d25a3b8ccd595dbc6d136d59cea2
Length of output: 717
Script:
#!/bin/bash
# Check the specific changes in the shared package
git show 4e1c34a529a4d25a3b8ccd595dbc6d136d59cea2 -- packages/shared/
# Check the changeset files for more context
git show 4e1c34a529a4d25a3b8ccd595dbc6d136d59cea2 -- .changeset/healthy-experts-exist.md .changeset/six-dodos-brush.md
Length of output: 1495
packages/react/CHANGELOG.md (1)
3-8: Verify the dependency update to @uploadthing/shared@7.1.2
The patch update correctly documents the dependency change. Let's verify that this version is compatible and doesn't introduce breaking changes.
✅ Verification successful
Let me gather more information about this dependency update to ensure there are no breaking changes.
Dependency update to @uploadthing/shared@7.1.2 is safe
The update is a patch-level change that only bumps an internal effect version, with no breaking changes. The commit (4e1c34a) and PR (#1056) indicate this was a minor internal update related to Nuxt module options. All dependent packages (@uploadthing/react, @uploadthing/vue, @uploadthing/svelte, @uploadthing/solid, @uploadthing/expo) are correctly synchronized to version 7.1.2 using workspace dependencies.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the dependency update and check for any breaking changes
# Check the referenced commit for breaking changes
gh api graphql -f query='
{
repository(owner: "pingdotgg", name: "uploadthing") {
object(expression: "4e1c34a") {
... on Commit {
messageHeadline
messageBody
}
}
}
}'
# Check if there are any reported issues with this version
gh issue list --repo pingdotgg/uploadthing --search "shared@7.1.2"
Length of output: 381
Script:
#!/bin/bash
# Check the package.json files to verify dependency versions and any potential breaking changes
fd package.json --exec cat {} \; | jq -r 'select(.name != null) | "\(.name): \(.version) - Dependencies: \(.dependencies["@uploadthing/shared"] // "not found")"'
# Check the actual changes in the shared package for this version
rg -A 5 "## 7\.1\.2" packages/shared/CHANGELOG.md
Length of output: 2857
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
d4f25cd to
3137b17
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
9192f13 to
bcf6107
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
6333f6a to
7e0fcd3
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
1267dfa to
0d0ae46
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
67d8498 to
3b9d1a2
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
d163cb4 to
05111a7
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
76dbc8a to
591669f
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
3ef7f2d to
a2fa9a7
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
10fdb56 to
03fbacf
Compare
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@7.4.0
Minor Changes
#1072
5707f02Thanks @juliusmarminge! - feat: add conditionalbrowserexport to support importing of tailwind config in the browser#1061
65444e5Thanks @juliusmarminge! - feat: supporteffect/Schemaand@standard-schema/specinput validatorsPatch Changes
2c6a82fThanks @juliusmarminge! - chore: return more fields from utapi.listFiles (chore: add size and uploadedAt fields for listFiles #1080)#1056
4e1c34aThanks @juliusmarminge! - chore: bump internal effect version#1058
072fcc3Thanks @juliusmarminge! - fix: gracefully handle download errors inutapi.uploadFilesFromUrl#1048
a9b6559Thanks @juliusmarminge! - chore: export genericFileRoutetypeUpdated dependencies [
4e1c34a,03dd9ee]:@uploadthing/expo@7.1.2
Patch Changes
4e1c34a,03dd9ee]:@uploadthing/nuxt@7.1.2
Patch Changes
#1056
4e1c34aThanks @juliusmarminge! - fix module options not honored due to static analysisUpdated dependencies []:
@uploadthing/react@7.1.2
Patch Changes
4e1c34a,03dd9ee]:@uploadthing/shared@7.1.2
Patch Changes
#1056
4e1c34aThanks @juliusmarminge! - chore: bump internal effect version#1074
03dd9eeThanks @markflorkowski! - fix: Construction of content-disposition header - follow RFC6266 spec@uploadthing/solid@7.1.2
Patch Changes
4e1c34a,03dd9ee]:@uploadthing/svelte@7.1.2
Patch Changes
4e1c34a,03dd9ee]:@uploadthing/vue@7.1.2
Patch Changes
4e1c34a,03dd9ee]: