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

renovate · 2024-11-27T17:59:14Z

This PR contains the following updates:

Package	Change	Type	Update
@discordjs/builders (source)	`^1.11.3` -> `^1.13.0`	dependencies	minor
@prisma/client (source)	`^6.16.2` -> `^6.19.0`	dependencies	minor
@sapphire/framework (source)	`^5.3.6` -> `^5.4.0`	dependencies	minor
@sapphire/result (source)	`^2.7.2` -> `^2.8.0`	dependencies	minor
@tsconfig/node20 (source)	`^20.1.6` -> `^20.1.8`	devDependencies	patch
@types/node (source)	`^20.19.17` -> `^20.19.25`	devDependencies	patch
@typescript-eslint/eslint-plugin (source)	`^8.44.0` -> `^8.47.0`	devDependencies	minor
@typescript-eslint/parser (source)	`^8.44.0` -> `^8.47.0`	devDependencies	minor
discord-api-types (source)	`^0.37.120` -> `^0.38.34`	dependencies	minor
discord.js (source)	`^14.22.1` -> `^14.25.0`	dependencies	minor
eslint (source)	`^9.36.0` -> `^9.39.1`	devDependencies	minor
ghcr.io/hazmi35/node	`22-alpine` -> `22.21.1-alpine`	final	minor
ghcr.io/hazmi35/node	`22-dev-alpine` -> `22.21.1-dev-alpine`	stage	minor
node (source)	`>=22.17.0` -> `>=22.21.1`	engines	minor
node (source)	`22` -> `22.21.1`		minor
npm (source)	`>=7.0.0` -> `>=7.24.2`	engines	minor
pnpm (source)	`10.17.0+sha512.fce8a3dd29a4ed2ec566fb53efbb04d8c44a0f05bc6f24a73046910fb9c3ce7afa35a0980500668fa3573345bd644644fa98338fa168235c80f4aa17aa17fbef` -> `10.22.0`	packageManager	minor
prisma (source)	`^6.16.2` -> `^6.19.0`	devDependencies	minor
shoukaku	`^4.1.1` -> `^4.2.0`	dependencies	minor
typescript (source)	`^5.9.2` -> `^5.9.3`	devDependencies	patch

Release Notes

discordjs/discord.js (@discordjs/builders)

`v1.13.0`

Compare Source

Features

V1 builders file uploads support (#11196) (1417c49)

Testing

Fix type error (f780c6a)

`v1.12.2`

Compare Source

Bug Fixes

Assertions: Literal default values (43362c9)

`v1.12.1`

Compare Source

Bug Fixes

builders: Text display component support for modals (#11155) (99b8436)

`v1.12.0`

Compare Source

Features

builders: Modal select menus in builders v1 (#11138) (ac683b9)

prisma/prisma (@prisma/client)

`v6.19.0`

Compare Source

`v6.18.0`

Compare Source

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

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

Prisma ORM

Prisma ORM is the most popular ORM in the TypeScript ecosystem. Today’s release brings a bunch of new bug fixes and overall improvements:

prisma init now creates a prisma.config.ts automatically

When creating a new project with 6.18.0, prisma init will now create a prisma.config.ts file automatically. This prepares new applications for the future of Prisma 7. Some fields that have been historically set in the schema.prisma file are now able to be set in the prisma.config.ts, and we encourage people to migrate over to the new structure before the release of version 7, where this file will become a requirement.

Support for defining your datasource in prisma.config.ts

If you’re adopting the new prisma.config.ts setup in your projects, version 6.18.0 brings the ability to set your datasource directly in your config file. Once this is in your config file, any datasource set in your schema.prisma will be ignored. To set the datasource, we also must include the new engine key which we can set to "classic" , which will be required for Prisma v7

import { defineConfig, env } from "prisma/config";
export default defineConfig({
    // The Rust-compiled schema engine 
    engine: "classic",
    datasource: {
        url: env('DATABASE_URL'),
    }
});

#28291 Support multiple Prisma instances with different providers
#28305 Add env helper function
#28266 Add support for js or classic as engine types in prisma.config
#28139 Map Bytes to Uint8Array depending on Typescript version

Preparing for Prisma v7

While it has been mentioned a few times already, many of the changes in this release are here to prepare folks for the upcoming release of Prisma v7. It’s worth repeating that these changes and the migration to prisma.config.ts will be required for Prisma v7, so we’re releasing this as opt-in features for developers. But come Prisma v7, they will be the new way of configuring your project.

Prisma Postgres

Prisma Postgres is our fully managed Postgres service designed with the same philosophy of great DX that has guided Prisma for close to a decade. With this release we are introducing the following improvements:

Database Metric in Console

Inside of your database console, you can now view metrics on your database usage and interactions. You can get insights into the follow:

Total egress
Average response size
Average query duration

In addition, you can also get insights into how to improve your query caching and gain better performance.

Open roles at Prisma

Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our Careers page and find the role that’s right for you.

Enterprise support

Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.

With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.

`v6.17.1`

Compare Source

Today, we are issuing a patch release to address a regression in v6.17.0 that affected diffing of unsupported types, leading to unnecessary or incorrect changes when creating new migrations or running db pull. This update is recommended for all users who have any fields marked as Unsupported in their schema files.

Changes

prisma/prisma-engines#5633

`v6.17.0`

Compare Source

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

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

Prisma ORM

Prisma ORM is the most popular ORM in the TypeScript ecosystem. Today's release brings a number of bug fixes and improvements to Prisma ORM.

Bug fixes and improvements

Added support for Entra ID (ActiveDirectory) authentication parameters for the MS SQL Server driver adapter. For example, you can use the config object to configure DefaultAzureCredential:

import { PrismaMssql } from '@&#8203;prisma/adapter-mssql'
import { PrismaClient } from '@&#8203;prisma/client'

const config = {
  server: 'localhost',
  port: 1433,
  database: 'mydb',
  authentication: {
    type: 'azure-active-directory-default',
  },
  options: {
    encrypt: true,
  },
}

const adapter = new PrismaMssql(config)
const prisma = new PrismaClient({ adapter })

Learn more in this PR.

Relaxed the support package range for @opentelemetry/instrumentation to be compatible with ">=0.52.0 <1". Learn more in this PR.
Added Codex CLI detection, ensuring dangerous Prisma operations are not executed by Codex without explicit user consent. Learn more in this PR.
Fixed JSON column handling when using a MariaDB database. Learn more in this PR.
Restored the original behaviour of group-by aggregations where they would refer to columns with explicit table names which fixes a regression that would result in ambiguous column errors. Learn more in this PR.

Prisma Postgres

Prisma Postgres is our fully managed Postgres service designed with the same philosophy of great DX that has guided Prisma for close to a decade. With this release we are introducing the following improvements:

New usage workspace metrics available in your Console Dashboard

The Dashboard in your Prisma Console account now displays new metrics about your Prisma Postgres usage:

Key metrics
- Estimated upcoming invoice
- Total storage used
- Total DBs
Overall usage
- Cumulative operations
- Operations per day

Using Prisma Postgres with any tool is ready for production

Previously, the only way to connect to Prisma Postgres was using Prisma ORM. That combination is great because it gives you connection pooling, global caching and overall an amazing DX.

That being said, we understand that preferences vary and some developers prefer to use plain SQL or lower-level query builders in their applications. As of this release, these ways for connecting to Prisma Postgres are now officially generally available and can be used in your production apps!

You can connect using Drizzle, Kysely, TypeORM, psql, or any other Postgres-compatible library, database migration tools like Atlas or interfaces like DBeaver, Postico, and more.

📚 Learn more in the docs.

Enterprise support

Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.

With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.

`v6.16.3`

Compare Source

Today, we are issuing a 6.16.3 patch release focused on bug fixes.

🛠 Fixes

Prisma Client (prisma-client generator): fixed missing JSON null type definitions (JsonNull, DbNull, AnyNull) in the browser.ts entrypoint. (#28186)
Prisma Migrate: don't add the default schema (namespace) to the generated migrations unless it was specified explicitly in the schema file. This restores the pre-6.13.0 behaviour that was inadvertently changed with enabling multi-schema support by default. Users who rely on database schemas for multi-tenancy can now again use the same migration files for all of their schemas. (prisma/prisma-engines#5614)
Prisma Client: enabled negative take with findFirst again. (prisma/prisma-engines#5616 — contributed by @jay-l-e-e)
Prisma Accelerate: aligned the behaviour of the new Rust-free client with Query Engine to handle self-signed certificates consistently and ensure backward compatibility. (#28134)
@prisma/adapter-mariadb: fixed error event listeners leak. (#28177 — contributed by @Tiaansu)

⚠️ Known Limitation: JSON null types in browser builds

The fix introduces the missing types, but the singleton instances differ between the client and browser entrypoints of the generated client. This means that values like Prisma.JsonNull imported from browser cannot yet be assigned to fields expected from the client entrypoint, and vice versa. This results in confusing TypeScript errors if you mix them. A follow-up improvement is planned to unify these utility types across entrypoints.

sapphiredev/framework (@sapphire/framework)

`v5.4.0`

Compare Source

🐛 Bug Fixes

deps: Update all non-major dependencies (9e5943d) (#857 by @renovate[bot])
deps: Update all non-major dependencies (f458712) (#853 by @renovate[bot])

🚀 Features

Update sapphire dependencies (d3aad6a)

`v5.3.7`

Compare Source

🐛 Bug Fixes

Update result and lexure (c9d86ce)
Update code in ClientPermissions and command channel types to match latest discordjs changes (43d7e4a) (#849 by @favna)
deps: Update all non-major dependencies (e9190b8)

sapphiredev/utilities (@sapphire/result)

`v2.8.0`

Compare Source

🚀 Features

Add safeTry to emulate rust ? operator (6abc552) (#917 by @feelsantiago)
Improve result and options types (f3515ea) (#918 by @feelsantiago)

`v2.7.3`

Compare Source

🐛 Bug Fixes

deps: Update all non-major dependencies (636a5ee) (#897 by @renovate[bot])
deps: Update all non-major dependencies (4bc5591) (#879 by @renovate[bot])
deps: Update all non-major dependencies (bc2f01c) (#869 by @renovate[bot])
Result value types losing types after mapping (44fccf0) (#833 by @OfficialSirH)

📝 Documentation

Update documentation link for usage examples (e79994f) (#883 by @favna)

tsconfig/bases (@tsconfig/node20)

`v20.1.8`

Compare Source

`v20.1.7`

Compare Source

typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)

`v8.47.0`

Compare Source

🚀 Features

eslint-plugin: [no-unused-private-class-members] new extension rule (#10913)

❤️ Thank You

Brad Zacher @bradzacher

You can read about our versioning strategy and releases on our website.

`v8.46.4`

Compare Source

🩹 Fixes

parser: error when both projectService and project are set (#11333)
eslint-plugin: handle override modifier in promise-function-async fixer (#11730)
eslint-plugin: [no-deprecated] fix double-report on computed literal identifiers (#11006, #10958)

❤️ Thank You

Evgeny Stepanovych @undsoft
Kentaro Suzuki @sushichan044
Maria Solano @MariaSolOs

You can read about our versioning strategy and releases on our website.

`v8.46.3`

Compare Source

🩹 Fixes

eslint-plugin: [no-duplicate-enum-values] support signed numbers (#11722, #11723)
eslint-plugin: [no-misused-promises] expand union type to retrieve target property (#11706)

❤️ Thank You

Evgeny Stepanovych @undsoft
tao

You can read about our versioning strategy and releases on our website.

`v8.46.2`

Compare Source

🩹 Fixes

eslint-plugin: [prefer-optional-chain] skip optional chaining when it could change the result (#11702)

❤️ Thank You

mdm317

You can read about our versioning strategy and releases on our website.

`v8.46.1`

Compare Source

🩹 Fixes

eslint-plugin: [no-misused-promises] special-case .finally not to report when a promise returning function is provided as an argument (#11667)
eslint-plugin: [prefer-optional-chain] include mixed "nullish comparison style" chains in checks (#11533)

❤️ Thank You

mdm317
Ronen Amiel

You can read about our versioning strategy and releases on our website.

`v8.46.0`

Compare Source

🚀 Features

eslint-plugin: [no-unsafe-member-access] add allowOptionalChaining option (#11659)
rule-schema-to-typescript-types: clean up and make public (#11633)

🩹 Fixes

eslint-plugin: [prefer-readonly-parameter-types] ignore tagged primitives (#11660)
typescript-estree: forbid abstract method and accessor to have implementation (#11657)
eslint-plugin: removed error type previously deprecated (#11674)
eslint-plugin: [no-deprecated] ignore deprecated export imports (#11603)
eslint-plugin: [unbound-method] improve wording around this: void and binding (#11634)
rule-tester: deprecate TestCaseError#type and LintMessage#nodeType (#11628)
eslint-plugin: [no-floating-promises] remove excess parentheses in suggestions (#11487)

❤️ Thank You

fisker Cheung @fisker
Josh Goldberg ✨
Kirk Waiblinger @kirkwaiblinger
Mark de Dios @peanutenthusiast
Richard Torres @richardtorres314
Victor Genaev @mainframev

You can read about our versioning strategy and releases on our website.

`v8.45.0`

Compare Source

🚀 Features

eslint-plugin: expose rule name via RuleModule interface (#11616)

🩹 Fixes

eslint-plugin: [prefer-nullish-coalescing] ignoreBooleanCoercion should not apply to top-level ternary expressions (#11614)
eslint-plugin: [no-base-to-string] check if superclass is ignored (#11617)

❤️ Thank You

mdm317
Moses Odutusin @thebolarin
Yukihiro Hasegawa @y-hsgw

You can read about our versioning strategy and releases on our website.

`v8.44.1`

Compare Source

🩹 Fixes

eslint-plugin: [await-thenable] should not report passing values to promise aggregators which may be a promise in an array literal (#11611)
eslint-plugin: [no-unsafe-enum-comparison] support unions of literals (#11599)
eslint-plugin: [no-base-to-string] make ignoredTypeNames match type names without generics (#11597)

❤️ Thank You

Kirk Waiblinger @kirkwaiblinger
mdm317
Ronen Amiel

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@typescript-eslint/parser)