[dependabot]

Bumps @remix-run/router to 1.23.3 and updates ancestor dependencies @remix-run/router, @remix-run/express, @remix-run/node, @remix-run/react, @remix-run/serve and @remix-run/dev. These dependencies need to be updated together.

Updates @remix-run/router from 1.11.0 to 1.23.3

Changelog

Sourced from @​remix-run/router's changelog.

v1.23.3

Patch Changes

• Lift decodePath call out of hot path during route matching (#15119)
• Normalize double slashes in redirect paths (#15118)

1.23.2

Patch Changes

• Validate redirect locations (#14707)

1.23.1

Patch Changes

• Normalize double-slashes in resolvePath (#14537)

1.23.0

Minor Changes

• Add fetcherKey as a parameter to patchRoutesOnNavigation (#13109)

Patch Changes

• Fix regression introduced in 6.29.0 via #12169 that caused issues navigating to hash routes inside splat routes for applications using Lazy Route Discovery (patchRoutesOnNavigation) (#13108)

1.22.0

Minor Changes

• Provide the request signal as a parameter to patchRoutesOnNavigation (#12900)

  • This can be used to abort any manifest fetches if the in-flight navigation/fetcher is aborted

Patch Changes

• Do not log v7 deprecation warnings in production builds (#12794)
• Strip search parameters from patchRoutesOnNavigation path param for fetcher calls (#12899)
• Properly bubble headers when throwing a data() result (#12845)
• Optimize route matching by skipping redundant matchRoutes calls when possible (#12169)

1.21.1

Patch Changes

• • Fix issue with fetcher data cleanup in the data layer on fetcher unmount (#12674)
  • Fix behavior of manual fetcher keys when not opted into future.v7_fetcherPersist

... (truncated)

Commits

• 651211c Release v6.30.4 (#15120)
• 4deb9c5 Lift decodePath call (#15119)
• d77f6b1 Normalize double slashes in redirect paths (#15118)
• f82a6f9 Bring new release process into v6 branch (#15115)
• c662ca3 chore: Update version for release (#14713)
• 98ad691 chore: Update version for release (pre-v6) (#14710)
• 2fbb84c Validate redirect locations (v6) (#14707)
• 26b5d45 chore: Update version for release (#14541)
• 919f8a8 chore: Update version for release (pre-v6) (#14540)
• 69bf705 Normalize double slashes in resolvePath (#14537)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​remix-run/router since your current version.

Updates @remix-run/express from 2.2.0 to 2.17.5

Release notes

Sourced from @​remix-run/express's releases.

file-storage-s3 v1.1.0

Minor Changes

• storage.set() now streams files to S3 instead of reading the whole file into memory first. Files larger than one part are sent with an S3 multipart upload, so memory use stays at about two parts per upload no matter how large the file is. Smaller files are still sent with a single PUT. Any File-shaped object works, including streaming sources that can only be read with stream() and don't know their size up front, which are sent to S3 as they're read. (#12070)

  Use the new partSize option to set the part size, which defaults to 8 MiB and must be at least 5 MiB, the S3 minimum. If a multipart upload fails, it is aborted so S3 does not keep the uploaded parts. Consider also adding a bucket lifecycle rule that removes incomplete multipart uploads, in case a process exits before it can abort one.

  let storage = createS3FileStorage({
    accessKeyId: process.env.AWS_ACCESS_KEY_ID!,
    secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY!,
    bucket: 'my-app-uploads',
    region: 'us-east-1',
    partSize: 16 * 1024 * 1024,
  })

  storage.put() uses the same upload path, but it still holds the whole file in memory because it returns a File with the stored contents. Use set() for large files.

file-storage-s3 v1.0.0

Major Changes

• First stable release.

Patch Changes

• Bumped @remix-run/* dependencies:
  • file-storage@1.0.0

Commits

• 8307662 Version 2.17.5
• ab977d9 Version 2.17.4
• b1d29d9 Version 2.17.3
• 4a5ffd1 Revert "Version 2.17.3"
• 98c89fa Version 2.17.3
• 3920349 Version 2.17.2
• 91ef6fe Version 2.17.1
• 3000859 chore: Update version for release (#10698)
• 3004a98 chore: Update version for release (pre) (#10692)
• fc5cb1f chore: Update version for release (pre) (#10691)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​remix-run/express since your current version.

Updates @remix-run/node from 2.2.0 to 2.17.5

Release notes

Sourced from @​remix-run/node's releases.

file-storage-s3 v1.1.0

Minor Changes

• storage.set() now streams files to S3 instead of reading the whole file into memory first. Files larger than one part are sent with an S3 multipart upload, so memory use stays at about two parts per upload no matter how large the file is. Smaller files are still sent with a single PUT. Any File-shaped object works, including streaming sources that can only be read with stream() and don't know their size up front, which are sent to S3 as they're read. (#12070)

  Use the new partSize option to set the part size, which defaults to 8 MiB and must be at least 5 MiB, the S3 minimum. If a multipart upload fails, it is aborted so S3 does not keep the uploaded parts. Consider also adding a bucket lifecycle rule that removes incomplete multipart uploads, in case a process exits before it can abort one.

  let storage = createS3FileStorage({
    accessKeyId: process.env.AWS_ACCESS_KEY_ID!,
    secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY!,
    bucket: 'my-app-uploads',
    region: 'us-east-1',
    partSize: 16 * 1024 * 1024,
  })

  storage.put() uses the same upload path, but it still holds the whole file in memory because it returns a File with the stored contents. Use set() for large files.

file-storage-s3 v1.0.0

Major Changes

• First stable release.

Patch Changes

• Bumped @remix-run/* dependencies:
  • file-storage@1.0.0

Commits

• 8307662 Version 2.17.5
• ab977d9 Version 2.17.4
• b1d29d9 Version 2.17.3
• 4a5ffd1 Revert "Version 2.17.3"
• 98c89fa Version 2.17.3
• 3920349 Version 2.17.2
• 64d88de Validate session id in file session storage (#10806)
• 91ef6fe Version 2.17.1
• 3000859 chore: Update version for release (#10698)
• 3004a98 chore: Update version for release (pre) (#10692)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​remix-run/node since your current version.

Updates @remix-run/react from 2.2.0 to 2.17.5

Release notes

Sourced from @​remix-run/react's releases.

file-storage-s3 v1.1.0

Minor Changes

• storage.set() now streams files to S3 instead of reading the whole file into memory first. Files larger than one part are sent with an S3 multipart upload, so memory use stays at about two parts per upload no matter how large the file is. Smaller files are still sent with a single PUT. Any File-shaped object works, including streaming sources that can only be read with stream() and don't know their size up front, which are sent to S3 as they're read. (#12070)

  Use the new partSize option to set the part size, which defaults to 8 MiB and must be at least 5 MiB, the S3 minimum. If a multipart upload fails, it is aborted so S3 does not keep the uploaded parts. Consider also adding a bucket lifecycle rule that removes incomplete multipart uploads, in case a process exits before it can abort one.

  let storage = createS3FileStorage({
    accessKeyId: process.env.AWS_ACCESS_KEY_ID!,
    secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY!,
    bucket: 'my-app-uploads',
    region: 'us-east-1',
    partSize: 16 * 1024 * 1024,
  })

  storage.put() uses the same upload path, but it still holds the whole file in memory because it returns a File with the stored contents. Use set() for large files.

file-storage-s3 v1.0.0

Major Changes

• First stable release.

Patch Changes

• Bumped @remix-run/* dependencies:
  • file-storage@1.0.0

Commits

• 8307662 Version 2.17.5
• efdd2c4 v2 updates (#11487)
• ab977d9 Version 2.17.4
• 010b356 Bump router versions (#10938)
• b1d29d9 Version 2.17.3
• 5c87c08 Escape HTML in scroll restoration keys (#10925)
• 4a5ffd1 Revert "Version 2.17.3"
• 98c89fa Version 2.17.3
• 3920349 Version 2.17.2
• 91ef6fe Version 2.17.1
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​remix-run/react since your current version.

Updates @remix-run/serve from 2.2.0 to 2.17.5

Release notes

Sourced from @​remix-run/serve's releases.

file-storage-s3 v1.1.0

Minor Changes

• storage.set() now streams files to S3 instead of reading the whole file into memory first. Files larger than one part are sent with an S3 multipart upload, so memory use stays at about two parts per upload no matter how large the file is. Smaller files are still sent with a single PUT. Any File-shaped object works, including streaming sources that can only be read with stream() and don't know their size up front, which are sent to S3 as they're read. (#12070)

  Use the new partSize option to set the part size, which defaults to 8 MiB and must be at least 5 MiB, the S3 minimum. If a multipart upload fails, it is aborted so S3 does not keep the uploaded parts. Consider also adding a bucket lifecycle rule that removes incomplete multipart uploads, in case a process exits before it can abort one.

  let storage = createS3FileStorage({
    accessKeyId: process.env.AWS_ACCESS_KEY_ID!,
    secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY!,
    bucket: 'my-app-uploads',
    region: 'us-east-1',
    partSize: 16 * 1024 * 1024,
  })

  storage.put() uses the same upload path, but it still holds the whole file in memory because it returns a File with the stored contents. Use set() for large files.

file-storage-s3 v1.0.0

Major Changes

• First stable release.

Patch Changes

• Bumped @remix-run/* dependencies:
  • file-storage@1.0.0

Commits

• 8307662 Version 2.17.5
• ab977d9 Version 2.17.4
• b1d29d9 Version 2.17.3
• 4a5ffd1 Revert "Version 2.17.3"
• 98c89fa Version 2.17.3
• 3920349 Version 2.17.2
• 91ef6fe Version 2.17.1
• c5298ea Update compression and morgan packages (#10740)
• 3000859 chore: Update version for release (#10698)
• 3004a98 chore: Update version for release (pre) (#10692)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​remix-run/serve since your current version.

Updates @remix-run/dev from 2.2.0 to 2.17.5

Release notes

Sourced from @​remix-run/dev's releases.

file-storage-s3 v1.1.0

Minor Changes

• storage.set() now streams files to S3 instead of reading the whole file into memory first. Files larger than one part are sent with an S3 multipart upload, so memory use stays at about two parts per upload no matter how large the file is. Smaller files are still sent with a single PUT. Any File-shaped object works, including streaming sources that can only be read with stream() and don't know their size up front, which are sent to S3 as they're read. (#12070)

  Use the new partSize option to set the part size, which defaults to 8 MiB and must be at least 5 MiB, the S3 minimum. If a multipart upload fails, it is aborted so S3 does not keep the uploaded parts. Consider also adding a bucket lifecycle rule that removes incomplete multipart uploads, in case a process exits before it can abort one.

  let storage = createS3FileStorage({
    accessKeyId: process.env.AWS_ACCESS_KEY_ID!,
    secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY!,
    bucket: 'my-app-uploads',
    region: 'us-east-1',
    partSize: 16 * 1024 * 1024,
  })

  storage.put() uses the same upload path, but it still holds the whole file in memory because it returns a File with the stored contents. Use set() for large files.

file-storage-s3 v1.0.0

Major Changes

• First stable release.

Patch Changes

• Bumped @remix-run/* dependencies:
  • file-storage@1.0.0

Commits

• 8307662 Version 2.17.5
• efdd2c4 v2 updates (#11487)
• ab977d9 Version 2.17.4
• 010b356 Bump router versions (#10938)
• b1d29d9 Version 2.17.3
• 4a5ffd1 Revert "Version 2.17.3"
• 98c89fa Version 2.17.3
• b6aec07 deps(dev): update valibot (#10901)
• 3920349 Version 2.17.2
• 91ef6fe Version 2.17.1
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​remix-run/dev since your current version.

Samples Checklist

✅ All good!

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[defangdevs]

@dependabot rebase

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI; Enforced overrides: Organization
• Review profile: CHILL
• Plan: Advanced
• Run ID: b073d3db-cbf0-4416-8093-8bb77577cb4c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}