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.

Sign up for GitHub

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

Jump to bottom

fix(deps): update all non-major dependencies (minor) #188

Merged
merged 1 commit into from
Dec 17, 2023
Merged

fix(deps): update all non-major dependencies (minor) #188

merged 1 commit into from
Dec 17, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 13, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@clerk/nextjs (source) 4.27.7 -> 4.28.1 age adoption passing confidence
@tanstack/query-async-storage-persister (source) 5.13.4 -> 5.14.1 age adoption passing confidence
@tanstack/react-query (source) 5.13.4 -> 5.14.1 age adoption passing confidence
@tanstack/react-query-devtools (source) 5.13.5 -> 5.14.1 age adoption passing confidence
@tanstack/react-query-persist-client (source) 5.13.4 -> 5.14.1 age adoption passing confidence
eslint (source) 8.55.0 -> 8.56.0 age adoption passing confidence
openai 4.20.1 -> 4.23.0 age adoption passing confidence
react-router-dom (source) 6.20.1 -> 6.21.0 age adoption passing confidence
vaul (source) 0.7.9 -> 0.8.0 age adoption passing confidence

Release Notes

clerk/javascript (@​clerk/nextjs)

v4.28.1

Compare Source

Patch Changes

v4.28.0

Compare Source

Minor Changes

  • Introduce Protect for authorization. (#​2309) by @​panteliselef

    Changes in public APIs:

    • Rename Gate to Protect
    • Support for permission checks. (Previously only roles could be used)
    • Remove the experimental tags and prefixes
    • Drop some from the has utility and Protect. Protect now accepts a condition prop where a function is expected with the has being exposed as the param.
    • Protect can now be used without required props. In this case behaves as <SignedIn>, if no authorization props are passed.
    • has will throw an error if neither permission or role is passed.
    • auth().protect() for Nextjs App Router. Allow per page protection in app router. This utility will automatically throw a 404 error if user is not authorized or authenticated.
      • inside a page or layout file it will render the nearest not-found component set by the developer
      • inside a route handler it will return empty response body with a 404 status code
Patch Changes
TanStack/query (@​tanstack/query-async-storage-persister)

v5.14.1

Compare Source

Version 5.14.1 - 12/17/2023, 2:28 PM

Changes
Fix
Docs
Other
Packages

v5.14.0

Compare Source

Version 5.14.0 - 12/15/2023, 12:01 PM

Changes
Feat
  • core: changing mutationKeys should reset observer (#​6511) (94154d7) by Dominik Dorfmeister
Docs
Other
  • Update config.json (e2d5da2) by Tanner Linsley
  • Update config.json (b3a73b0) by Tanner Linsley
  • Update config.json (5eb4f6d) by Tanner Linsley
  • Update config.json (2539b37) by Tanner Linsley
Packages
eslint/eslint (eslint)

v8.56.0

Compare Source

Features
  • 0dd9704 feat: Support custom severity when reporting unused disable directives (#​17212) (Bryan Mishkin)
  • 31a7e3f feat: fix no-restricted-properties false negatives with unknown objects (#​17818) (Arka Pratim Chaudhuri)
Bug Fixes
  • 7d5e5f6 fix: TypeError: fs.exists is not a function on read-only file system (#​17846) (Francesco Trotta)
  • 74739c8 fix: suggestion with invalid syntax in no-promise-executor-return rule (#​17812) (Bryan Mishkin)
Documentation
  • 9007719 docs: update link in ways-to-extend.md (#​17839) (Amel SELMANE)
  • 3a22236 docs: Update README (GitHub Actions Bot)
  • 54c3ca6 docs: fix migration-guide example (#​17829) (Tanuj Kanti)
  • 4391b71 docs: check config comments in rule examples (#​17815) (Francesco Trotta)
  • fd28363 docs: remove mention about ESLint stylistic rules in readme (#​17810) (Zwyx)
  • 48ed5a6 docs: Update README (GitHub Actions Bot)
Chores
openai/openai-node (openai)

v4.23.0

Compare Source

Full Changelog: v4.22.1...v4.23.0

Features
Chores

v4.22.1

Compare Source

Full Changelog: v4.22.0...v4.22.1

Chores
Documentation

v4.22.0

Compare Source

Full Changelog: v4.21.0...v4.22.0

Features
Chores

v4.21.0

Compare Source

Full Changelog: v4.20.1...v4.21.0

Features
  • client: support reading the base url from an env variable (#​547) (06fb68d)
Bug Fixes
  • correct some runTools behavior and deprecate runFunctions (#​562) (f5cdd0f)
  • prevent 400 when using runTools/runFunctions with Azure OpenAI API (#​544) (735d9b8)
Documentation
Build System
remix-run/react-router (react-router-dom)

v6.21.0

Compare Source

Minor Changes

  • Add a new future.v7_relativeSplatPath flag to implement a breaking bug fix to relative routing when inside a splat route. (#​11087)

    This fix was originally added in #​10983 and was later reverted in #​11078 because it was determined that a large number of existing applications were relying on the buggy behavior (see #​11052)

    The Bug
    The buggy behavior is that without this flag, the default behavior when resolving relative paths is to ignore any splat (*) portion of the current route path.

    The Background
    This decision was originally made thinking that it would make the concept of nested different sections of your apps in <Routes> easier if relative routing would replace the current splat:

    <BrowserRouter>
  <Routes>
    <Route path="/" element={<Home />} />
    <Route path="dashboard/*" element={<Dashboard />} />
  </Routes>
</BrowserRouter>

    Any paths like /dashboard, /dashboard/team, /dashboard/projects will match the Dashboard route. The dashboard component itself can then render nested <Routes>:

    function Dashboard() {
  return (
    <div>
      <h2>Dashboard</h2>
      <nav>
        <Link to="/">Dashboard Home</Link>
        <Link to="team">Team</Link>
        <Link to="projects">Projects</Link>
      </nav>

      <Routes>
        <Route path="/" element={<DashboardHome />} />
        <Route path="team" element={<DashboardTeam />} />
        <Route path="projects" element={<DashboardProjects />} />
      </Routes>
    </div>
  );
}

    Now, all links and route paths are relative to the router above them. This makes code splitting and compartmentalizing your app really easy. You could render the Dashboard as its own independent app, or embed it into your large app without making any changes to it.

    The Problem

    The problem is that this concept of ignoring part of a path breaks a lot of other assumptions in React Router - namely that "." always means the current location pathname for that route. When we ignore the splat portion, we start getting invalid paths when using ".":

    // If we are on URL /dashboard/team, and we want to link to /dashboard/team:
function DashboardTeam() {
  // ❌ This is broken and results in <a href="/dashboard">
  return <Link to=".">A broken link to the Current URL</Link>;

  // ✅ This is fixed but super unintuitive since we're already at /dashboard/team!
  return <Link to="./team">A broken link to the Current URL</Link>;
}

    We've also introduced an issue that we can no longer move our DashboardTeam component around our route hierarchy easily - since it behaves differently if we're underneath a non-splat route, such as /dashboard/:widget. Now, our "." links will, properly point to ourself inclusive of the dynamic param value so behavior will break from it's corresponding usage in a /dashboard/* route.

    Even worse, consider a nested splat route configuration:

    <BrowserRouter>
  <Routes>
    <Route path="dashboard">
      <Route path="*" element={<Dashboard />} />
    </Route>
  </Routes>
</BrowserRouter>

    Now, a <Link to="."> and a <Link to=".."> inside the Dashboard component go to the same place! That is definitely not correct!

    Another common issue arose in Data Routers (and Remix) where any <Form> should post to it's own route action if you the user doesn't specify a form action:

    let router = createBrowserRouter({
  path: "/dashboard",
  children: [
    {
      path: "*",
      action: dashboardAction,
      Component() {
        // ❌ This form is broken!  It throws a 405 error when it submits because
        // it tries to submit to /dashboard (without the splat value) and the parent
        // `/dashboard` route doesn't have an action
        return <Form method="post">...</Form>;
      },
    },
  ],
});

    This is just a compounded issue from the above because the default location for a Form to submit to is itself (".") - and if we ignore the splat portion, that now resolves to the parent route.

    The Solution
    If you are leveraging this behavior, it's recommended to enable the future flag, move your splat to it's own route, and leverage ../ for any links to "sibling" pages:

    <BrowserRouter>
  <Routes>
    <Route path="dashboard">
      <Route index path="*" element={<Dashboard />} />
    </Route>
  </Routes>
</BrowserRouter>

function Dashboard() {
  return (
    <div>
      <h2>Dashboard</h2>
      <nav>
        <Link to="..">Dashboard Home</Link>
        <Link to="../team">Team</Link>
        <Link to="../projects">Projects</Link>
      </nav>

      <Routes>
        <Route path="/" element={<DashboardHome />} />
        <Route path="team" element={<DashboardTeam />} />
        <Route path="projects" element={<DashboardProjects />} />
      </Router>
    </div>
  );
}

    This way, . means "the full current pathname for my route" in all cases (including static, dynamic, and splat routes) and .. always means "my parents pathname".

Patch Changes
  • Updated dependencies:
    • @remix-run/router@1.14.0
    • react-router@6.21.0
emilkowalski/vaul (vaul)

v0.8.0

Compare Source

What's Changed

New Contributors

Full Changelog: emilkowalski/vaul@v0.7.9...v0.8.0

Configuration

📅 Schedule: Branch creation - "after 9pm,before 9am" in timezone Asia/Shanghai, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

@renovate renovate bot added the renovate label Dec 13, 2023
@vercel Vercel
Copy link

vercel bot commented Dec 13, 2023 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
shiro ⬜️ Ignored (Inspect) Visit Preview Dec 17, 2023 4:48pm

@renovate renovate bot changed the title fix(deps): update dependency openai to v4.21.0 fix(deps): update all non-major dependencies (minor) Dec 13, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 12edf98 to 02fff16 Compare December 16, 2023 19:09
@Innei Innei enabled auto-merge (squash) December 17, 2023 12:09
@Innei Innei merged commit 13b5a52 into main Dec 17, 2023
2 of 3 checks passed
@renovate renovate bot deleted the renovate/all-minor-patch branch December 17, 2023 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Innei Innei Innei approved these changes

Assignees
No one assigned
Labels
renovate
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@Innei