Skip to content
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 #1152

Merged
merged 2 commits into from
Feb 17, 2025
Merged

Conversation

t3dotgg
Copy link
Member

@t3dotgg t3dotgg commented Feb 17, 2025

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/[email protected]

Minor Changes

  • #1151
    67c3b1c
    Thanks @juliusmarminge! - feat: add
    uploadProgressGranularity option to control how granular progress events are
    fired at

    You can now set uploadProgressGranularity to all, fine, or coarse to
    control how granular progress events are fired at.

    • all will forward every event from the XHR upload
    • fine will forward events for every 1% of progress
    • coarse (default) will forward events for every 10% of progress

Patch Changes

@uploadthing/[email protected]

Minor Changes

  • #1151
    67c3b1c
    Thanks @juliusmarminge! - feat: add
    uploadProgressGranularity option to control how granular progress events are
    fired at

    You can now set uploadProgressGranularity to all, fine, or coarse to
    control how granular progress events are fired at.

    • all will forward every event from the XHR upload
    • fine will forward events for every 1% of progress
    • coarse (default) will forward events for every 10% of progress

Patch Changes

@uploadthing/[email protected]

Minor Changes

  • #1151
    67c3b1c
    Thanks @juliusmarminge! - feat: add
    uploadProgressGranularity option to control how granular progress events are
    fired at

    You can now set uploadProgressGranularity to all, fine, or coarse to
    control how granular progress events are fired at.

    • all will forward every event from the XHR upload
    • fine will forward events for every 1% of progress
    • coarse (default) will forward events for every 10% of progress

Patch Changes

@uploadthing/[email protected]

Minor Changes

  • #1151
    67c3b1c
    Thanks @juliusmarminge! - feat: add
    uploadProgressGranularity option to control how granular progress events are
    fired at

    You can now set uploadProgressGranularity to all, fine, or coarse to
    control how granular progress events are fired at.

    • all will forward every event from the XHR upload
    • fine will forward events for every 1% of progress
    • coarse (default) will forward events for every 10% of progress

Patch Changes

@uploadthing/[email protected]

Patch Changes

@uploadthing/[email protected]

Patch Changes

@uploadthing/[email protected]

Patch Changes

  • a1e13b5
    Thanks @juliusmarminge! - This release
    just contains helper exports for the new uploadProgressGranularity feature
    in the frontend library adapters

[email protected]

Patch Changes

Summary by CodeRabbit

  • New Features

    • Introduced an upload progress control option that lets users choose between detailed, moderate, or coarse progress updates during file uploads.
  • Chores

    • Updated dependency and package versions across various projects and examples to ensure improved consistency and performance.

@github-actions github-actions bot force-pushed the changeset-release/main branch from c53c7dd to 9108369 Compare February 17, 2025 20:25
Copy link

vercel bot commented Feb 17, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs-uploadthing ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 17, 2025 8:36pm
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
legacy-docs-uploadthing ⬜️ Ignored (Inspect) Visit Preview Feb 17, 2025 8:36pm

Copy link
Contributor

coderabbitai bot commented Feb 17, 2025

Walkthrough

This pull request introduces an uploadProgressGranularity option that allows users to control the frequency of progress events during file uploads, with settings for all, fine, or coarse. Additionally, multiple dependency version updates have been applied across example projects and packages, ensuring consistency and incorporating minor version changes. Changelog files have also been revised to reflect these updates.

Changes

File Change Summary
.changeset/...-jog.md Deleted file that documented the new uploadProgressGranularity feature and its settings.
examples/.../package.json Updated dependency versions across various example projects. In most cases, @uploadthing/react was upgraded from 7.2.1 to 7.3.0, and uploadthing from 7.5.1 to 7.5.2, along with similar updates for client-vanilla, client-vue, expo, nuxt, and others.
packages/... Revised changelogs and package.json files for packages (expo, nuxt, react, shared, solid, svelte, uploadthing, vue) to document version bumps and the addition of the uploadProgressGranularity option.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant C as Upload Component
    participant O as Option Handler
    participant X as XHR Upload Process

    U->>C: Initiate file upload
    C->>O: Retrieve uploadProgressGranularity setting (all/fine/coarse)
    O-->>C: Return granularity value
    C->>X: Begin file upload with specified granularity
    X->>C: Emit progress events at chosen frequency
    C->>U: Display upload progress
Loading

Possibly related PRs

  • chore(release): 📦 version packages #1149: The changes in the main PR, which introduce the uploadProgressGranularity option for file uploads, are related to the retrieved PR that updates the uploadthing package, as both involve modifications to the upload functionality within the same package.
  • chore: sync key usage on upload #998: The changes in the main PR, which introduce the uploadProgressGranularity option for controlling upload progress events, are related to the retrieved PR that enhances the upload process by adding a version header to upload requests, as both pertain to improving the upload functionality within the same context.
  • feat: add ProgressGranularity #1151: The changes in the main PR regarding the uploadProgressGranularity option are directly related to the modifications in the retrieved PR, which also introduces the uploadProgressGranularity property across various components, enhancing upload progress control.

Suggested labels

examples, 📚 documentation

Suggested reviewers

  • markflorkowski

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot force-pushed the changeset-release/main branch from 4f34173 to 008e953 Compare February 17, 2025 20:29
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (5)
packages/svelte/CHANGELOG.md (1)

5-19: New Feature Addition: uploadProgressGranularity Option

The changelog entry clearly describes the addition of the uploadProgressGranularity option, including its allowed values and behavior:

  • all – forwards every event from the XHR upload.
  • fine – forwards events for every 1% progress.
  • coarse (default) – forwards events for every 10% progress.

A minor suggestion: consider using “triggered” instead of “fired at” to improve clarity.

packages/shared/CHANGELOG.md (1)

3-19: New Version Entry for 7.1.7 with uploadProgressGranularity

This changelog entry clearly documents the new feature by listing the available options (all, fine, and coarse) and explaining what each does. Consider rephrasing the repeated phrase “fired at” (for example, “triggered” or “emitted”) to improve clarity.

packages/solid/CHANGELOG.md (2)

5-12: Minor Changes Section – New Option Documentation

The new minor changes block properly documents the addition of the uploadProgressGranularity option (introduced via #1151). The inclusion of the commit link and thanks to the contributor add transparency. One minor suggestion is to consider rephrasing “fired at” (line 11) for improved clarity (e.g. “triggered” or “emitted”).


13-14: Clarification on Option Usage

The description explaining that uploadProgressGranularity accepts values all, fine, or coarse is concise. For increased grammatical clarity, consider rewording the sentence. For example, “You can now set uploadProgressGranularity to all, fine, or coarse to determine the frequency at which progress events are emitted.”

packages/vue/CHANGELOG.md (1)

7-19: Detailing the New Feature
This block provides details on the newly added uploadProgressGranularity option, explaining that users can set it to all, fine, or coarse. The explanation and bullet-point list are clear and succinct. A minor suggestion: consider rephrasing “fired at” (e.g., “triggered” or “emitted”) to improve clarity.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 67c3b1c and 4f34173.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (41)
  • .changeset/fair-tomatoes-jog.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/profile-picture/package.json (2 hunks)
  • examples/with-clerk-appdir/package.json (1 hunks)
  • examples/with-clerk-pagesdir/package.json (1 hunks)
  • examples/with-clerk-react-router/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 (1)
  • .changeset/fair-tomatoes-jog.md
✅ Files skipped from review due to trivial changes (29)
  • packages/nuxt/package.json
  • packages/shared/package.json
  • packages/svelte/package.json
  • packages/vue/package.json
  • packages/react/package.json
  • examples/backend-adapters/client-vanilla/package.json
  • packages/solid/package.json
  • examples/backend-adapters/client-vue/package.json
  • examples/backend-adapters/client-react/package.json
  • examples/minimal-pagedir/package.json
  • examples/minimal-nuxt/package.json
  • examples/minimal-solidstart/package.json
  • examples/profile-picture/package.json
  • examples/with-drizzle-appdir/package.json
  • examples/with-novel/package.json
  • packages/expo/CHANGELOG.md
  • examples/backend-adapters/server/package.json
  • examples/minimal-astro-react/package.json
  • examples/with-drizzle-pagesdir/package.json
  • examples/minimal-expo/package.json
  • packages/nuxt/CHANGELOG.md
  • examples/with-clerk-remix/package.json
  • examples/minimal-tanstack-start/package.json
  • examples/with-clerk-pagesdir/package.json
  • packages/uploadthing/package.json
  • examples/with-clerk-appdir/package.json
  • examples/with-serveractions/package.json
  • packages/expo/package.json
  • examples/backend-adapters/package.json
🔇 Additional comments (25)
packages/svelte/CHANGELOG.md (2)

3-4: Version Bump Header for 7.3.0

The new version header "## 7.3.0" is clear and effectively highlights the latest release.


20-25: Dependency Update: @uploadthing/shared Version Bump

The patch changes section accurately documents the dependency update to @uploadthing/[email protected] with an appropriate commit reference. This ensures consistency across the packages.

examples/with-react-image-crop/package.json (2)

12-13: Approved: Dependency Version Update for @uploadthing/react
The version change to "7.3.0" reflects the release that introduces the new uploadProgressGranularity option. This update is consistent with the overall package upgrade.


17-17: Approved: Dependency Version Update for uploadthing
The version has been correctly updated to "7.5.2", ensuring consistency with the minor version bump across the ecosystem.

examples/minimal-appdir/package.json (2)

12-13: Approved: Dependency Version Update for @uploadthing/react
The dependency update to "7.3.0" is in line with the release changes and brings in the new progress granularity feature.


16-16: Approved: Dependency Version Update for uploadthing
Updating to "7.5.2" maintains consistency with the overall upgrade strategy across all examples.

examples/with-tailwindcss/package.json (2)

12-13: Approved: Dependency Version Update for @uploadthing/react
The version has been correctly bumped to "7.3.0", reflecting the introduction of the new upload progress option.


16-16: Approved: Dependency Version Update for uploadthing
The updated version "7.5.2" is consistent with other package updates in this PR.

examples/minimal-sveltekit/package.json (2)

17-17: Approved: Dependency Version Update for @uploadthing/svelte
Changing to "7.3.0" correctly aligns with the new feature rollout and ensures compatibility with the updated ecosystem.


18-18: Approved: Dependency Version Update for uploadthing
The "7.5.2" version update here is in line with changes across other examples, ensuring consistency.

examples/with-clerk-react-router/package.json (2)

16-16: Approved: Dependency Version Update for @uploadthing/react
The upgrade to "7.3.0" reflects the necessary update for utilizing the new uploadProgressGranularity option.


22-22: Approved: Dependency Version Update for uploadthing
The bump to "7.5.2" is applied uniformly and aligns well with the overall dependency update strategy.

packages/react/CHANGELOG.md (2)

3-19: New Version 7.3.0 Release Entry for @uploadthing/react

The entry effectively introduces the new uploadProgressGranularity option. It clearly explains the available settings and provides practical guidance for users.


20-25: Dependency Update to @uploadthing/[email protected]

The dependency bump is correctly applied and aligns with the new shared functionality. This update ensures consistency across packages.

packages/uploadthing/CHANGELOG.md (5)

3-4: Version Bump Verification:
The release note header for version 7.5.2 is clearly marked and follows the expected changelog format. This helps users immediately identify the new release.


5-6: Section Heading – Patch Changes:
The heading "### Patch Changes" is appropriately used here and sets up the context for the updates that follow.


7-12: New Feature Entry for uploadProgressGranularity:
The changelog entry documents the addition of the uploadProgressGranularity option along with the commit reference and acknowledgment. It concisely describes the feature addition. One minor suggestion is to verify that the default behavior (later described as coarse) is highlighted so users have immediate clarity if they do not specify a value.


13-19: Detailed Explanation of Granularity Options:
The breakdown of the available options—all, fine, and coarse—is both clear and informative. This explanation provides a solid guide on how progress events will be fired based on the chosen granularity.


20-23: Dependency Update Details:
The dependency update block clearly indicates that @uploadthing/shared has been updated to version 7.1.7 with its corresponding commit reference. It would be good to double-check that this dependency update is in sync across all related packages if applicable.

packages/solid/CHANGELOG.md (3)

3-4: Clear Version Header

The header ## 7.3.0 clearly indicates the new release version and follows the changelog’s existing style. This helps users quickly locate the most recent changes.


16-18: Bullet Points for Progress Events

The bullet points effectively differentiate the behaviors of the three settings:

  • all – forwards every event from the XHR upload,
  • fine – forwards events for every 1% of progress, and
  • coarse – (default) forwards events for every 10% of progress.

This clear distinction minimizes confusion about the feature’s functionality.


20-24: Patch Changes – Dependency Update

The patch changes section documents the update to the @uploadthing/shared dependency (upgraded to version 7.1.7) with a commit reference. The dependency update is clearly noted, ensuring consistency with similar changes in other packages.

packages/vue/CHANGELOG.md (3)

3-4: New Release Header Added
The section header for version 7.3.0 is clearly introduced. This correctly marks the new release entry for the @uploadthing/vue package.


20-25: Dependency Update Documentation
The Patch Changes section clearly documents the dependency update for @uploadthing/shared to version 7.1.7 with the associated commit reference. This is consistent with the changelog style of previous versions.


26-312: Historical Release Notes Consistency
The remainder of the file contains historical records for earlier releases (versions 7.2.0 down to 6.5.0). These entries are well maintained and consistent with established formatting. No issues noted in these sections.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
packages/svelte/CHANGELOG.md (1)

7-19: Documentation of New uploadProgressGranularity Feature

This section effectively explains the new uploadProgressGranularity option, including its available settings (all, fine, and coarse). The commit reference, acknowledgment, and detailed description ensure transparency about the change.

Suggestion: Consider rephrasing "fired at" to "emitted" to improve clarity. For example, update:

- feat: add `uploadProgressGranularity` option to control how granular progress events are fired at
+ feat: add `uploadProgressGranularity` option to control the granularity of emitted progress events

This minor wording tweak can enhance readability and consistency with industry terminology.

packages/vue/CHANGELOG.md (1)

5-19: Clarify the uploadProgressGranularity Option Description
The changelog clearly documents the addition of the uploadProgressGranularity option and its available settings (all, fine, and coarse). However, the phrasing at lines 10–11 (“...fired at”) can be a bit ambiguous. Consider rephrasing it to something like “...emitted during the upload process” or “...triggered at the specified intervals” for improved clarity.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4f34173 and 92b2ac8.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (41)
  • .changeset/fair-tomatoes-jog.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/profile-picture/package.json (2 hunks)
  • examples/with-clerk-appdir/package.json (1 hunks)
  • examples/with-clerk-pagesdir/package.json (1 hunks)
  • examples/with-clerk-react-router/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 (1)
  • .changeset/fair-tomatoes-jog.md
🚧 Files skipped from review as they are similar to previous changes (38)
  • packages/shared/package.json
  • packages/vue/package.json
  • packages/expo/package.json
  • packages/solid/package.json
  • packages/uploadthing/package.json
  • packages/svelte/package.json
  • packages/react/package.json
  • examples/with-serveractions/package.json
  • examples/with-drizzle-pagesdir/package.json
  • examples/backend-adapters/client-vanilla/package.json
  • examples/with-clerk-pagesdir/package.json
  • examples/profile-picture/package.json
  • examples/backend-adapters/client-vue/package.json
  • examples/with-clerk-appdir/package.json
  • packages/nuxt/package.json
  • examples/minimal-expo/package.json
  • examples/with-clerk-react-router/package.json
  • examples/with-react-image-crop/package.json
  • examples/minimal-astro-react/package.json
  • examples/backend-adapters/package.json
  • examples/minimal-nuxt/package.json
  • examples/minimal-pagedir/package.json
  • packages/expo/CHANGELOG.md
  • examples/with-tailwindcss/package.json
  • examples/with-clerk-remix/package.json
  • examples/with-novel/package.json
  • examples/minimal-appdir/package.json
  • examples/minimal-tanstack-start/package.json
  • examples/minimal-sveltekit/package.json
  • packages/nuxt/CHANGELOG.md
  • examples/backend-adapters/client-react/package.json
  • packages/uploadthing/CHANGELOG.md
  • examples/minimal-solidstart/package.json
  • packages/shared/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • examples/with-drizzle-appdir/package.json
  • packages/solid/CHANGELOG.md
  • examples/backend-adapters/server/package.json
🔇 Additional comments (4)
packages/svelte/CHANGELOG.md (2)

3-4: Version Header for 7.3.0 is Clear

The new "## 7.3.0" header is clearly delineated, indicating a major milestone for the package release.


22-24: Dependency Update Noted Successfully

The changelog correctly documents the update of @uploadthing/shared to version 7.1.7 under the patch changes. This explicit tracking of dependency versions is important for maintainability and compatibility.

packages/vue/CHANGELOG.md (2)

3-4: New Version Header is Correctly Formatted
The new version header "## 7.3.0" is clear and follows the established markdown convention. This correctly signals the introduction of the new release.


22-25: Dependency Update Section Verified
The patch changes section properly lists the dependency update to @uploadthing/[email protected]. This aligns with the PR objectives and ensures consistency across related packages.

@juliusmarminge juliusmarminge merged commit b2f3f87 into main Feb 17, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants