chore(deps): bump @redwoodjs/router from 1.5.2 to 4.2.2

[dependabot]

Bumps @redwoodjs/router from 1.5.2 to 4.2.2.

Release notes

Sourced from @​redwoodjs/router's releases.

v4.2.2

Patch Release

• Allow passing an array of auth decoders to createGraphQLHandler #7685 by @​Tobbe
• fix(cli): disable rollbacks when using force #7679 by @​Josh-Walker-GM

v4.2.1

Patch Release

This release fixes redwoodjs/redwood#7691 where the GraphQL server couldn't read various properties on the request object.

v4.2.0

Security Release for Redwood Apps Using Clerk

Note

You can skip this notice if you're not using Clerk as an auth provider.

We've made a security improvement to the getCurrentUser function in the api-side Clerk auth template (PR here: redwoodjs/redwood#7668). Existing projects using Clerk as an auth provider should run the codemod or make the changes manually.

In detail, with Clerk, you can set privateMetadata on a user. (Note that you have to set data on this property via the Clerk API for there to be data there.) The template getCurrentUser was returning this data to the frontend by default, making it available to your frontend code when a user was logged in.

Clerk users should run this codemod:

npx @redwoodjs/codemods@canary update-clerk-get-current-user

Or make the changes manually:

 // api/src/lib/auth.ts
export const getCurrentUser = async (
decoded,
/* eslint-disable-next-line @​typescript-eslint/no-unused-vars /
{ token, type },
/ eslint-disable-next-line @​typescript-eslint/no-unused-vars */
{ event, context }
) => {
if (!decoded) {
logger.warn('Missing decoded user')
return null
}
</tr></table>

... (truncated)

Commits

• 0c754c8 v4.2.2
• 474684e v4.2.1
• 6ab3c87 v4.2.0
• a28b8f5 fix(deps): update dependency core-js to v3.28.0 (#7666)
• 99928e7 v4.1.4
• 4512e27 v4.1.3
• 4ecf4d3 v4.1.2
• daddcfa v4.1.1
• 9552159 v4.1.0
• 382dc25 fix(deps): update jest monorepo to v29.4.2 (#7581)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[netlify]

❌ Deploy Preview for redwoodblog-dev failed.

Name	Link
🔨 Latest commit	0221a7e
🔍 Latest deploy log	https://app.netlify.com/sites/redwoodblog-dev/deploys/63ffcf14550c76000820fd5b

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.