-
Notifications
You must be signed in to change notification settings - Fork 326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(release): 📦 version packages #1041
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 4 minutes and 8 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 updates various Changes
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 (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
⛔ Files ignored due to path filters (1)
pnpm-lock.yaml
is excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (27)
.changeset/little-boxes-taste.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
(1 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
(1 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/nuxt/CHANGELOG.md
(1 hunks)packages/nuxt/package.json
(1 hunks)packages/uploadthing/CHANGELOG.md
(1 hunks)packages/uploadthing/package.json
(1 hunks)
💤 Files with no reviewable changes (1)
- .changeset/little-boxes-taste.md
✅ Files skipped from review due to trivial changes (21)
- examples/backend-adapters/client-react/package.json
- examples/backend-adapters/client-vanilla/package.json
- examples/backend-adapters/client-vue/package.json
- examples/backend-adapters/package.json
- examples/backend-adapters/server/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-tanstack-start/package.json
- examples/with-clerk-appdir/package.json
- examples/with-clerk-pagesdir/package.json
- examples/with-clerk-remix/package.json
- examples/with-drizzle-appdir/package.json
- examples/with-drizzle-pagesdir/package.json
- examples/with-novel/package.json
- examples/with-react-image-crop/package.json
- examples/with-serveractions/package.json
- examples/with-tailwindcss/package.json
- packages/nuxt/package.json
- packages/uploadthing/package.json
🔇 Additional comments (5)
examples/minimal-solidstart/package.json (2)
18-18
: LGTM: Version bump to uploadthing@7.2.1
The version update aligns with the PR objectives for the release.
Line range hint 14-14
: Verify version compatibility between uploadthing packages
Please ensure that @uploadthing/solid@7.1.0
is compatible with uploadthing@7.2.1
.
Also applies to: 18-18
✅ Verification successful
Version compatibility verified between uploadthing packages
The @uploadthing/solid
package explicitly declares uploadthing@^7.2.0
as a peer dependency. Since uploadthing@7.2.1
satisfies this version constraint (7.2.1 > 7.2.0 within the same major version), these versions are compatible.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for version compatibility documentation or constraints
# Test 1: Search for peer dependency requirements
rg -A 5 '"peerDependencies".*uploadthing"'
# Test 2: Look for version compatibility notes in README
rg -i 'compatibility|version requirement' README.md
# Test 3: Check package.json files in the monorepo for version patterns
fd -e json -x jq -r '.dependencies.uploadthing + " in " + input_filename' {} 2>/dev/null
Length of output: 3850
Script:
#!/bin/bash
# Let's check the peer dependencies in @uploadthing/solid package
# Check package.json of @uploadthing/solid for peer dependencies
rg -A 10 '"peerDependencies"' ./packages/solid/package.json
# Check if there are any version constraints or compatibility notes
rg -i "version|compatibility" ./packages/solid/README.md
# Let's also check the changelog for any breaking changes
rg -i "breaking" ./packages/solid/CHANGELOG.md
# Check the main uploadthing package for any solid-specific version requirements
rg -i "solid" ./packages/uploadthing/package.json
Length of output: 523
examples/minimal-sveltekit/package.json (1)
17-17
: LGTM! Version bump aligns with release objectives.
The update of uploadthing
from 7.2.0 to 7.2.1 matches the PR's purpose of releasing packages with the Tailwind-related patch.
Let's verify version compatibility:
✅ Verification successful
Version bump to uploadthing@7.2.1 is safe to proceed
Based on the verification results:
- The example project maintains a consistent pattern of using uploadthing@7.2.1 with @uploadthing/svelte@7.1.0
- No explicit version constraints or peer dependency requirements were found
- The patch version bump (7.2.0 → 7.2.1) follows semantic versioning principles, indicating backward compatibility
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check if @uploadthing/svelte version is compatible with uploadthing
# Look for any version compatibility requirements or breaking changes
# Search for version compatibility documentation
rg -l "uploadthing.*compatibility|version.*requirement" README.md docs/
# Check if other example projects maintain specific version relationships
fd package.json --exec jq -r 'select(.dependencies != null) | select(.dependencies["uploadthing"] != null and .dependencies["@uploadthing/svelte"] != null) | "uploadthing: \(.dependencies.uploadthing), @uploadthing/svelte: \(.dependencies["@uploadthing/svelte"])"'
Length of output: 387
Script:
#!/bin/bash
# Let's check for any version constraints or peer dependencies in package.json files
fd package.json --exec jq -r 'select(.peerDependencies != null) | select(.peerDependencies["uploadthing"] != null) | "File: {}, uploadthing peer dependency: \(.peerDependencies.uploadthing)"'
# Search for any version-related comments or documentation
rg -i "version|peer|dependency" -A 2 -B 2 "uploadthing"
# Check commit history for any version compatibility notes
git log -p --grep="uploadthing"
Length of output: 333
packages/nuxt/CHANGELOG.md (1)
3-11
: LGTM! Changelog entry is well-formatted and accurate.
The changelog entry correctly documents:
- The patch version increment to 7.1.1
- The dynamic stylesheet/Tailwind plugin addition from PR fix: nuxt module tailwind support #1033
- The dependency update to @uploadthing/vue@7.1.0
packages/uploadthing/CHANGELOG.md (1)
3-7
: LGTM! The changelog entry accurately reflects the changes.
The changelog entry for version 7.2.1:
- Correctly references PR fix: nuxt module tailwind support #1033 and the contributor
- Accurately describes the patch change for dynamically adding either a stylesheet or tailwind plugin based on
@nuxtjs/tailwindcss
installation - Matches the PR objectives
examples/minimal-appdir/package.json
Outdated
@@ -13,7 +13,7 @@ | |||
"next": "14.2.11", | |||
"react": "18.3.1", | |||
"react-dom": "18.3.1", | |||
"uploadthing": "7.2.0" | |||
"uploadthing": "7.2.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codebase verification
Version inconsistency found in profile-picture example
The version bump to 7.2.1
is correct, but there's an inconsistency in the examples:
examples/profile-picture/package.json
uses^7.0.0
while all other examples use7.2.1
- This inconsistency should be addressed to maintain version parity across examples
🔗 Analysis chain
LGTM! Version bump looks correct.
The upgrade from uploadthing@7.2.0
to uploadthing@7.2.1
aligns with the PR objectives for this release.
Let's verify version consistency across all example projects:
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify that all example projects are using the same version of uploadthing
# Test: Check uploadthing versions across all package.json files
# Expect: All should be using version 7.2.1
fd package.json examples/ --exec grep -l "uploadthing" {} | xargs jq -r '.dependencies.uploadthing // empty'
Length of output: 249
Script:
#!/bin/bash
# Let's identify which example has the ^7.0.0 version to check if it's intentional
fd package.json examples/ --exec grep -l "uploadthing" {} | xargs -I {} sh -c 'echo "=== {}:" && jq -r ".dependencies.uploadthing" {}'
Length of output: 1348
415694a
to
078c7ff
Compare
24543c9
to
6a69071
Compare
b59c800
to
ca8856e
Compare
572e459
to
0104d82
Compare
e7f1781
to
1cb90ac
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.3.0
Minor Changes
2d9eb40
Thanks @juliusmarminge! - feat: forward request context toonUploadComplete
andonUploadError
Patch Changes
#1044
1afb1c9
Thanks @juliusmarminge! - refactor: simplify types for built file route#1043
d72a427
Thanks @juliusmarminge! - fix: support input transformers#1033
de98bab
Thanks @juliusmarminge! - fix: dynamically add either stylesheet or tailwind plugin based on whether `@nuxtjs/tailwindcss´ is installed#1013
7ae1ed9
Thanks @juliusmarminge! - chore: only slice file when necessary for resumabilityUpdated dependencies [
7ae1ed9
]:@uploadthing/expo@7.1.1
Patch Changes
#1044
1afb1c9
Thanks @juliusmarminge! - refactor: simplify types for built file routeUpdated dependencies [
1afb1c9
]:@uploadthing/mime-types@0.3.2
Patch Changes
7ae1ed9
Thanks @juliusmarminge! - fix: support legacy module resolutions to support Expo@uploadthing/nuxt@7.1.1
Patch Changes
#1044
1afb1c9
Thanks @juliusmarminge! - refactor: simplify types for built file route#1033
de98bab
Thanks @juliusmarminge! - fix: dynamically add either stylesheet or tailwind plugin based on whether `@nuxtjs/tailwindcss´ is installedUpdated dependencies [
1afb1c9
]:@uploadthing/react@7.1.1
Patch Changes
#1044
1afb1c9
Thanks @juliusmarminge! - refactor: simplify types for built file routeUpdated dependencies []:
@uploadthing/shared@7.1.1
Patch Changes
7ae1ed9
]:@uploadthing/solid@7.1.1
Patch Changes
#1044
1afb1c9
Thanks @juliusmarminge! - refactor: simplify types for built file routeUpdated dependencies []:
@uploadthing/svelte@7.1.1
Patch Changes
#1044
1afb1c9
Thanks @juliusmarminge! - refactor: simplify types for built file routeUpdated dependencies []:
@uploadthing/vue@7.1.1
Patch Changes
#1044
1afb1c9
Thanks @juliusmarminge! - refactor: simplify types for built file routeUpdated dependencies []: