v6.6.3

Patch Release

• feat(crwa): Always install using yarn v4 #9861 by @Tobbe

  This only affects yarn create redwood-app. This PR fixes errors in the installation process by changing directories into the new redwood app before running yarn install so that the subprocess uses the correct version of yarn.

v6.6.2

Patch Release

• fix(dbAuth): Correct hardcoded DB column #9788 by @Josh-Walker-GM

  Logging in with webauthn enabled was broken when you had customised your schema to use different column names than the default. See #8743 for details.

• fix(fastify): Prevent duplicate @fastify/url-data registration #9794

  A recent change in #9714 introduced a small issue where the @fastify/url-data plugin would register twice and on the second registration would throw an uncaught error. This would cause failures when attempting to launch the server from some entrypoints. See: #9789 for more information.

v6.6.1

Patch Release

Note

If you're using the experimental OpenTelemetry support, and have your config file in a non-standard location this release is breaking.
See further down for more info
TL;DR: Please move the config file to api/src/opentelemetry.ts

• fix: Support Custom Id Field Names when generating Cells #9778 by @dthyresson

  With this fix in place it's now possible to use yarn rw g cell ModelName for models that use a custom id field name, like uuid or email.

• fix(baremetal) sshExec() errors not displaying #9743 by @Mirai-Miki

  Running yarn rw deploy baremetal production could sometimes exit without displaying an error. With this fix a nicely formated error is now displayed

• fix(studio): Fix windows path issues #9752 by @Josh-Walker-GM

  Removes some assumptions of / as the path separator.

• fix(path-alias): Fix aliasing of paths using ts/jsconfig #9574 by @dac09

• Fix supertokens docs & integration issues #9757 by @suzdalnitski

  Adds more details to the Supertokens docs. Especially around environment variables.

  Also updates the api/lib/supertokens.ts template to include apiKey: process.env.SUPERTOKENS_API_KEY.

• Fixes the way OpenTelemetry setup template uses project-config for port setting #9775 by @dthyresson

  The syntax in the opentelemetry.ts template was wrong. It was using a mix of import and require on the same line. This PR fixes this, so the file can be executed properly

• fix(otel): Fix OTel sdk loading #9777 by @Josh-Walker-GM

  Problem
  The toml config value that was supported for the experimental OpenTelemetry support points to the source file. It was however being used as if it were pointing to the transpiled version of the file.

  Changes

  1. Switches the opentelemetry.ts file to use import over require syntax.
  2. Removes the apiSdk toml option and now assumes the file exists at api/src/opentelemetry.ts such that it then also exists at api/dist/opentelemetry.js.
  3. Adds a large concurrencyLimit option to the OTel trace exporter. This fixes a limitation of the current redwood studio. This config will be removed in an upcoming change to the redwood studio which will better support the BatchSpanProcessor instead.

  Warning
  If you're using the experimental OpenTelemetry support, and have your config file in a non-standard location this change is breaking.
  Please move the config file to api/src/opentelemetry.ts

• fix(crwa): use fs.renameSync instead of fs.rename #9787 by @jtoar

• Adds a note about the two commands you will use with your schema to the top of the schema file #8589 by @orta

  The following comment is now part of the schema.prisma template

   // Don't forget to tell Prisma about your edits to this file using
   // `yarn rw prisma migrate dev` or `yarn rw prisma db push`.
   // `migrate` is like committing while `push` is for prototyping.
   // Read more about both here:
   // https://www.prisma.io/docs/orm/prisma-migrate
  

• Docker: Update to work with corepack and yarn v4 #9764

  Update our experimental Dockerfile support to work with corepack and yarn v4. If you're using this experimental feature you probably want to run yarn rw exp setup-docker -f to generate a new Dockerfile and compare the changes to your own Dockerfile to see what you might want to incorporate.

• docs: Update Metadata docs #9744 by @Tobbe

• docs: added some clarification on serverless functions getting executed in a non-serverless environment #9742 by @suzdalnitski

• docs: Replaced deprecated <Set private> with PrivateSet within router.md #9749 by @suzdalnitski

• docs: Make it easier to find useMatch docs #9756 by @Tobbe

• docs: Supertokens.md: Fix typo #9765 by @Tobbe

• docs: docker.md: Fix web path #9768 by @Tobbe

v6.6.0

Changelog

Important

While this release includes preliminary support for Yarn v4, upgrading to it is completely optional. If anything doesn't work, you can always downgrade back to Yarn v3. We expect most rough edges to be with deploy providers. If you run into anything, please open an issue!

Features

• chore(deps): update yarn to v4 #9343

  New Redwood projects will use Yarn v4 out of the box. Yarn v4 includes many new features and fixes like an improved UI, the ability to write constraints in JS instead of Prolog, and a simpler way to get set up all together.

  For existing projects, upgrading to Yarn v4 is fairly simple, but may require changes based on your deploy provider. Here are the steps locally:

  • Enable corepack

    corepack enable
    

    Corepack is a manager for package managers if you will. It's a tool shipped with Node.js 16+ that automatically selects the right package manager and version to run depending on the project you're working on.

  • Update the packageManager field in your project's root package.json to yarn@4.0.2

    -  "packageManager": "yarn@3.7.0" // Or whatever version it happened to be at
    +  "packageManager": "yarn@4.0.2"

    Corepack uses the packageManager field in your root package json to select the package manager and version.

  • Remove yarnPath in .yarnrc.yml and remove .yarn/releases

    Now that you're using Corepack, you don't need yarnPath or the binary in .yarn/releases anymore. You can still use them if you prefer this workflow, but they're not necessary and will take precedence over packageManager.

  • If you previously installed yarn via hombrew or NPM we recommend removing that installation since it can conflict with corepack in some cases:

    brew uninstall yarn
    

    See Yarn's announcement post for more details: https://yarnpkg.com/blog/release/4.0.

• Support custom @id column name in scaffold #8264 by @samthuang

  An improvement to the scaffold generator now allows columns with custom names to serve as the @id field in the Prisma datamodel. Previously the scaffold generator assumed that the @id field was named "id". This change provides flexibility to specify any name for the @id column if it's marked with the @id attribute in the Prisma datamodel.

• Adds new <Metadata> component for proper <meta> tag generation #9315 by @cannikin

  The new <Metadata> component allows for a more natural and powerful way to set <head> tags, like <meta ... />. See the new docs at https://redwoodjs.com/docs/seo-head#setting-meta-tags-and-opengraph-directives-with-metadata.

• Add vscode web debugger and compound #9567 by @xmaxcooking

  Adds two debug configurations to .vscode/launch.json:

  • Web Debugger (launches the built-in chrome web debugger)
  • Compound of Dev + Api + Web (launches a fully-debuggable redwood with a single configuration)

• Studio: Make port configurable #9709 by @Tobbe

  Makes it possible to configure the base port Redwood Studio uses. The default is 4318. Mailer will use basePort + 1.

• Preserve trailing whitespace for Markdown, HTML & MJML (RedwoodJS project + create-redwood-app template) #5869 by @Philzen

  While trailing whitespace is just noise in code (well, 99 % of the time...), for markdown it has actual significance. This changes the VS Code configuration to respect it in markdown files.

• ✨ Added autodocs to component Storybook Stories #9547 by @ahaywood

  For the Storybook component template, tags: ['autodocs'] is added to the meta block:

   const meta: Meta<typeof ${pascalName}> = {
     component: ${pascalName},
  +  tags: ['autodocs']
   }

• Export SignupHandlerOptions interface and update its userAttributes type #9049 by @c-ciobanu

  You can now use TypeScript generics to get correct typings for userAttributes. For more context, see https://community.redwoodjs.com/t/signuphandleroptions-userattributes-type/5231.

Fixes

• fix: sentry no longer supports tracing as a seperate package #9542 by @ageddesi

• fix: Safeguard for Sentry default templates + nitpick #9012 by @HazAT

  This, and the fix above both make sure our Sentry setup script follows the latest best practices and also enables the HTTP Tracing integration for the frontend.

• Update .vscode/settings.json files for ESLint setting #9723 by @morganmspencer

• Fix Studio paths #9729 by @Tobbe

• fix(gitpod): enable corepack to get proper node version #9732 by @colbywhite

• fix(CLI): fix getDevNodeOptions #9735 by @jtoar

  NODE_OPTIONS="..." yarn rw dev now works as expected.

• fix(fastify): Server not handling periods in query params #9714

Docs

• Proofreading fixes for realtime docs #9657 by @Tobbe
• docs: auth - Clerk - Corrects Home Page generation instructions #9662 by @dthyresson
• Update Toast Notifications Docs with Example of Async Toast using toast.promise #9710 by @xmaxcooking
• docs(#9006) - Update redwoodjs cli to include correct forum url #9721 by @ageddesi
• 💬 Fixed formatting within the docs #9587 by @ahaywood
• fix "Core Team" link #9621 by @sqs
• Fix grammar #9720 by @wingedotter5
• Fixed closing tag used as opening tag in several places #9724 by @joshdotjs
• Fix typo #9725 by @joshdotjs
• Add a note about build and runtime environments #9726 by @Tobbe
• fix(docs): update webAuthn import in dbauth doc #9170 #9178 by @jlthompso

Core Dependencies

• fix(deps): update storybook monorepo to v7.6.4 #9647
• chore(deps): update yarn to v4 #9343
• chore(deps): update babel monorepo #9718
• chore(deps): update dependency typescript to v5.3.3 #9645

Dependencies

Click to see all upgraded dependencies

• chore(deps): update dependency @clerk/clerk-react to v4.28.3 #9643
• fix(deps): update dependency @clerk/clerk-sdk-node to v4.13.1 #9648
• fix(deps): update dependency clsx to v2 #9681
• chore(deps): update postgres docker tag to v16 #9679
• fix(deps): update dependency ci-info to v4 #9680
• fix(deps): update dependency core-js to v3.34.0 #9649
• chore(deps): update dependency @clerk/types to v3.60.0 #9644
• chore(deps): update dependency typescript to v5.3.3 #9645

v6.5.1

Patch Release

• fix(deps): update prisma monorepo to v5.7.0 #9642

  Users were facing issues deploying to Netlify on Node.js 20. Prisma would fail during runtime saying it couldn't locate the engine binary. This Prisma minor includes the fix; read more in the Prisma release notes.

  (Note that Redwood doesn't officially support Node.js 20 yet, but their deploys were upgrading from underneath them due to the unpinned .nvmrc; see v6.4.2)

• fix(cli): avoid calling rw-vite-build via yarn #9624 by @jtoar

  This PR starts optimizing Redwood's memory usage during build. Redwood has always had memory problems on certain deploy providers. But many users have reported that v6 seems to be more problematic than usual. To address this, we started profiling CLI commands, looking at the amount of memory used and the number of processes spawned, starting with yarn rw build. We found that using yarn internally to call a binary seemed to increas memory by ~100 MB compared to using node. The number of processes spawned also dropped by two with this change. While this is far from conclusive, we'd like to get this change in an RC to see if it makes a noticeable difference for users.

  (If you're interested in profiling the amount of memory used by CLI commands, now's a great time to contribute!)

• fix(CLI): merge NODE_OPTIONS in yarn rw dev #9585 by @jtoar

  This PR merges user-specified NODE_OPTIONS with Redwood's, which is just the --enable-source-maps option:

  NODE_OPTIONS="--no-experimental-fetch" yarn rw dev
  # Resulting NODE_OPTIONS: --no-experimental-fetch --enable-source-maps
  

• chore: Update Testing documentation to link to How to Test Email/Mailer #9634 by @dthyresson

v6.5.1-rc.0

Patch Release

• fix(cli): avoid calling rw-vite-build via yarn #9624 by @jtoar

  This PR starts optimizing Redwood's memory usage during build. Redwood has always had memory problems on certain deploy providers. But many users have reported that v6 seems to be more problematic than usual. To address this, we started profiling CLI commands, looking at the amount of memory used and the number of processes spawned, starting with yarn rw build. We found that using yarn internally to call a binary seemed to increas memory by ~100 MB compared to using node. The number of processes spawned also dropped by two with this change. While this is far from conclusive, we'd like to get this change in an RC to see if it makes a noticeable difference for users.

  (If you're interested in profiling the amount of memory used by CLI commands, now's a great time to contribute!)

v6.5.0

Changelog

Fix

• fix: add custom inspect to work around a Prisma issue that causes console to hang #9623 by @ymc9

  Fixes #8817. (The related Prisma issue: prisma/prisma#18292.) Typing db in the Redwood console (yarn rw console) caused it to hang for ~10 seconds. This PR adds a workaround as suggseted by the Prisma team here: prisma/prisma#19648 (comment).

Core Dependencies

• update prisma to v5.5.2 #9403
• update vite to v4.5.1 #9627
• update @apollo/client to v3.8.8 #9600
• update storybook to v7.6.3 #9628
• update react-hook-form to v7.48.2 #9407
• update webpack to v5.89.0 #9408
• update typescript to 5.3.2 #9589

Docs

• Fix typos in tutorial #9516 by @MatrixFrog
• docs(docker): add troubleshooting section for python #9548 by @jtoar
• fix(docker): correct links, fix typos #9551 by @jtoar
• Docker docs: Typo fixes #9552 by @Tobbe
• add documentation on mocking useParams in component test #9284 by @dustinsgoodman
• chore(private-set): Wrap profile page in <PrivateSet> instead of Private #9575 by @DonsWayo
• Add note about base 64 encoded event body #9595 by @tmikeschu

Dependencies

Click to see all upgraded dependencies

• fix(deps): update dependency graphql-sse to v2.3.0 #9406
• chore(deps): update dependency @clerk/types to v3.58.0 #9431
• chore(deps): update dependency @azure/msal-browser to v2.38.3 #9421
• chore(deps): update dependency graphql-scalars to v1.22.4 #9426
• chore(deps): update dependency @auth0/auth0-spa-js to v2.1.2 #9420
• chore(deps): update dependency @clerk/clerk-react to v4.28.0 #9430
• chore(deps): update dependency @envelop/types to v4.0.1 #9424
• fix(deps): update dependency @graphql-yoga/plugin-defer-stream to v2.0.5 #9439
• fix(deps): update dependency fast-glob to v3.3.2 #9442
• fix(deps): update dependency @graphql-tools/utils to v10.0.8 #9438
• fix(deps): update dependency systeminformation to v5.21.17 #9446
• fix(deps): update dependency jsonwebtoken to v9.0.2 #9443
• fix(deps): update dependency semver to v7.5.4 #9445
• fix(deps): update dependency @envelop/on-resolve to v3.0.3 #9436
• fix(deps): update dependency nodemailer to v6.9.7 #9444
• fix(deps): update dependency @graphql-yoga/plugin-graphql-sse to v2.0.5 #9440
• fix(deps): update dependency @simplewebauthn/browser to v7.4.0 #9454
• chore(deps): update dependency firebase to v10.6.0 #9449
• fix(deps): update dependency firebase-admin to v11.11.0 #9458
• fix(deps): update dependency @testing-library/user-event to v14.5.1 #9455
• chore(deps): update dependency supertokens-node to v15.2.1 #9466
• fix(deps): update dependency jwks-rsa to v3.1.0 #9467
• fix(deps): update opentelemetry-js monorepo #9468
• fix(deps): update typescript-eslint monorepo to v5.62.0 #9469
• chore(deps): update dependency nodemon to v3 #9470
• fix(deps): update dependency @react-email/render to v0.0.9 #9473
• fix(deps): update dependency @whatwg-node/fetch to v0.9.14 #9474
• chore(deps): update dependency @simplewebauthn/server to v7.4.0 #9480
• fix(deps): update dependency uuid to v9.0.1 #9477
• fix(deps): update dependency whatwg-fetch to v3.6.19 #9478
• chore(deps): update dependency @supabase/supabase-js to v2.38.4 #9482
• chore(deps): update dependency @testing-library/react to v14.1.0 #9488
• fix(deps): update dependency ci-info to v3.9.0 #9490
• fix(deps): update dependency smtp-server to v3.13.0 #9494
• fix(deps): update dependency envinfo to v7.11.0 #9491
• fix(deps): update dependency resend to v1.1.0 #9493
• chore(deps): update dependency @testing-library/jest-dom to v5.17.0 #9487
• chore(deps): update dependency autoprefixer to v10.4.16 #9502
• fix(deps): update dependency eslint-plugin-import to v2.29.0 #9499
• fix(deps): update dependency eslint-config-prettier to v8.10.0 #9498
• fix(deps): update dependency eslint to v8.53.0 #9497
• fix(deps): update dependency @types/aws-lambda to v8.10.126 #9503
• fix(deps): update dependency eslint-plugin-jsx-a11y to v6.8.0 #9500
• fix(deps): update dependency eslint-plugin-react to v7.33.2 #9501
• fix(deps): update dependency @clerk/clerk-sdk-node to v4.12.21 #9505
• fix(deps): update dependency @types/node to v18.18.9 #9504
• fix(deps): update dependency @types/jest to v29.5.8 #9508
• fix(deps): update dependency @vscode/ripgrep to v1.15.6 #9538
• chore(deps): update dependency @playwright/test to v1.40.0 #9565
• chore(deps): update dependency @supabase/supabase-js to v2.38.5 #9563
• fix(deps): update dependency core-js to v3.33.3 #9564
• chore(deps): update dependency @testing-library/react to v14.1.2 #9569
• fix(deps): update dependency eslint to v8.54.0 #9571
• chore(deps): update dependency @clerk/clerk-react to v4.28.1 #9598
• fix(deps): update dependency @clerk/clerk-sdk-node to v4.12.22 #9601
• chore(deps): update dependency @supabase/supabase-js to v2.39.0 #9603
• chore(deps): update dependency @playwright/test to v1.40.1 #9599
• fix(deps): update dependency @whatwg-node/server to v0.9.18 #9602
• fix(deps): update docusaurus monorepo to v3.0.1 #9608
• fix(deps): update dependency graphql-sse to v2.4.0 #9607
• fix(deps): update dependency fs-extra to v11.2.0 #9606
• fix(deps): update graphql-tools monorepo #9609
• chore(deps): update dependency nodemon to v3.0.2 #9615
• fix(deps): update dependency @react-email/render to v0.0.10 #9616
• fix(deps): update dependency systeminformation to v5.21.20 #9617
• fix(deps): update dependency eslint to v8.55.0 #9629
• chore(deps): update dependency @clerk/clerk-react to v4.28.2 #9625

v6.4.2

Patch Release

• fix(crwa): pin Node.js version in .nvmrc #9614 by @jtoar

  Netlify deploys were failing on Node.js v20 with the following Prisma error:

  Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".
  This happened because Prisma Client was generated for "debian-openssl-1.1.x", 
  but the actual deployment required "rhel-openssl-3.0.x"
  

  Netlify uses the .nvmrc to determine the Node.js version. It takes precedence over other ways of specifying the Node.js version like the NODE_VERISON env var.

  This PR pins the Node.js version to v18 in the .nvmrc. This change only affects for new projects; if you're deploying to Netlify and seeing a similar error, simply replace the version in your .nvmrc with the following:

  v18
  

v6.4.1

Patch Release

• fix(deps): update @types/react to v18.2.37 #9391 by @leahincom

  Fixes the Argument of type 'Element' is not assignable to parameter of type 'ReactNode'.ts(2345) TS error in web/src/entry.client.tsx.

• fix(cli): Remove boxen from default error output #9568 by @Josh-Walker-GM

  There are too many cases where drawing a box around the CLI's default error output causes readability issues. This PR swaps the box for colored horizontal dividers.

• 9316/update mantine setup #9388 by @bnn1

  Fixes #9316. Mantine migrated to using CSS in v7 and now requires additional setup.

• fix: Prevent rw graphiql setup from breaking with encryptSession error #9582 by @staticshock

  Fixes #9581, which was a CLI regression introduced in #9350.

• Tell the shell how to run the rw-vite-xx bins #9576 by @orta

  Adds shebangs to Vite scripts that were missing them.

• Added prompt, if the directory already exists #9362 by @ahaywood

  In yarn create redwood-app, if the user specified a directory that already exists, the app would quit. Now they're presented with an additional prompt.

• 💬 Added details for using GitPod within Create Redwood App #9364 by @ahaywood

  In yarn create redwood-app, if the user encounters an issue with Node or Yarn, they'll see an option for using Gitpod alongside the error.

• Experimental Dockerfile: Fix typo in setup command #9577 by @Tobbe

• fix: Remove "god code" typos from auth READMEs #9583 by @staticshock

v6.4.0

Changelog

Features

• dbAuth: Unique session cookie name per port #9248 by @Tobbe

  Previously, when using dbAuth, you couldn't run two different Redwood apps at the same time on different ports. One app would overwrite the session cookie used by the other, and vice versa. They both used the same cookie name (session), and browsers distinguish cookies by hostname, not port.

  This PR lets users configure the cookie name they want to use by setting cookie.name in their api/src/functions/auth.ts file:

  // api/src/functions/auth.ts
  
  const authHandler = new DbAuthHandler(event, context, {
    // ...
  
    cookie: {
      name: 'session_%port%',
  
      // The cookie's attributes have moved to `cookie.attributes`:
      attributes: {
        // ...
      }
    },
  })

  If that option isn't set, it defaults to the old name (session) for backwards compatibility. In a similar vein, DbAuthHandler still handles all the properties that are now nested in cookie.attributes at the top level.

• <PrivateSet> #9303 by @Tobbe

  Fixes #2562, #9304, and https://community.redwoodjs.com/t/private-route-error-with-7-0-0-canary-347/5337. This PR deprecates the Router's <Private> component and the private prop on the Router's <Set> component. In their place, it introduces a new Router component, <PrivateSet>.

  Starting in this release, you'll see strikethroughs in your IDE when you use <Private> or the private prop on <Set>. They still work just as they did, but they'll be removed in a future major release, and <PrivateSet> is little more than a new name. The reason for the change is that in strict mode, private is a reserved word and there were just some bugs we couldn't fix without changing the name.

• feat(cli): Setup command for mailer #9335 by @Josh-Walker-GM

  This PR adds a setup command for the mailer:

  yarn rw setup mailer
  

  and adds functionality that enables it to conditionally use an in-memory handler for tests and the studio handler for development if those dependencies are available.

  Check out the mailer docs for more: https://redwoodjs.com/docs/mailer.

Fixes

• Fix infinite loops on nested private routes with roles #9204 by @KrisCoulson

  Fixes #9131. This restores the Router's ability to handle multiple nested routes with different levels of authentication and redirect contexts.

• fix(types): Generate maps to allow improved "go to definition" behaviour #9269 by @Josh-Walker-GM

  Fixes #5862 and #2867. Previously, navigating to the definition of cells, components, layouts, pages, etc. would lead to the .d.ts file. This could be pretty frustrating if you're used to flying between definitions. This PR generates basic definition/source mappings for directory-mapped modules, cell mirrors, router pages, and route links.

• Fix Set wrapper type so you can have an array of wrappers #9314 by @Tobbe

  Fixes #9313. This PR lets you do something like this in your web/src/Routes.tsx without type errors (notice the array of wrappers):

  const Routes = () => {
    return (
      <Router>
        <Set wrap={[Wrapper]}>
          <Route path="/" page={HomePage} name="home" />
        </Set>
        {/* ... */}
      </Router>
    )
  }

• Don't remount wrap components when navigating within Set #9312 by @Tobbe

  Fixes #9105. This PR assigns each Set a unique id and uses that id as a key when rendering all the wrapper components.

• preview stats when building storybook for Chromatic "TurboSnap" #9462 by @majimaccho

  yarn rw storybook --build didn't generate a preview-stats.json required for Chromatic's TurboSnap feature.

Core Dependencies

• update storybook monorepo to v7.4.6 #9256
• update prisma monorepo to v5.6.0 #9447
• update babel monorepo to v7.23.3 #9450
• update fastify to v4.24.3 #9457
• update yarn to v3.7.0 #9489
• update vite to v4.5.0 #9328

Docs

• Fix typos, removing erroneous apostrophes from personal possessive pronouns #9216 by @Philzen
• Fix broken link to most recent jest config example #9266 by @Philzen
• Fix TypeScript code highlighting (Chapter 6: Comments – Testing the service) #9267 by @Philzen
• Clarify Auth0 Configuration #9238 by @jdrbc
• docs: add missing await in service validation example #9243 by @G-Rath
• docs: Clarifies the testimonial section of the What is Redwood documentation #9207 by @jdrbc
• fix (docs): use default markdown numbered list #9265 by @esteban-url
• Fix typo in RBAC @requireAuth example #9286 by @Philzen
• Fix links to Prisma n:m relationship docs #9285 by @Philzen
• docs: How to Use Prisma Client Extensions with DB Client and Logging #9283 by @dthyresson
• docs(mailer): Initial mailer docs #9363 by @Josh-Walker-GM
• Added missing type to routing-params.md #9377 by @pr0h0
• Update dbauth-passwordless.md #9357 by @brendandonahue
• docs: Update Deployment Docs to Provide Guidance on Extending the Timeout Duration in Vercel #9370 by @dinakartumu

Experimental features

Note

These features aren't officially released, but are included here for completeness since they're in this version. They're usable, but aren't fully documented and their API may change in future releases.

• feat: add experimental docker setup command #9024 by @jtoar

  This release features the first iteration of Redwood's Dockerfile and compose files. Thanks to everyone who participated in the container working group! Get started with the experimental setup command:

  yarn rw exp setup-docker
  

  And consult the docs here if you have any questions: https://redwoodjs.com/docs/docker. Feedback welcome!

• feat: Support GraphQL Subscriptions in Apollo Client using SSE links #9009 by @dthyresson

  This PR adds support for GraphQL SSE (Server Sent Events) in both Redwood's GraphQL Server and RedwoodApolloProvider if realtime is enabled. For more on the status of realtime, see https://community.redwoodjs.com/t/redwoodjs-realtime/5002.

• feature: Support defer and stream GraphQL Directives in RedwoodRealtime #9235 by @dthyresson

• feat(cli-helpers): Root package install and RWJS env var #9296 by @Josh-Walker-GM

  This PR adds a few helper functions for installing packages in a Redwood app's root workspace and for setting the RWJS_CWD env var correctly.

• feature: Adds utility functions to add envars and update redwood.toml #9324 by @dthyresson

Dependencies

Click to see all upgraded dependencies

• chore(deps): update dependency @clerk/types to v3.52.0 #9213
• fix(deps): update dependency @clerk/clerk-sdk-node to v4.12.6 #9214
• chore(deps): update dependency @clerk/clerk-react to v4.25.1 #9212
• chore(deps): update dependency firebase to v10.4.0 #9203
• chore(deps): update dependency rimraf to v5.0.5 #9360
• fix(deps): update dependency concurrently to v8.2.2 #9361
• chore(deps): update dependency tailwindcss to v3.3.5 #9378
• fix(deps): update dependency msw to v1.3.2 #9379
• fix(deps): update dependency core-js to v3.33.2 #9293
• fix(deps): update apollo graphql packages #9418
• fix(deps): update dependency pino to v8.16.2 #9476
• fix(deps): update dependency prism-react-renderer to v2.2.0 #9492