Skip to content

chore(deps): bump @remix-run/server-runtime, @remix-run/express, @remix-run/node, @remix-run/react, @remix-run/serve and @remix-run/dev in /samples/pulumi-remix-postgres/remix - #570

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/samples/pulumi-remix-postgres/remix/multi-f5a96cb15e
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/samples/pulumi-remix-postgres/remix/multi-f5a96cb15e

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jan 8, 2026 •

Copy link
Copy Markdown
Contributor

Bumps @remix-run/server-runtime to 2.17.5 and updates ancestor dependencies @remix-run/server-runtime, @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/server-runtime from 2.2.0 to 2.17.5

Release notes

Sourced from @​remix-run/server-runtime'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

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​remix-run/server-runtime 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

Commits
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

Commits
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

Commits
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

Commits
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

Commits
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

Copy link
Copy Markdown
Contributor

@dependabot rebase

…ix-run/node, @remix-run/react, @remix-run/serve and @remix-run/dev

Bumps [@remix-run/server-runtime](https://github.com/remix-run/remix/tree/HEAD/packages/remix-server-runtime) to 2.17.5 and updates ancestor dependencies [@remix-run/server-runtime](https://github.com/remix-run/remix/tree/HEAD/packages/remix-server-runtime), [@remix-run/express](https://github.com/remix-run/remix/tree/HEAD/packages/remix-express), [@remix-run/node](https://github.com/remix-run/remix/tree/HEAD/packages/remix-node), [@remix-run/react](https://github.com/remix-run/remix/tree/HEAD/packages/remix-react), [@remix-run/serve](https://github.com/remix-run/remix/tree/HEAD/packages/remix-serve) and [@remix-run/dev](https://github.com/remix-run/remix/tree/HEAD/packages/remix-dev). These dependencies need to be updated together.


Updates `@remix-run/server-runtime` from 2.2.0 to 2.17.5
- [Release notes](https://github.com/remix-run/remix/releases)
- [Commits](https://github.com/remix-run/remix/commits/remix@2.17.5/packages/remix-server-runtime)

Updates `@remix-run/express` from 2.2.0 to 2.17.5
- [Release notes](https://github.com/remix-run/remix/releases)
- [Commits](https://github.com/remix-run/remix/commits/remix@2.17.5/packages/remix-express)

Updates `@remix-run/node` from 2.2.0 to 2.17.5
- [Release notes](https://github.com/remix-run/remix/releases)
- [Commits](https://github.com/remix-run/remix/commits/remix@2.17.5/packages/remix-node)

Updates `@remix-run/react` from 2.2.0 to 2.17.5
- [Release notes](https://github.com/remix-run/remix/releases)
- [Commits](https://github.com/remix-run/remix/commits/remix@2.17.5/packages/remix-react)

Updates `@remix-run/serve` from 2.2.0 to 2.17.5
- [Release notes](https://github.com/remix-run/remix/releases)
- [Commits](https://github.com/remix-run/remix/commits/remix@2.17.5/packages/remix-serve)

Updates `@remix-run/dev` from 2.2.0 to 2.17.5
- [Release notes](https://github.com/remix-run/remix/releases)
- [Commits](https://github.com/remix-run/remix/commits/remix@2.17.5/packages/remix-dev)

---
updated-dependencies:
- dependency-name: "@remix-run/dev"
  dependency-version: 2.17.3
  dependency-type: direct:development
- dependency-name: "@remix-run/express"
  dependency-version: 2.17.3
  dependency-type: direct:production
- dependency-name: "@remix-run/node"
  dependency-version: 2.17.3
  dependency-type: direct:production
- dependency-name: "@remix-run/react"
  dependency-version: 2.17.3
  dependency-type: direct:production
- dependency-name: "@remix-run/serve"
  dependency-version: 2.17.3
  dependency-type: direct:production
- dependency-name: "@remix-run/server-runtime"
  dependency-version: 2.17.3
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title Bump @remix-run/server-runtime, @remix-run/express, @remix-run/node, @remix-run/react, @remix-run/serve and @remix-run/dev in /samples/pulumi-remix-postgres/remix chore(deps): bump @remix-run/server-runtime, @remix-run/express, @remix-run/node, @remix-run/react, @remix-run/serve and @remix-run/dev in /samples/pulumi-remix-postgres/remix Oct 31, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/samples/pulumi-remix-postgres/remix/multi-f5a96cb15e branch from f5c31d2 to 75cfafd Compare October 31, 2026 01:21
@dependabot
dependabot Bot had a problem deploying to deploy-changed-samples October 31, 2026 01:21 Error
@coderabbitai

coderabbitai Bot commented Oct 31, 2026

Copy link
Copy Markdown

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: 37c7417e-4ee4-4361-bf86-0ccacc4fa047

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.

This branch was successfully deployed

No deployments
deploy-changed-samples — 75cfafd4 Deployed Oct 31, 2026 by dependabot[bot] via deploy_changed_samples #917
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant