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 #306

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

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

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 11, 2025 •
edited
Loading

RicardoGEsteves all-non-major update, dependency @clerk/nextjs to v6.9.9

This PR contains the following updates:

Package Type Update Change OpenSSF New value Package file References
@clerk/nextjs (source) dependencies patch 6.9.6 -> 6.9.9 OpenSSF Scorecard ^6.9.6 package.json homepage, source
@hookform/resolvers (source) dependencies minor 3.9.1 -> 3.10.0 OpenSSF Scorecard ^3.4.2 package.json homepage, source
@prisma/client (source) dependencies minor 6.1.0 -> 6.2.1 OpenSSF Scorecard ^6.1.0 package.json homepage, source
@types/react (source) devDependencies patch 19.0.2 -> 19.0.6 OpenSSF Scorecard 19.0.6 package.json homepage, source
@types/react-dom (source) devDependencies patch 19.0.2 -> 19.0.3 OpenSSF Scorecard 19.0.3 package.json homepage, source
eslint-config-next (source) devDependencies patch 15.1.3 -> 15.1.4 OpenSSF Scorecard 15.1.4 package.json homepage, source
lucide-react (source) dependencies minor ^0.469.0 -> ^0.471.0 OpenSSF Scorecard ^0.471.0 package.json homepage, source
next (source) dependencies patch 15.1.3 -> 15.1.4 OpenSSF Scorecard 15.1.4 package.json homepage, source
openai dependencies minor 4.77.3 -> 4.78.1 OpenSSF Scorecard ^4.77.3 package.json source
prisma (source) devDependencies minor 6.1.0 -> 6.2.1 OpenSSF Scorecard 6.2.1 package.json homepage, source
react-markdown dependencies patch 9.0.1 -> 9.0.3 OpenSSF Scorecard ^9.0.1 package.json source
typescript (source) devDependencies patch 5.7.2 -> 5.7.3 OpenSSF Scorecard 5.7.3 package.json homepage, source
zustand dependencies patch 5.0.2 -> 5.0.3 OpenSSF Scorecard ^5.0.0 package.json source

Release Notes

clerk/javascript (@​clerk/nextjs)

v6.9.9

Compare Source

Patch Changes

v6.9.8

Compare Source

Patch Changes

v6.9.7

Compare Source

Patch Changes
react-hook-form/resolvers (@​hookform/resolvers)

v3.10.0

Compare Source

Features
prisma/prisma (@​prisma/client)

v6.2.1

Compare Source

Today we are releasing the 6.2.1 patch release to address an issue with some of the omitApi preview feature checks having been accidentally omitted when making the feature GA. Now it is fully functional without the preview feature flag.

Changes

v6.2.0

Compare Source

Today we're releasing Prisma ORM version 6.2.0 🎉

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

We have a number of new features in this version, including support for json and enum fields in SQLite, a new updateManyAndReturn function, support for ULID values, as well as the promotion of the omit feature from Preview to Generally Availability.

Highlights
Excluding fields via omit is now production-ready

Our number one requested feature is out of Preview and Generally Available. In 6.2.0, you no longer need to add omitApi to your list of Preview features:

generator client {
  provider        = "prisma-client-js"
- previewFeatures = ["omitApi"]
}

As a refresher: omit allows you to exclude certain fields from being returned in the results of your Prisma Client queries.

You can either do this locally, on a per-query level:

const result = await prisma.user.findMany({
  omit: {
    password: true,
  },
});

Or globally, to ensure a field is excluded from all queries of a certain model:

const prisma = new PrismaClient({
  omit: {
    user: {
      password: true
    }
  }
})

// The password field is excluded in all queries, including this one
const user = await prisma.user.findUnique({ where: { id: 1 } })

For more information on omit, be sure to check our documentation.

json and enum fields in SQLite

Previous to this version, you could not define json and enum fields in your Prisma schema when using SQLite. The respective GitHub issues have been among the most popular ones in our repo, so with our new approach to open-source governance, we finally got to work and implemented these.

Working with JSON and Enum fields works similarly to other database providers, here’s an example:

datasource db {
  provider = "sqlite"
  url      = "file:./dev.db"
}

model User {
  id   Int    @​id @​default(autoincrement())
  name String
  role Role  
  data Json
}

enum Role {
  Customer
  Admin 
}
Support for auto-generated ULID values

Similar to cuid2 support released in ORM version 6.0.0, we are now adding support for Universally Unique Lexicographically Sortable Identifiers (or short: ULIDs 😄) in version 6.2.0. A ULID value is a 26-character alphanumeric string, e.g. 01GZ0GZ3XARH8ZP44A7TQ2W4ZD.

With this new feature, you can now create records with auto-generated ULID values for String fields:

model User {
  id String @​id @​default(ulid())  
}
New batch function: updateManyAndReturn

updateMany allows you to update many records in your database, but it only returns the count of the affected rows, not the resulting rows themselves. With updateManyAndReturn you are now able to achieve this:

const users = await prisma.user.updateManyAndReturn({
  where: {
    email: {
      contains: 'prisma.io',
    }
  },
  data: {
    role: 'ADMIN'
  }
})

This call to updateManyAndReturn will now return the actual records that have been updated in the query:

[{
  id: 22,
  name: 'Alice',
  email: '[email protected]',
  profileViews: 0,
  role: 'ADMIN',
  coinflips: []
}, {
  id: 23,
  name: 'Bob',
  email: '[email protected]',
  profileViews: 0,
  role: 'ADMIN',
  coinflips: []
}]

Please note that like createManyAndReturn, updateManyAndReturn is only supported in PostgreSQL, CockroachDB, and SQLite.

Fixed runtime error in Node.js v23

While not officially supported, we understand that a lot of you like to be on the latest Node.js version — so we fixed an error that only occurred on Node.js 23. Happy coding ✌️

Prisma is hiring 🤝

Join us at Prisma to work on the most popular TypeScript ORM and other exciting products like the first serverless database built on unikernels!

We currently have two open roles in our Engineering team:

If these don’t fit, you can still check out our jobs page and send a general application.

vercel/next.js (eslint-config-next)

v15.1.4

Compare Source

lucide-icons/lucide (lucide-react)

v0.471.1: Hotfix Lucide React exports

Compare Source

What's Changed

v0.471.0: Dynamic Icon component Lucide React and new icons 0.471.0

Compare Source

New Dynamic Icon Component (lucide-react)

This is an easier approach than the previous dynamicIconImports we exported in the library. This one supports all environments.
We removed the examples in the docs of how you can make a dynamic icon yourself with a dedicated DynamicIcon component.
This one fetches the icon data itself and renders it instead of fetching the Icon component from the library.
This makes it more flexible with all the frontend frameworks and libraries that exist for React.

🚨
Not recommended for regular applications that work fine with the regular static icon components.
Using the dynamic icon component increases build time, separate bundles, and separate network requests for each icon.

How to use

DynamicIcon is useful for applications that want to show icons dynamically by icon name, for example when using a content management system where icon names are stored in a database.

const App = () => (
  <DynamicIcon name="camera" color="red" size={48} />
);
Possible Breaking changes

We have switched to the "exports" property in package.json. This can cause issues if you have directly imported scripts from the package. Please open an issue if we need to refine this export map.

New icons 🎨

v0.470.0: New icons 0.470.0

Compare Source

New icons 🎨
Modified Icons 🔨
vercel/next.js (next)

v15.1.4

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes
  • backport: force module format for virtual client-proxy (#​74608)
  • Fix prerender tags when notFound is called (#​74607)
  • Use provided waitUntil for pending revalidates (#​74604)
  • Feature: next/image: add support for images.qualities in next.config (#​74588)
  • Chore: docs: add missing search: '' on remotePatterns (#​74587)
  • Chore: docs: update version history of next/image (#​73923) (#​74570)
  • Chore: next/image: improve imgopt api bypass detection for unsupported images (#​74569)
Credits

Huge thanks to @​ and @​ for helping!

openai/openai-node (openai)

v4.78.1

Compare Source

Full Changelog: v4.78.0...v4.78.1

Bug Fixes

v4.78.0

Compare Source

Full Changelog: v4.77.4...v4.78.0

Features

v4.77.4

Compare Source

Full Changelog: v4.77.3...v4.77.4

Documentation
remarkjs/react-markdown (react-markdown)

v9.0.3

Compare Source

(same as 9.0.2 but now with d.ts files)

Full Changelog: remarkjs/react-markdown@9.0.2...9.0.3

v9.0.2

Compare Source

Types
Miscellaneous

Full Changelog: remarkjs/react-markdown@9.0.1...9.0.2

microsoft/TypeScript (typescript)

v5.7.3

Compare Source

pmndrs/zustand (zustand)

v5.0.3

Compare Source

ExtractState is a type util to extract state type from store type.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v5.0.2...v5.0.3

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added @clerk/nextjs all-non-major dependencies Pull requests that update a dependency file major minor patch labels Jan 11, 2025
@renovate renovate bot enabled auto-merge (squash) January 11, 2025 02:06
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jan 11, 2025 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   react@"^19" from the root project
npm error   peer react@">=16.8.0" from @floating-ui/[email protected]
npm error   node_modules/@floating-ui/react-dom
npm error     @floating-ui/react-dom@"^2.0.0" from @radix-ui/[email protected]
npm error     node_modules/@radix-ui/react-popper
npm error       @radix-ui/react-popper@"1.2.1" from @radix-ui/[email protected]
npm error       node_modules/@radix-ui/react-select
npm error         @radix-ui/react-select@"^2.1.4" from the root project
npm error   45 more (@radix-ui/react-arrow, @radix-ui/react-avatar, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^17.x || ^18.x" from [email protected]
npm error node_modules/typewriter-effect
npm error   typewriter-effect@"^2.21.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"^17.x || ^18.x" from [email protected]
npm error   node_modules/typewriter-effect
npm error     typewriter-effect@"^2.21.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-01-13T10_27_06_829Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-13T10_27_06_829Z-debug-0.log

@renovate renovate bot force-pushed the renovate/all-non-major branch from e02edcc to d2414be Compare January 12, 2025 12:49
@renovate renovate bot force-pushed the renovate/all-non-major branch from d2414be to e2db157 Compare January 13, 2025 04:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@RicardoGEsteves RicardoGEsteves

Labels
all-non-major @clerk/nextjs dependencies Pull requests that update a dependency file major minor patch
Projects
None yet
Milestone
No milestone
Development

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