-
Notifications
You must be signed in to change notification settings - Fork 3
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 dependency @redwoodjs/cli-helpers to v5.4.3 #134
Conversation
|
32d8e6b
to
5b86dea
Compare
5b86dea
to
dfe0f60
Compare
dfe0f60
to
c094709
Compare
3c0c5d9
to
f808307
Compare
f808307
to
33562cd
Compare
33562cd
to
1545174
Compare
b28973e
to
7221d35
Compare
7221d35
to
4cef1c5
Compare
4cef1c5
to
211e601
Compare
211e601
to
c68af9a
Compare
c68af9a
to
beaab31
Compare
beaab31
to
3a2253b
Compare
1f72af1
to
7dc7f72
Compare
7dc7f72
to
59f111c
Compare
59f111c
to
ed00022
Compare
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
This PR contains the following updates:
5.3.1
->5.4.3
Release Notes
redwoodjs/redwood (@redwoodjs/cli-helpers)
v5.4.3
Compare Source
Patch Release
This patch release includes an update to Prisma and a fix for Serverless deploy (see https://github.com/redwoodjs/redwood/issues/8804)
v5.4.2
Compare Source
Patch Release
This patch release configures the the new
unsupported-route-components
ESLint rule to only run on theweb/src/Routes.{js,jsx,tsx}
file:v5.4.1
Compare Source
Patch Release
This patch release fixes https://github.com/redwoodjs/redwood/issues/8789, where the new
@redwoodjs/eslint-plugin
package wasn't listed as one of@redwoodjs/eslint-config
's dependencies:v5.4.0
Compare Source
Changelog
This release features a great new addition to Redwood's prerendering capabilities: Redwood now preloads the Apollo Client Cache on the frontend with the data retrieved during prerendering. Where Cells are used, this allows the data served during prerender to match the client data.
In addition to that, there's plenty more features and fixes in this release like:
We plan for this release to be the last v5 release before the next major, but will of course release patches as appropriate.
Lastly, if you're using Clerk authentication and haven't seen the new auth decoder in the
v5.3.2
patch, please see the release notes and migration guide: https://github.com/redwoodjs/redwood/releases/tag/v5.3.2.Features
Fixed
setup ui windicss
(project is sunsetting) #8597 by @thedavidpriceDocs
services.md
#8577 by @BlackHawkSigmaChore
ScenarioData
JSDoc example #8545 by @BlackHawkSigmaproject:sync
ignore more files #8579 by @jtoarCore dependencies
Dependencies
Click to see all upgraded dependencies
v5.3.2
Compare Source
Patch Release
This patch adds a new auth decoder,
clerkAuthDecoder
to the@redwoodjs/auth-clerk-api
package and deprecates the existing one, which is simply namedauthDecoder
. We recommend that everyone using Clerk migrate to the new auth decoder unless you’re already using a custom one. The current auth decoder is subject to rate limiting.Background
First, a quick reminder on how auth works in Redwood. On a project's api side, there's two critical auth functions,
authDecoder
andgetCurrentUser
. They're both passed tocreateGraphQLHandler
inapi/src/functions/graphql.{ts,js}
:As the codeblock above shows,
authDecoder
comes from one of Redwood's auth packages (but you can write it yourself if you want), whilegetCurrentUser
comes from theapi/src/lib/auth.{ts,js}
file—it's a function that you own in your project.These functions are used together internally by Redwood. While this is a simplification, basically
authDecoder
's return value is the first argument togetCurrentUser
, like this:Migration Path
The last thing you want is your project's
authDecoder
getting rate limited! Here's how to migrate:yarn rw upgrade
api/src/functions/graphql.{ts,js}
, import the new auth decoder,clerkAuthDecoder
, as theauthDecoder
function from@redwoodjs/auth-clerk-api
:api/src/lib/auth.{ts,js}
, modify thegetCurrentUser
function accordingly and customize the session token on your Clerk application's dashboard (see https://clerk.com/docs/request-authentication/customizing-session-tokens)The modifications you'll have to make will be specific to your project. The
getCurrentUser
function's first argument,decoded
, will be different. It'll still be an object, but by default, it has much fewer props than before. To illustrate the difference, let’s look at an example of what thedecoded
parameter to thegetCurrentUser
function is before and after:It’s unlikely that you were using all of its properties before. But if you were using Clerk for user management and not just for authentication, you were certainly using some. Luckily it's easy to add them back to the object—all you have to do is customize the session token on your Clerk application's dashboard. See Clerk's docs here: https://clerk.com/docs/request-authentication/customizing-session-tokens.
Changelog
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 this update again.
This PR has been generated by Mend Renovate. View repository job log here.