fix(deps): update @redwoodjs packages to v7 (major) #4599
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.6.4
->7.6.3
6.6.4
->7.6.3
6.6.4
->7.6.3
6.6.4
->7.6.3
6.6.4
->7.6.3
6.6.4
->7.6.3
6.6.4
->7.6.3
Release Notes
redwoodjs/redwood (@redwoodjs/api)
v7.6.3
Compare Source
Patch Release
fix(cli): Fix issues with Serverless deployments in 7.x (#10646) by @jwwisgerhof
Serverless deployments were not functional since an internal update in the last minor versions. This change updates the NFT packer to a more modern import system which resolves the issue.
fix(cli): Directive generator command was not creating files (#10698) by @dthyresson
The change fixes a regression in the directive generator where files were not created.. For more information see this issue.
v7.6.2
Compare Source
Patch Release
fix(cli): Correct baremetal deploy command construction (#10675) by @Josh-Walker-GM
We correct a bug in the CLI introduced in the prior patch for baremetal deployments.
v7.6.1
Compare Source
Patch Release
fix(cli): Handle case for no arguments for verbose baremetal deploy (#10663) by @Josh-Walker-GM
The change corrects a bug during baremetal deployments when using the
--verbose
flag. See #10654 for more details.v7.6.0
Compare Source
Changelog
feat(cli): Add experimental setup command for React Compiler (#10574) by @Josh-Walker-GM
You can now use
yarn rw exp setup-react-compiler
to enable the experimental React Compiler. See our forum post for more information and feedback.fix(cli): Add deprecation notice for edgio deployment (#10551) by @Josh-Walker-GM
This change adds notices to the CLI and our documentation site to inform you that the edgio deployment provider is now deprecated as of v7.
Added warning note to not add WebAuthn (#10231) by @pantheredeye
Adds a warning to the tutorial telling users not to add WebAuthn as it's not supported by the generated login pages the tutorial uses.
fix(functions): Fix context variable warning/error (#10556) by @Tobbe
In a newly generated function there's a warning/error in the JSDoc that also prevents VSCode from showing the correct information. This change corrects this problem.
patch(crwa): Fix small annoyances (formatting, spell-check) (#10651) by @Tobbe
This change corrects a few typo errors and improves the formatting of our template files.
Docs: QoL Updates to Contributing.md (#10561) by @pantheredeye
Quality of life updates for the contributing doc (the document in the root of the main repository).
Dependencies
Click to see all upgraded dependencies
v7.5.1
Compare Source
Patch Release
Fix radio button null element default prop to use correct input (#10510) by @jason-curtis
This change fixes an issue with the
defaultChecked
field when using the scaffold generator with an enum. You should now see correct code generated to determine if the default is checked or unchecked.fix(functions): Mock context in function test template (#10555) by @Tobbe
Currently if you switch on TypeScript strict mode in a Redwood project you will get red squiggles in our default function tests that we create when users generate new functions. This change corrects this particular error by providing the correct function parameter in the generated code.
v7.5.0
Compare Source
Changelog
feat(upgrade): Use GitHub token if available when downloading patches (#10515) by @Tobbe
When you upgrade via
yarn rw upgrade
and require yarn patches, we will now use a GitHub token if it is available in your environment when fetching the git tree from GitHub. We supportGH_TOKEN
,GITHUB_TOKEN
andREDWOOD_GITHUB_TOKEN
as the env var names.feat(baremetal): Add verbose output to ssh exec (#10525) by @Tobbe
This change adds additional logging to the ssh during baremetal when you use
--verbose
. Allowing you to see exactly what SSH commands are being run, and in what path.Standard output without
--verbose
- this remains unchangedBefore (verbose output)
After (verbose output)
feat(baremetal): Add more details to error messages (#10527) by @Tobbe
Now when an ssh command execution fails the error message will additionally include the directory it was executed in and the full stderr message
Before
After
Add redwood.toml to
yarn rw info
(#10518) by @TobbeThe project
redwood.toml
file is now included in theyarn rw info
output to make it easier and faster to provide enough details for issues to be debugged quicklyBefore
After
Add any ENV vars that should be available to the web side to this array
See https://redwoodjs.com/docs/environment-variables#web
v7.4.3
Compare Source
Patch Release
Modified type for describeScenario (https://github.com/redwoodjs/redwood/pull/10468) by @cjreimer
This change corrects the return type of
getScenario
. See: https://github.com/redwoodjs/redwood/pull/10468 for more information.v7.4.2
Compare Source
Patch Release
fix(cli): avoid
npx
during upgrade command (#10479) by @Josh-Walker-GMThis change fixes a problem with the
yarn rw upgrade
command when you don't havenpx
installed. If you don't havenpx
installed you will now have to manually run a command to dedupe dependencies rather than this being done for you automatically during the upgrade command. If this is the case, thenpx
command will be logged to the console when you runyarn rw upgrade
. See #10466 for more information.fix: Fixes Unknown Fragment issues due to GraphQL Tag type mismatch in web (#10357) by @dthyresson
Users reported in #10322 an incompatibility with fragments and when using gql from global web. The TS errors were caused by the global web gql type not being compatible with the standard graphql-tag type. This change corrects this issue.
v7.4.1
Compare Source
Patch Release
chore(deps): update dependency typescript to v5.4.5 (#10452)
This dependency upgrade includes fixes that address a bug that caused auto-complete and auto-import functionality to be broken in Javascript projects.
v7.4.0
Compare Source
Changelog
docs(redirect): Add docs for redirect routes (#10374) by @Tobbe
There were no docs for
<Route path="/some/path" redirect="/some/other/path" />
. This change introduces docs for theredirect
prop.feat(router): Allow redirect routes to use route names as target (#10376) by @Tobbe
When specifying a redirect route like
<Route path="/simple" redirect="/newSimple" name="simple" />
the value ofredirect
is the path of the page the user should be redirected to. However, the paths can be long and annoying to type out. And if they ever change the redirect would now be broken.Also, for private routes we do this:
Here, if a user isn't authenticated, the user will be redirected to the
home
route. Notice how the target route is specified by its name (home
) instead of its path (/
).With this it's now also possible to redirect using the name of the target route, making our route behavior more consistent. So this will now work
Old style paths still works. The logic is super simple. If the
redirect
value starts with/
it's assumed to be a path. If not, it's assumed to be a route name. This should make this change fully backwards compatible.docs: Adds important admonition for generate dbAuth to clarify that must setup dbAuth not just generate the pages (#10293) by @dthyresson
docs: Add information about how to turn off Prisma/db operations during a Vercel deploy to reduce Postgres Storage use (#10294) by @dthyresson
chore(CLI): build with esbuild (#10323) by @jtoar
This change speeds up the CLI by up to 50ms.
Dependencies
Click to see all upgraded dependencies
v7.3.2
Compare Source
Patch Release
fix(auth): Handle when authorization header is lowercased (#10442) by @dac09
This fix handles an authentication error that occurred when the 'Authorization' header was presented in lowercase as 'authorization'.
v7.3.1
Compare Source
Patch Release
fix(vercel): write
vercel.json
as a part of setup (#10355) by @jtoarThis fix smooths initial deploys to Vercel by writing a
vercel.json
file that specifies an env var that enables Corepack. Users that already successfully deploy to Vercel don't need to introduce this file.fix(cli): only show webpack options for dev if
bundler = "webpack"
(#10359) by @jtoarA few flags for
yarn rw dev
don't apply to Vite but are shown nevertheless. One of them,watchNodeModules
, is legacy at this point. It's only useful for testing out framework changes on a project using webpack. It makes the webpack dev server reload on changes to node_modules. The other,forward
(aliasedfwd
) isn't fundamentally Webpack specific, but has been broken for quite a while because the fix is nontrivial. It seems better to hide these flags for now, otherwise we're just advertising broken or no-op behavior.v7.3.0
Compare Source
Changelog
fix(deps): update prisma monorepo to v5.11.0 #10262
fix(deps): update dependency @apollo/client to v3.9.9 #10297
chore(deps): update dependency typescript to v5.4.3 #10308
fix(cli): Update build and serve to handle the absence of the api side (#10265) by @Josh-Walker-GM
This change allows you to successfully build your app with
yarn rw build
even when you choose to totally delete your api side. Previously you would have seen errors related to both Prisma and GraphQL. It also improves the error messages produced byyarn rw serve
in this case.fix(esm): get lint working (#10152) by @jtoar
This PR fixes
yarn rw lint
and some generators and setup commands for ESM projects.Before projects would get the following error:
chore(babel-config): Fix error message grammar (#10280) by @Tobbe
Fixed the grammar of the error message you see if you have more than one Page file in a single Page directory.
Fix react docs links (#10278) by @rxx
Update deployment.md (#10267) by @LAdanimo
Update Prisma Dataguide Link (#10254) by @pantheredeye
docs: fix typo on router page (#10251) by @thenewnickyzz
Update first-test.md (#10244) by @LAdanimo
Dependencies
Click to see all upgraded dependencies
v7.2.0
Compare Source
v7.1.3
Compare Source
Patch Release
fix(dbAuth): restore behavior of checking whether a search query is present (#10204) by @cannikin
Previously dbAuth would check whether or not query string variables were present at all before invoking the proper function. During a refactor we updated this code to assume a query would always be present. Which it would be during normal browser behavior. But, we had a complaint from a user who relied on this optional check in one of their tests. So we're restoring the optional check here.
v7.1.2
Compare Source
Patch Release
Fix storybook preview config path reference (#10160) by @pvenable
This change fixes a small regression related to storybook preview config which resulted it in your config not being loaded. Details of this issue can be found in #10113.
v7.1.1
Compare Source
Patch Release
Enable CSS nesting syntax by default when using Tailwind (#10116) by @cannikin
This lets you use nested CSS syntax in your
web/src/index.css
right after you install Tailwind.fix(setup realtime): remove "exp" from suggested setup command (#10151) by @jtoar
The realtime setup command was still suggesting running the experimental server file setup command if the server file wasn't setup. This fixes it so that it points users to the stable setup command,
yarn rw setup server-file
, instead.fix(esm): use CJS wrapper for ESM default interop (#10119) by @jtoar
This PR builds on the work started in https://github.com/redwoodjs/redwood/pull/10083 around ESM. One of the caveats of that PR was that the default export from
@redwoodjs/vite
broke. The workaround was referencing thedefault
property on the Redwood Vite plugin, likeredwood.default()
. This fixes the ES module default export interoperability so that no change is necessary in switching between module types.v7.1.0
Compare Source
v7.0.7
Compare Source
v7.0.6
Compare Source
v7.0.5
Compare Source
v7.0.4
Compare Source
v7.0.3
Compare Source
v7.0.2
Compare Source
v7.0.1
Compare Source
v7.0.0
Compare Source
Configuration
📅 Schedule: Branch creation - "after 5:00am every weekday, before 7:00am every weekday,every weekend" (UTC), Automerge - "before 7am every weekday" (UTC).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.