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

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

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

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 3, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@commitlint/cli (source) ^19.5.0 -> ^19.8.0 age adoption passing confidence devDependencies minor
@commitlint/config-conventional (source) ^19.5.0 -> ^19.8.0 age adoption passing confidence devDependencies minor
@discordjs/builders (source) ^1.9.0 -> ^1.10.1 age adoption passing confidence dependencies patch
@prisma/client (source) ^6.0.0 -> ^6.5.0 age adoption passing confidence dependencies minor
@sapphire/iterator-utilities (source) ^2.0.0 -> ^2.0.1 age adoption passing confidence dependencies patch
@sapphire/result (source) ^2.6.6 -> ^2.7.2 age adoption passing confidence dependencies patch
@sapphire/time-utilities (source) ^1.7.12 -> ^1.7.14 age adoption passing confidence dependencies patch
@sapphire/utilities (source) ^3.17.0 -> ^3.18.2 age adoption passing confidence dependencies patch
@skyra/http-framework (source) ^2.1.0 -> ^2.2.0 age adoption passing confidence dependencies patch
@types/node (source) ^22.8.6 -> ^22.13.10 age adoption passing confidence devDependencies minor
docker/build-push-action v6.9.0 -> v6.15.0 age adoption passing confidence action minor
docker/login-action v3.3.0 -> v3.4.0 age adoption passing confidence action minor
docker/setup-buildx-action v3.7.1 -> v3.10.0 age adoption passing confidence action minor
eslint-config-prettier ^10.0.1 -> ^10.1.1 age adoption passing confidence devDependencies minor
eslint-plugin-prettier ^5.2.1 -> ^5.2.3 age adoption passing confidence devDependencies patch
lint-staged ^15.2.10 -> ^15.5.0 age adoption passing confidence devDependencies minor
node (source) 22.11.0 -> 22.14.0 age adoption passing confidence volta minor
prettier (source) ^3.3.3 -> ^3.5.3 age adoption passing confidence devDependencies minor
prisma (source) ^6.0.0 -> ^6.5.0 age adoption passing confidence devDependencies minor
tslib (source) ^2.8.0 -> ^2.8.1 age adoption passing confidence dependencies patch
yarn (source) 4.5.1 -> 4.7.0 age adoption passing confidence packageManager minor

Release Notes

conventional-changelog/commitlint (@​commitlint/cli)

v19.8.0

Compare Source

Performance Improvements
  • use node: prefix to bypass require.cache call for builtins (#​4302) (0cd8f41)

19.7.1 (2025-02-02)

Note: Version bump only for package @​commitlint/cli

19.6.1 (2024-12-15)

Note: Version bump only for package @​commitlint/cli

v19.7.1

Compare Source

Note: Version bump only for package @​commitlint/cli

conventional-changelog/commitlint (@​commitlint/config-conventional)

v19.8.0

Compare Source

Performance Improvements
  • use node: prefix to bypass require.cache call for builtins (#​4302) (0cd8f41)

19.7.1 (2025-02-02)

Note: Version bump only for package @​commitlint/config-conventional

v19.7.1

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

discordjs/discord.js (@​discordjs/builders)

v1.10.1

Compare Source

Bug Fixes

prisma/prisma (@​prisma/client)

v6.5.0

Compare Source

Today, we are excited to share the 6.5.0 stable release 🎉

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

Highlights

Databases can only be reset manually and explicitly

In previous versions, if Prisma ORM determined that a migrate command could not be applied cleanly to the underlying database, you would get a message like this one:

? We need to reset the "public" schema at "db.url.com:5432"
Do you want to continue? All data will be lost. (y/N)

While "no" was the default, we've determined that having this prompt in the first place was a mistake. In this version we're removing the prompt entirely and instead exiting with an appropriate error message.

To get the previous behavior, you will need to run prisma migrate reset directly.

Support for prisma.config.ts in Prisma Studio

We've expanded support for our prisma.config.ts file to include Prisma Studio!

To use the new config file, including the ability to connect to driver adapter enabled databases with Prisma Studio, add a studio block to your prisma.config.ts file:

import path from 'node:path'
import type { PrismaConfig } from 'prisma'
import { PrismaLibSQL } from '@​prisma/adapter-libsql'
import { createClient } from '@​libsql/client'

export default {
  earlyAccess: true,
  schema: {
    kind: 'single',
    filePath: './prisma/schema.prisma',
  },
  studio: {
    adapter: async (env: unknown) => {
      const connectionString = `file:./dev.db'
      const libsql = createClient({
        url: connectionString,
      })
      return new PrismaLibSQL(libsql)
    },
  },
} satisfies PrismaConfig

Notice how this looks a little different from last release! Instead of an @prisma/config package there’s now two different options:

  1. Using the defineConfig helper exported by prisma/config.
  2. Using the PrismaConfig utility type exported by Prisma.

All the relevant info for the prisma.config.ts file, including these new ways of defining your config, can be found in our docs.

Allow for chaining $on and $extends.

In previous versions of Prisma ORM, the return type of the $on client method was void. This did not allow for chaining $on() and $extends() calls, as $on is not available on extended clients.

In this version we've resolved this issue and $on will now return the modified Prisma Client.

Community fixes

We have a number of community-submitted fixes that improve Prisma ORM:

Prisma is hiring

Join us at Prisma and work on our TypeScript ORM (now faster than ever) and our Cloud products like Prisma Postgres (now in GA!)

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.

Enterprise support

Prisma offers an enterprise support plan for Prisma ORM. Get direct help from our team and a joint slack channel! With Prisma ORM 7 on the horizon this is a great time to upgrade your support today.

Credits

v6.4.1

Compare Source

Today, we are issuing the 6.4.1 patch release. It fixes a few issues with the NPS survey and makes it respect the --no-hints CLI flag.

Fixes

Prisma CLI

v6.4.0

Compare Source

Today, we are excited to share the 6.4.0 stable release 🎉

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

Highlights

TypeScript-based configuration with prisma.config.ts (Early Access)

In this release, we're introducing an Early Access version of a TypeScript-based configuration file for Prisma ORM: prisma.config.ts.

This file will serve as a central configuration point for Prisma ORM:

import path from 'node:path'

export default {
  earlyAccess: true, // required while in Early Access

  schema: {
    kind: 'single', // use 'multi' if you're using the `prismaSchemaFolder` preview feature
    filePath: path.join('custom', 'prisma', 'schema.prisma')
  }
  
})

With this file you are able to run any arbitrary code needed to get values required by Prisma ORM, such as database URLs from a secret store or fine-grained control of settings. It needs to live in the current working directory from where you're executing Prisma CLI commands (typically, the root of your project).

Note: If you're using prisma.config.ts, the Prisma CLI will not load environment variables from .env files. If you want to use a .env file with prisma.config.ts, you'll need to load the environment variables manually using the dotenv package (see here).

Learn more about the new prisma.config.ts file in the docs.

Case-insensitive mode in JSON filters

You can now do case-insensitive filtering on JSON data.

Just use the new mode option when filtering using string_contains, string_starts_with or string_ends_with in a JSON object and set it to "insensitive":

await prisma.user.findMany({
  where: {
    pets: {
      path: ['favorites', 'catBreed'],
      string_contains: 'Van',
      mode: "insensitive",
    },
  },
});

The above query returns all users where the favorites.catBreed value contains "Van" or "van".

Thanks to @​lubosmato who implemented this feature 🎉

Improved CockroachDB migration speed

In this release we found some inefficiencies in our migration engine that was impacting CockroachDB migrations. In 6.4.0, CockroachDB migrations should be significantly faster.

Calling all devs: Give us your feedback!

Prisma ORM's community keeps us going. To make sure that we're focused on what the community needs, we would like to get your feedback via our online feedback form.

Credits

Huge thanks to @​lubosmato, @​notomo, @​Mayureshd-18, @​mydea, @​omar-dulaimi and @​Hazmi35 for helping out with this release!

v6.3.1

Compare Source

This patch releases introduces improvements to the prisma init output when invoked to with the --db option.

Run npx prisma@latest init --db to get an instant Prisma Postgres database.

v6.3.0

Compare Source

Today, we are excited to share the 6.3.0 stable release 🎉

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

Highlights

A brand new Prisma Studio

In this release we've included several great improvements to Prisma Studio's developer experience. You can learn all about the changes we've made in our release blog post, but here's a short list:

Prisma Studio is back in the Console

Fans of Prisma Data Browser rejoice! The new Prisma Studio is now in the Prisma Console and is available for all PostgreSQL and MySQL databases.

A new model viewer

Previously, switching from model to model in Prisma Studio would require backing all the way out to the model view, then digging in again. With our new UI, it's easy to switch from model to model while keeping your place.

image

A new editing experience

If you're trying to edit a given field in a model, Prisma Studio made it quite easy. However, if you're trying to edit every field in a given row, it could get quite annoying to keep scrolling left to right. Our new edit sidebar resolves that with the ability to edit all fields for a given row at once.

image

Clean up at the click of a button

When editing a number of models, it can get difficult to get back to a clean slate. In the new Prisma Studio, we've added a "Close all" button that puts you back to a fresh start.

image

Add limit to updateMany() and deleteMany()

Previously, limit has not existed as a valid option in top level updateMany() and deleteMany() queries. In 6.3.0 limit is now available in these queries, bringing their features more in line with other query types.

You can use limit like the following:

await prisma.user.deleteMany({
  where: { column: 'value' },
  limit: 100,
});

This will limit the number of deleted users to 100 at maximum.

Sort generator fields deterministically

In previous version of Prisma ORM, the fields inside of a generator block in your Prisma Schema were not deterministically sorted. This could lead to cases where prisma db pull could lead to re-ordering of fields.

In 6.3.0, the sorting of fields in this block is now deterministic. You may see re-ordering on the first prisma db pull after you upgrade, but it will remain consistent afterwards.

Replace NOT IN with NOT EXISTS for PostgreSQL relation filters

In previous versions of Prisma ORM, when using the none or some relation filters, the SQL queries generated used NOT IN. In many cases this lead to performance issues as the size of the related table grew. In 6.3.0, we’ve replaced these usages of IN with EXISTS in order to improve query performance.

A special thank you

We'd like to extend our heartfelt thanks to @​loren and his team for the collaboration and trust in our enterprise support plan. Working closely with them allowed us to address important issues like #​19249 and #​17303. Their insights and partnership have been invaluable in improving our product.

If your team could benefit from dedicated support and tailored solutions, learn more about our enterprise support plan.

Fixes and improvements

Prisma Client
Prisma

Credits

Huge thanks to @​WhyAsh5114 for their contributions to this release!

sapphiredev/utilities (@​sapphire/utilities)

v3.18.2

Compare Source

🐛 Bug Fixes

docker/build-push-action (docker/build-push-action)

v6.15.0

Compare Source

Full Changelog: docker/build-push-action@v6.14.0...v6.15.0

v6.14.0

Compare Source

Full Changelog: docker/build-push-action@v6.13.0...v6.14.0

v6.13.0

Compare Source

Full Changelog: docker/build-push-action@v6.12.0...v6.13.0

v6.12.0

Compare Source

Full Changelog: docker/build-push-action@v6.11.0...v6.12.0

v6.11.0

Compare Source

Full Changelog: docker/build-push-action@v6.10.0...v6.11.0

v6.10.0

Compare Source

Full Changelog: docker/build-push-action@v6.9.0...v6.10.0

docker/login-action (docker/login-action)

v3.4.0

Compare Source

docker/setup-buildx-action (docker/setup-buildx-action)

v3.10.0

Compare Source

Full Changelog: docker/setup-buildx-action@v3.9.0...v3.10.0

v3.9.0

Compare Source

Full Changelog: docker/setup-buildx-action@v3.8.0...v3.9.0

v3.8.0

Compare Source

Full Changelog: docker/setup-buildx-action@v3.7.1...v3.8.0

prettier/eslint-config-prettier (eslint-config-prettier)

v10.1.1

Compare Source

Patch Changes

  • #​309 eb56a5e Thanks @​JounQin! - fix: separate the /flat entry for compatibility

    For flat config users, the previous "eslint-config-prettier" entry still works, but "eslint-config-prettier/flat" adds a new name property for config-inspector, we just can't add it for the default entry for compatibility.

    See also #​308

    // before
import eslintConfigPrettier from "eslint-config-prettier";

// after
import eslintConfigPrettier from "eslint-config-prettier/flat";

v10.1.0

Compare Source

Minor Changes

v10.0.3

Compare Source

Patch Changes

v10.0.2

Compare Source

Patch Changes
lint-staged/lint-staged (lint-staged)

v15.5.0

Compare Source

Minor Changes
  • #​1526 630af5f Thanks @​iiroj! - Lint-staged no longer resets to the original state when preventing an empty git commit. This happens when your configured tasks reset all the staged changes, typically when trying to commit formatting changes which conflict with your linter setup like ESLint or Prettier.
Example with Prettier

By default Prettier prefers double quotes.

Previously
  1. Stage file.js with only double quotes " changed to '
  2. Run git commit -am "I don't like double quotes"
  3. Lint-staged runs prettier --write file.js, converting all the ' back to "
  4. Because there are now no changes, lint-staged fails, cancels the commit, and resets back to the original state
  5. Commit was not done, original state is restored and single quotes ' are staged
Now
  1. Stage file.js with only double-quotes " changed to '
  2. Run git commit -am "I don't like double quotes"
  3. Lint-staged runs prettier --write file.js, converting all the ' back to "
  4. Because there are now no changes, lint-staged fails and cancels the commit
  5. Commit was not done, and there are no staged changes

v15.4.3

Compare Source

Patch Changes
  • #​1512 cbfed1d Thanks @​tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.

v15.4.2

Compare Source

Patch Changes
  • #​1509 8827ebf Thanks @​iiroj! - Change lint-staged's dependencies to use caret (^) ranges instead of tilde (~). This makes it easier for package managers to perform dependency management when minor-level updates are also permitted instead of just patch-level.
nodejs/node (node)

v22.14.0: 2025-02-11, Version 22.14.0 'Jod' (LTS), @​aduh95

Compare Source

Notable Changes
  • [82a9000e9e] - crypto: update root certificates to NSS 3.107 (Node.js GitHub Bot) #​56566
  • [b7fe54fc88] - (SEMVER-MINOR) fs: allow exclude option in globs to accept glob patterns (Daeyeon Jeong) #​56489
  • [3ac92ef607] - (SEMVER-MINOR) lib: add typescript support to STDIN eval (Marco Ippolito) #​56359
  • [1614e8e7bc] - (SEMVER-MINOR) module: add ERR_UNSUPPORTED_TYPESCRIPT_SYNTAX (Marco Ippolito) #​56610
  • [6d6cffa9cc] - (SEMVER-MINOR) module: add findPackageJSON util (Jacob Smith) #​55412
  • [d35333ae18] - (SEMVER-MINOR) process: add process.ref() and process.unref() methods (James M Snell) #​56400
  • [07ff3ddcb5] - (SEMVER-MINOR) sqlite: support TypedArray and DataView in StatementSync (Alex Yang) #​56385
  • [94d3fe1b62] - (SEMVER-MINOR) src: add --disable-sigusr1 to prevent signal i/o thread (Rafael Gonzaga) #​56441
  • [5afffb4415] - (SEMVER-MINOR) src,worker: add isInternalWorker (Carlos Espa) #​56469
  • [697a851fb3] - (SEMVER-MINOR) test_runner: add TestContext.prototype.waitFor() (Colin Ihrig) #​56595
  • [047537b48c] - (SEMVER-MINOR) test_runner: add t.assert.fileSnapshot() (Colin Ihrig) #​56459
  • [926cf84e95] - (SEMVER-MINOR) test_runner: add assert.register() API (Colin Ihrig) #​56434
  • [c658a8afdf] - (SEMVER-MINOR) worker: add eval ts input (Marco Ippolito) #​56394
Commits

Configuration

📅 Schedule: Branch creation - "before 12pm on Sunday" (UTC), 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies label Nov 3, 2024
@renovate renovate bot enabled auto-merge (rebase) November 3, 2024 01:48
renovate-approve[bot]
renovate-approve bot previously approved these changes Nov 3, 2024
View reviewed changes
renovate-approve-2[bot]
renovate-approve-2 bot previously approved these changes Nov 3, 2024
View reviewed changes
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4107e80 to 16d4fe3 Compare November 3, 2024 07:49
renovate-approve[bot]
renovate-approve bot previously approved these changes Nov 3, 2024
View reviewed changes
renovate-approve-2[bot]
renovate-approve-2 bot previously approved these changes Nov 3, 2024
View reviewed changes
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 16d4fe3 to 9d19217 Compare November 3, 2024 11:43
renovate-approve[bot]
renovate-approve bot previously approved these changes Nov 3, 2024
View reviewed changes
renovate-approve-2[bot]
renovate-approve-2 bot previously approved these changes Nov 3, 2024
View reviewed changes
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9d19217 to a741280 Compare November 4, 2024 16:34
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a741280 to 59ebc0b Compare November 5, 2024 03:28
renovate-approve-2[bot]
renovate-approve-2 bot previously approved these changes Nov 5, 2024
View reviewed changes
renovate-approve[bot]
renovate-approve bot previously approved these changes Nov 5, 2024
View reviewed changes
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 59ebc0b to fb3a90f Compare November 5, 2024 16:28
renovate-approve-2[bot]
renovate-approve-2 bot previously approved these changes Nov 5, 2024
View reviewed changes
renovate-approve[bot]
renovate-approve bot previously approved these changes Nov 5, 2024
View reviewed changes
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from fb3a90f to 7398afb Compare November 9, 2024 12:16
renovate-approve[bot]
renovate-approve bot previously approved these changes Nov 9, 2024
View reviewed changes
renovate-approve-2[bot]
renovate-approve-2 bot previously approved these changes Nov 9, 2024
View reviewed changes
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 4e4f12d to b2597af Compare February 9, 2025 14:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 2b1a510 to 44a3c96 Compare February 14, 2025 00:13
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 0800aff to 8d43920 Compare February 22, 2025 06:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from 747e621 to ec9f0e0 Compare March 3, 2025 22:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from e5f48cd to 90b41e4 Compare March 12, 2025 19:20
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 90b41e4 to 2559f02 Compare March 14, 2025 10:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@renovate-approve renovate-approve[bot] renovate-approve[bot] left review comments

@renovate-approve-2 renovate-approve-2[bot] renovate-approve-2[bot] left review comments

@favna favna Awaiting requested review from favna favna is a code owner

At least 1 approving review is required to merge this pull request.

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

Successfully merging this pull request may close these issues.
0 participants