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
Update redwood monorepo to v7 (major) #69
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/major-redwood-monorepo
base: main
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
3 times, most recently
from
April 20, 2022 01:47
d00255c
to
ac73d2f
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
2 times, most recently
from
April 27, 2022 10:24
c2ff2f0
to
48d4b3b
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
3 times, most recently
from
May 5, 2022 17:37
258e7b2
to
75732ec
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
3 times, most recently
from
May 13, 2022 12:33
eaf0091
to
fac9962
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
3 times, most recently
from
May 22, 2022 03:48
54db30f
to
34eee33
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
2 times, most recently
from
May 26, 2022 02:27
981ce94
to
9fe50eb
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
from
June 18, 2022 18:49
9fe50eb
to
74f36a2
Compare
renovate
bot
changed the title
Update redwood monorepo to v1 (major)
Update redwood monorepo to v2 (major)
Jun 18, 2022
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
from
September 25, 2022 21:21
74f36a2
to
2160eb5
Compare
renovate
bot
changed the title
Update redwood monorepo to v2 (major)
Update redwood monorepo to v3 (major)
Sep 25, 2022
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
from
March 16, 2023 21:23
2160eb5
to
df918ff
Compare
renovate
bot
changed the title
Update redwood monorepo to v3 (major)
Update redwood monorepo to v4 (major)
Mar 16, 2023
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
2 times, most recently
from
March 27, 2023 05:27
a7983c1
to
2ed99d1
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
from
April 18, 2023 06:00
2ed99d1
to
5ca7881
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
from
May 31, 2023 05:55
5ca7881
to
304607f
Compare
renovate
bot
changed the title
Update redwood monorepo to v4 (major)
Update redwood monorepo to v5 (major)
May 31, 2023
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
2 times, most recently
from
June 10, 2023 08:23
0ccb749
to
d6d1c2d
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
from
June 16, 2023 05:57
d6d1c2d
to
a238c32
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
from
September 22, 2023 05:17
f9de954
to
b881f7e
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
from
October 11, 2023 05:15
b881f7e
to
ac8ae1b
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
from
November 9, 2023 03:00
ac8ae1b
to
ebf7eb1
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
from
November 17, 2023 06:00
ebf7eb1
to
4b322b0
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
3 times, most recently
from
December 6, 2023 08:23
87e5383
to
58ee030
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
from
December 8, 2023 02:39
58ee030
to
c0a3aad
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
from
December 23, 2023 05:00
c0a3aad
to
8e18486
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
2 times, most recently
from
January 5, 2024 14:53
f630b5a
to
9186092
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
from
January 25, 2024 05:38
9186092
to
ae5f2d9
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
from
February 21, 2024 02:22
ae5f2d9
to
bb20ac0
Compare
renovate
bot
changed the title
Update redwood monorepo to v6 (major)
Update redwood monorepo to v7 (major)
Feb 21, 2024
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
3 times, most recently
from
February 29, 2024 05:15
3415ffc
to
076fa8e
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
3 times, most recently
from
March 8, 2024 18:00
c63b948
to
086115a
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
3 times, most recently
from
March 13, 2024 02:38
eef774b
to
186db2b
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
2 times, most recently
from
March 30, 2024 14:42
2184edb
to
58e8655
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
from
April 13, 2024 17:53
58e8655
to
6a0f2dc
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
2 times, most recently
from
April 24, 2024 20:52
a6c0b76
to
9712c9a
Compare
renovate
bot
force-pushed
the
renovate/major-redwood-monorepo
branch
from
May 9, 2024 05:49
9712c9a
to
7fa73bd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
0.47.1
->7.5.0
0.47.1
->7.5.0
0.47.1
->7.5.0
0.47.1
->7.5.0
0.47.1
->7.5.0
Release Notes
redwoodjs/redwood (@redwoodjs/core)
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.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
v6.6.4
Compare Source
v6.6.3
Compare Source
v6.6.2
Compare Source
v6.6.1
Compare Source
v6.6.0
Compare Source
v6.5.1
Compare Source
v6.5.0
Compare Source
v6.4.2
Compare Source
v6.4.1
Compare Source
v6.4.0
Compare Source
v6.3.3
Compare Source
v6.3.2
Compare Source
v6.3.1
Compare Source
v6.3.0
Compare Source
v6.2.3
Compare Source
v6.2.2
Compare Source
v6.2.1
Compare Source
v6.2.0
Compare Source
v6.1.1
Compare Source
v6.1.0
Compare Source
v6.0.7
Compare Source
v6.0.6
Compare Source
v6.0.5
Compare Source
v6.0.4
Compare Source
v6.0.3
Compare Source
v6.0.2
Compare Source
v6.0.1
Compare Source
v6.0.0
Compare Source
v5.4.3
Compare Source
v5.4.2
Compare Source
v5.4.1
Compare Source
v5.4.0
Compare Source
v5.3.2
Compare Source
v5.3.1
Compare Source
v5.3.0
Compare Source
v5.2.4
Compare Source
v5.2.3
Compare Source
v5.2.2
Compare Source
v5.2.1
Compare Source
v5.2.0
Compare Source
v5.1.5
Compare Source
v5.1.4
Compare Source
v5.1.3
Compare Source
v5.1.2
Compare Source
v5.1.1
Compare Source
v5.1.0
Compare Source
v5.0.6
Compare Source
v5.0.5
Compare Source
v5.0.4
Compare Source
v5.0.3
Compare Source
v5.0.2
Compare Source
v5.0.1
Compare Source
v5.0.0
Compare Source
v4.5.0
Compare Source
v4.4.3
Compare Source
v4.4.2
Compare Source
v4.4.1
Compare Source
v4.4.0
Compare Source
v4.3.1
Compare Source
v4.3.0
Compare Source
Changelog
Fixed
Docs
Core dependencies
Dependencies
Click to see all upgraded dependencies
v4.2.2
Compare Source
v4.2.1
Compare Source
v4.2.0
Compare Source
v4.1.4
Compare Source
v4.1.3
Compare Source
v4.1.2
Compare Source
v4.1.1
Compare Source
v4.1.0
Compare Source
v4.0.1
Compare Source
v4.0.0
Compare Source
v3.8.0
Compare Source
v3.7.1
Compare Source
v3.7.0
Compare Source
v3.6.1
Compare Source
v3.6.0
Compare Source
v3.5.0
Compare Source
v3.4.0
Compare Source
v3.3.2
Compare Source
v3.3.1
Compare Source
v3.3.0
Compare Source
v3.2.2
Compare Source
v3.2.1
Compare Source
v3.2.0
Compare Source
v3.1.2
Compare Source
v3.1.1
Compare Source
v3.1.0
Compare Source
v3.0.3
Compare Source
v3.0.2
Compare Source
v3.0.1
Compare Source
v3.0.0
Compare Source
v2.2.5
Compare Source
v2.2.4
Compare Source
v2.2.3
Compare Source
v2.2.2
Compare Source
v2.2.1
Compare Source
v2.2.0
Compare Source
v2.1.1
Compare Source
v2.1.0
Compare Source
v2.0.0
Compare Source
v1.5.2
Compare Source
v1.5.1
Compare Source
v1.5.0
Compare Source
v1.4.3
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 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.