fix(deps): update all non-major dependencies#4
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
Conversation
|
337f018 to
7dafffd
Compare
941c6c4 to
83a7017
Compare
83a7017 to
0c13bfd
Compare
0c13bfd to
5004cc0
Compare
5004cc0 to
0127beb
Compare
0127beb to
be942b4
Compare
d2ba5ac to
eaaf688
Compare
eaaf688 to
3d10fc1
Compare
63d4996 to
3d35f9e
Compare
3df97d8 to
b7d645f
Compare
b7d645f to
491db18
Compare
491db18 to
d93ae32
Compare
beefe32 to
73c16b0
Compare
73c16b0 to
5ac1c20
Compare
5ac1c20 to
10f9cbf
Compare
10f9cbf to
99e8660
Compare
0aa4506 to
054bb86
Compare
054bb86 to
da8135b
Compare
da8135b to
62ef06f
Compare
62ef06f to
4d7fb0f
Compare
d8c3aac to
457dbe4
Compare
901bb03 to
a3e6efb
Compare
d440d03 to
30d5681
Compare
3dc22a0 to
fdb37b9
Compare
47d533c to
92903a8
Compare
e9cb626 to
1530f7e
Compare
ce9afbc to
b7dd0db
Compare
37f4bc5 to
9f6a1ed
Compare
f747ca9 to
8dc307d
Compare
8dc307d to
0c1f7a8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^1.11.3→^1.14.1^6.16.2→^6.19.3^5.3.6→^5.5.0^2.7.2→^2.8.0^20.1.6→^20.1.9^20.19.17→^20.19.39^8.44.0→^8.59.2^8.44.0→^8.59.2^0.37.120→^0.38.47^14.22.1→^14.26.4^9.36.0→^9.39.422-alpine→22.22.2-alpine22-dev-alpine→22.22.2-dev-alpine>=22.17.0→>=22.22.222→22.22.2>=7.0.0→>=7.24.210.17.0+sha512.fce8a3dd29a4ed2ec566fb53efbb04d8c44a0f05bc6f24a73046910fb9c3ce7afa35a0980500668fa3573345bd644644fa98338fa168235c80f4aa17aa17fbef→10.33.3^6.16.2→^6.19.3^4.1.1→^4.3.0^5.9.2→^5.9.3Release Notes
discordjs/discord.js (@discordjs/builders)
v1.14.1Compare Source
Bug Fixes
v1.14.0Compare Source
Documentation
Features
v1.13.1Compare Source
Bug Fixes
Documentation
v1.13.0Compare Source
Features
Testing
v1.12.2Compare Source
Bug Fixes
v1.12.1Compare Source
Bug Fixes
v1.12.0Compare Source
Features
prisma/prisma (@prisma/client)
v6.19.3Compare Source
Today, we are issuing a 6.19.3 patch release in the Prisma 6 release line. It updates the
effectdependency to resolve a security vulnerability.Changes:
#29416
v6.19.2Compare Source
Today, we are issuing a 6.19.2 patch release in the Prisma 6 release line. It fixes an issue with Prisma Accelerate support in some edge runtime configurations when the
@prisma/client/edgeentrypoint is not being used.Changes:
v6.19.1Compare Source
v6.19.0Compare Source
v6.18.0Compare Source
Today, we are excited to share the
6.18.0stable 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 initnow creates aprisma.config.tsautomaticallyWhen creating a new project with 6.18.0,
prisma initwill now create aprisma.config.tsfile automatically. This prepares new applications for the future of Prisma 7. Some fields that have been historically set in theschema.prismafile are now able to be set in theprisma.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.datasourceinprisma.config.tsIf you’re adopting the new
prisma.config.tssetup 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 yourschema.prismawill be ignored. To set the datasource, we also must include the newenginekey which we can set to"classic", which will be required for Prisma v7envhelper functionjsorclassicas engine types inprisma.configBytestoUint8Arraydepending on Typescript versionPreparing 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.tswill 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:
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.1Compare 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 asUnsupportedin their schema files.Changes
v6.17.0Compare Source
Today, we are excited to share the
6.17.0stable 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
configobject to configure DefaultAzureCredential:@opentelemetry/instrumentationto be compatible with">=0.52.0 <1". 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:
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.3Compare Source
Today, we are issuing a 6.16.3 patch release focused on bug fixes.
🛠 Fixes
Prisma Client (
prisma-clientgenerator): fixed missing JSON null type definitions (JsonNull,DbNull,AnyNull) in thebrowser.tsentrypoint. (#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
takewithfindFirstagain. (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)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.JsonNullimported 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.5.0Compare Source
🚀 Features
v5.4.0Compare Source
🐛 Bug Fixes
🚀 Features
v5.3.7Compare Source
🐛 Bug Fixes
sapphiredev/utilities (@sapphire/result)
v2.8.0Compare Source
🚀 Features
v2.7.3Compare Source
🐛 Bug Fixes
📝 Documentation
tsconfig/bases (@tsconfig/node20)
v20.1.9Compare Source
v20.1.8Compare Source
v20.1.7Compare Source
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.59.2Compare Source
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.59.1Compare Source
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.59.0Compare Source
🚀 Features
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.58.2Compare Source
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.58.1Compare Source
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.58.0Compare Source
🚀 Features
🩹 Fixes
no-unnecessary-type-arguments(#12163)❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.57.2Compare Source
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.57.1Compare Source
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.57.0Compare Source
🚀 Features
🩹 Fixes
TypeOrValueSpecifierto prefer-promise-reject-errors (#12094)cookedwill benull(#11355)❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.56.1Compare Source
This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.56.0Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.55.0Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.54.0Compare Source
🚀 Features
🩹 Fixes
def.name(#11982)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.53.1Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.53.0Compare Source
🚀 Features
🩹 Fixes
errortyped" with more helpful description (#11704)extendsandimplementsin interface declaration (#11935)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.52.0Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.51.0Compare Source
🚀 Features
🩹 Fixes
no-useless-default-assignment(#11845)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.50.1Compare Source
🩹 Fixes
this(#11813)❤️ Thank You
You can read about our
Configuration
📅 Schedule: (in timezone Asia/Jakarta)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.