Skip to content
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.4.3 #482

Merged
merged 1 commit into from
Apr 27, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 12, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@redwoodjs/api (source) 7.3.2 -> 7.4.3 age adoption passing confidence
@redwoodjs/auth (source) 7.3.2 -> 7.4.3 age adoption passing confidence
@redwoodjs/auth-dbauth-api (source) 7.3.2 -> 7.4.3 age adoption passing confidence
@redwoodjs/auth-dbauth-web (source) 7.3.2 -> 7.4.3 age adoption passing confidence
@redwoodjs/core (source) 7.3.2 -> 7.4.3 age adoption passing confidence
@redwoodjs/forms (source) 7.3.2 -> 7.4.3 age adoption passing confidence
@redwoodjs/graphql-server (source) 7.3.2 -> 7.4.3 age adoption passing confidence
@redwoodjs/router (source) 7.3.2 -> 7.4.3 age adoption passing confidence
@redwoodjs/vite (source) 7.3.2 -> 7.4.3 age adoption passing confidence
@redwoodjs/web (source) 7.3.2 -> 7.4.3 age adoption passing confidence

Release Notes

redwoodjs/redwood (@​redwoodjs/api)

v7.4.3

Compare Source

Patch Release

v7.4.2

Compare Source

Patch Release
  • fix(cli): avoid npx during upgrade command (#​10479) by @​Josh-Walker-GM

    This change fixes a problem with the yarn rw upgrade command when you don't have npx installed. If you don't have npx 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, the npx command will be logged to the console when you run yarn 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 the redirect 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 of redirect 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:

    <Router>
      <Route path="/" page={HomePage} name="home" />
      <PrivateSet unauthenticated="home">
        <Route path="/admin" page={AdminPage} name="admin" />
      </PrivateSet>
    </Router>

    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

    <Router>
      <Route path="/" page={HomePage} name="home" />
      <Route path="/no-longer-exists" redirect="home" />
    </Router>

    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
  • fix(deps): update docusaurus monorepo to v3.1.1 #​10337
  • fix(deps): update graphqlcodegenerator monorepo #​10338
  • fix(deps): update opentelemetry-js monorepo #​10339
  • fix(deps): update dependency @​graphql-codegen/client-preset to v4.2.5 #​10349
  • fix(deps): update dependency html-webpack-plugin to v5.6.0 #​10352
  • chore(deps): update dependency supertokens-auth-react to v0.39.1 #​10347
  • chore(deps): update babel monorepo #​10363
  • chore(deps): update dependency firebase to v10.11.0 #​10366

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Copy link

netlify bot commented Apr 12, 2024

Deploy Preview for superstore-redwood-stripe ready!

Name Link
🔨 Latest commit 3b09244
🔍 Latest deploy log https://app.netlify.com/sites/superstore-redwood-stripe/deploys/662c57f0750b5a0008719b8a
😎 Deploy Preview https://deploy-preview-482--superstore-redwood-stripe.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@renovate renovate bot assigned jtoar Apr 13, 2024
@renovate renovate bot force-pushed the renovate/redwood-monorepo branch from 0a1db4b to f72a518 Compare April 13, 2024 19:03
@renovate renovate bot changed the title Update redwood monorepo to v7.4.0 Update redwood monorepo to v7.4.1 Apr 13, 2024
@renovate renovate bot force-pushed the renovate/redwood-monorepo branch from f72a518 to b53f83f Compare April 19, 2024 22:16
@renovate renovate bot changed the title Update redwood monorepo to v7.4.1 Update redwood monorepo to v7.4.2 Apr 19, 2024
@renovate renovate bot force-pushed the renovate/redwood-monorepo branch from b53f83f to 6812263 Compare April 23, 2024 17:46
@renovate renovate bot changed the title Update redwood monorepo to v7.4.2 Update redwood monorepo to v7.4.3 Apr 23, 2024
@renovate renovate bot enabled auto-merge (squash) April 26, 2024 23:23
@renovate renovate bot force-pushed the renovate/redwood-monorepo branch from 6812263 to 71aadb4 Compare April 26, 2024 23:23
@renovate renovate bot force-pushed the renovate/redwood-monorepo branch from 71aadb4 to 3b09244 Compare April 27, 2024 01:42
@renovate renovate bot merged commit 6bee314 into main Apr 27, 2024
4 of 5 checks passed
@renovate renovate bot deleted the renovate/redwood-monorepo branch April 27, 2024 01:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant