fix(deps): 🐛 🔗 update all dependencies #114

renovate · 2023-12-01T01:04:15Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@aws-sdk/client-cloudformation (source)	`3.450.0` -> `3.461.0`
@aws-sdk/client-lambda (source)	`3.450.0` -> `3.461.0`
@commitlint/cli (source)	`18.4.1` -> `18.4.3`
@commitlint/config-conventional (source)	`18.4.0` -> `18.4.3`
@commitlint/types (source)	`18.4.0` -> `18.4.3`
@graphql-tools/merge	`9.0.0` -> `9.0.1`
@graphql-tools/utils	`10.0.8` -> `10.0.11`
@prisma/client (source)	`5.5.2` -> `5.6.0`
@smithy/util-waiter (source)	`2.0.12` -> `2.0.14`
@types/aws-lambda (source)	`8.10.126` -> `8.10.129`
@typescript-eslint/eslint-plugin	`6.11.0` -> `6.13.1`
@typescript-eslint/parser	`6.11.0` -> `6.13.1`
aws-cdk	`2.106.1` -> `2.111.0`
aws-cdk-lib	`2.106.1` -> `2.111.0`
esbuild	`0.19.5` -> `0.19.8`
eslint (source)	`8.53.0` -> `8.54.0`
pnpm (source)	`8.10.4` -> `8.11.0`
prettier-plugin-sql (source)	`0.16.0` -> `0.17.0`
prisma (source)	`5.5.2` -> `5.6.0`
tsup (source)	`7.2.0` -> `8.0.1`
tsx	`4.1.1` -> `4.6.0`
typescript (source)	`5.2.2` -> `5.3.2`

Release Notes

aws/aws-sdk-js-v3 (@aws-sdk/client-cloudformation)

`v3.461.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-cloudformation

`v3.460.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-cloudformation

`v3.458.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-cloudformation

`v3.454.0`

Compare Source

Features

client-cloudformation: This release adds a new flag ImportExistingResources to CreateChangeSet. Specify this parameter on a CREATE- or UPDATE-type change set to import existing resources with custom names instead of recreating them. (9dd25ec)

`v3.451.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-cloudformation

aws/aws-sdk-js-v3 (@aws-sdk/client-lambda)

`v3.461.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-lambda

`v3.460.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-lambda

`v3.458.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-lambda

`v3.454.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-lambda

`v3.453.0`

Compare Source

Features

client-lambda: Adds support for logging configuration in Lambda Functions. Customers will have more control how their function logs are captured and to which cloud watch log group they are delivered also. (3640ab6)

`v3.452.0`

Compare Source

Features

client-lambda: Add Java 21 (java21) support to AWS Lambda (39e78bd)

`v3.451.0`

Compare Source

Features

client-lambda: Add Python 3.12 (python3.12) support to AWS Lambda (b388fbe)

conventional-changelog/commitlint (@commitlint/cli)

`v18.4.3`

Compare Source

Note: Version bump only for package @commitlint/cli

`v18.4.2`

Compare Source

Note: Version bump only for package @commitlint/cli

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

`v18.4.3`

Compare Source

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

`v18.4.2`

Compare Source

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

conventional-changelog/commitlint (@commitlint/types)

`v18.4.3`

Compare Source

Note: Version bump only for package @commitlint/types

ardatan/graphql-tools (@graphql-tools/merge)

`v9.0.1`

Compare Source

Patch Changes

a570a601
Thanks @ardatan! - Add respectArrays flag to extensions merging
Updated dependencies
[a570a601]:
- @graphql-tools/utils @10.0.10

ardatan/graphql-tools (@graphql-tools/utils)

`v10.0.11`

Compare Source

Patch Changes

#4886
d3fe8d8c
Thanks @ldiqual! - Print debug timer logs by respecting the filters
in DEBUG env var

`v10.0.10`

Compare Source

Patch Changes

a570a601
Thanks @ardatan! - Add respectArrays flag to extensions merging

`v10.0.9`

Compare Source

Patch Changes

e1fb8bb8
Thanks @ardatan! - Merge directives in the extensions

prisma/prisma (@prisma/client)

`v5.6.0`

Compare Source

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

Highlights

Driver adapters improvements (Preview)

In version 5.4.0, we released driverAdapters into Preview. The driverAdapters feature enables Prisma Client to access your database using JavaScript or Serverless database drivers.

In this release, we fixed many bugs for the existing driver adapters. We appreciate all the community feedback that has helped us improve this feature!

PlanetScale serverless driver adapter improvements

This release also introduces a small breaking change to the @prisma/adapter-planetscale package to improve its stability and performance. The serverless driver adapter will now use a connection pool instead of a single connection from PlanetScale’s serverless driver.

In case you’re using the @prisma/adapter-planetscale, update your Prisma Client instance with the following:

-import { connect } from '@&#8203;planetscale/database'
+import { Client } from '@&#8203;planetscale/database'
import { PrismaPlanetScale } from '@&#8203;prisma/adapter-planetscale'
import { PrismaClient } from '@&#8203;prisma/client'
import { fetch as undiciFetch } from 'undici';

-const connection = connect({ url: connectionString, fetch: undiciFetch })
+const client = new Client({ url: connectionString, fetch: undiciFetch })

-const adapter = new PrismaPlanetScale(connection)
+const adapter = new PrismaPlanetScale(client)

const prisma = new PrismaClient({ adapter })

Request for feedback

We encourage you to try out the driver adapters and share your feedback to help us move it to General Availability in either of the following GitHub discussions:

Refer to our docs to learn more about driver adapters.

New `prisma debug` command

This release introduces a new command: prisma debug. The command provides debugging information such as environment variables that Prisma Client, Prisma Migrate, Prisma CLI, and Prisma Studio use. The command is also useful when creating a bug report as the information complements the output of the prisma -v command.

You can learn more about the command in our docs.

Read replicas extension improvements

We also released version 0.3.0 of the @prisma/extension-read-replicas package that contains the following improvements:

A new $replica() method that explicitly enables you to use a replica for your query.

For example, by default, the queryRaw and executeRaw methods are forwarded to the primary database, as they could try to write to the database. You can use the $replica() method with either of the *Raw methods to explicitly execute your query against a replica instead of your primary database.
Validation for when there’s an empty list of replicas.
Webpack bundling fixes

We want to thank you, our community members, for your contributions! 🙏

You can find additional information on the changes in the extension’s release. You can learn more about the extension in the announcement blog post.

Package provenance

npm has introduced provenance statements to improve supply-chain security and transparency of packages. This allows developers to verify where and how packages are built.

Starting with the 5.6.0 release, all npm packages for Prisma ORM will be published with provenance statements. If you maintain a Prisma Client extension or generator, we encourage you to enable provenance statements when publishing to npm.

Fixes and improvements

Prisma Migrate

Prisma Client

Prisma CLI

prisma debug

Credits

Huge thanks to @onichandame, @LucianBuzzo, @RobertCraigie, @fqazi, @KhooHaoYit, @alencardc, @Oreilles, @christianledgard, @skyzh, @alula, @luxaritas, @Nasfame, @lukahartwig, @steebchen, @icanipa for helping!

Miscellaneous

Prisma Accelerate is now Generally Available

We're excited to share that Prisma Accelerate is now Generally Available. Prisma Accelerate is a global database cache that's available in over 280 locations and provides scalable connection pooling for serverless and edge applications.

Learn more in the announcement blog post. Sign up and try out Prisma Accelerate

💼 We’re hiring!

If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you.

We're hiring for an Engineering Manager: Prisma Data Platform.

awslabs/smithy-typescript (@smithy/util-waiter)

`v2.0.14`

Compare Source

Patch Changes

Updated dependencies [9bfc64e]
Updated dependencies [9579a9a]
- @smithy/types @2.6.0
- @smithy/abort-controller @2.0.14

`v2.0.13`

Compare Source

Patch Changes

Updated dependencies [8044a81]
- @smithy/types @2.5.0
- @smithy/abort-controller @2.0.13

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

`v6.13.1`

Compare Source

Note: Version bump only for package @typescript-eslint/eslint-plugin

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

`v6.13.0`

Compare Source

Note: Version bump only for package @typescript-eslint/eslint-plugin

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

`v6.12.0`

Compare Source

Bug Fixes

eslint-plugin: [class-methods-use-this] detect a problematic case for private/protected members if ignoreClassesThatImplementAnInterface is set (#7705) (155aa1f)
eslint-plugin: [no-unnecessary-condition] fix false positive with computed member access and branded key type (#7706) (f151b26)
eslint-plugin: [switch-exhaustiveness-check] enum members with new line or single quotes are not being fixed correctly (#7806) (a034d0a), closes #7768

Features

[member-ordering] add accessor support for member-ordering (#7927) (3c8312d)
eslint-plugin: [switch-exhaustiveness-check] add requireDefaultForNonUnion option (#7880) (4cfcd45)

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

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

`v6.13.1`

Compare Source

Note: Version bump only for package @typescript-eslint/parser

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

`v6.13.0`

Compare Source

Note: Version bump only for package @typescript-eslint/parser

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

`v6.12.0`

Compare Source

Note: Version bump only for package @typescript-eslint/parser

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

aws/aws-cdk (aws-cdk)

`v2.111.0`

Compare Source

Features

aws-logs: add LogGroupClass property to AWS::Logs::LogGroup (da47ee6)

Alpha modules (2.111.0-alpha.0)

`v2.110.1`

Compare Source

Bug Fixes

cli: hotswap cannot evaluate nested stacks within nested stacks (8fa6bdd)

Alpha modules (2.110.1-alpha.0)

`v2.110.0`

Compare Source

Features

lambda: support for advanced logging (#28039) (3278c19)
update AWS Service Spec (#28034) (1d1876c)

Alpha modules (2.110.0-alpha.0)

`v2.109.0`

Compare Source

Features

update AWS Service Spec (#28011) (f0939f2)
apigateway: support firehose access log destination (#27959) (33357aa), closes #27954
eks: support for Kubernetes version 1.28 (#27930) (0b1f818), closes #27500
lambda: add java 21 lambda runtime (#27822) (ef4dee6)
lambda: add python 3.12 runtime (#27967) (9d17fe2)
lambda: node20 runtime (#27897) (2e3cdd9)
lambda: Support S3 as onFailure destinations on MSK and SelfManagedKafka events (#28010) (e789adc)
rds: support for aurora mysql 3.04.1 (#28002) (846c26a)
update AWS Service Spec (#27958) (1466207)

Bug Fixes

ec2: AmazonLinuxImage construct generates incorrect SSM parameter name for AL2023 images (#27698) (f6c1e62), closes /github.com/aws/aws-cdk/blob/d0d75478e1cf3bb9a06f33642b9a06fc68d0c99d/packages/aws-cdk-lib/aws-ec2/lib/machine-image/amazon-linux2.ts#L77-L84 /github.com/aws/aws-cdk/blob/d0d75478e1cf3bb9a06f33642b9a06fc68d0c99d/packages/aws-cdk-lib/aws-ec2/lib/machine-image/amazon-linux-2023.ts#L59-L66 #27638
elasticloadbalancingv2: access logging fails on imported bucket (#27948) (ba11f36), closes #27928
events: imported event rule ignores environment from arn (#27907) (bfbe756)
sqs: imported queue ignores environment from arn (#27906) (633dbe2)

Reverts

"chore(cdk): boostrap template uses deprecated AccessControl property" (#27939) (093c4ed), closes aws/aws-cdk#27764

Alpha modules (2.109.0-alpha.0)

Bug Fixes

integ-runner: fails with "no such file or directory, open 'node_modules/@aws-cdk/integ-runner/lib/workers/db.json.gz'" (#27983) (56daf0b)
integ-runner: update workflow error message is inaccurate (#27924) (844cd6f)

`v2.108.1`

Compare Source

Bug Fixes

elasticloadbalancingv2: access logging fails on imported bucket (#27948) (8243601), closes #27928

Alpha modules (2.108.1-alpha.0)

`v2.108.0`

Compare Source

Features

lambda: add python 3.12 runtime (#27967) (505907a)

Alpha modules (2.108.0-alpha.0)

`v2.107.0`

Compare Source

Features

lambda: node20 runtime (#27897) (a5acd0f)

Alpha modules (2.107.0-alpha.0)

evanw/esbuild (esbuild)

`v0.19.8`

Compare Source

Add a treemap chart to esbuild's bundle analyzer (#2848)

The bundler analyzer on esbuild's website (https://esbuild.github.io/analyze/) now has a treemap chart type in addition to the two existing chart types (sunburst and flame). This should be more familiar for people coming from other similar tools, as well as make better use of large screens.
Allow decorators after the export keyword (#104)

Previously esbuild's decorator parser followed the original behavior of TypeScript's experimental decorators feature, which only allowed decorators to come before the export keyword. However, the upcoming JavaScript decorators feature also allows decorators to come after the export keyword. And with TypeScript 5.0, TypeScript now also allows experimental decorators to come after the export keyword too. So esbuild now allows this as well:
```
// This old syntax has always been permitted:
@&#8203;decorator export class Foo {}
@&#8203;decorator export default class Foo {}

// This new syntax is now permitted too:
export @&#8203;decorator class Foo {}
export default @&#8203;decorator class Foo {}
```
In addition, esbuild's decorator parser has been rewritten to fix several subtle and likely unimportant edge cases with esbuild's parsing of exports and decorators in TypeScript (e.g. TypeScript apparently does automatic semicolon insertion after interface and export interface but not after export default interface).

Pretty-print decorators using the same whitespace as the original

When printing code containing decorators, esbuild will now try to respect whether the original code contained newlines after the decorator or not. This can make generated code containing many decorators much more compact to read:

// Original code
class Foo {
  @&#8203;a @&#8203;b @&#8203;c abc
  @&#8203;x @&#8203;y @&#8203;z xyz
}

// Old output
class Foo {
  @&#8203;a
  @&#8203;b
  @&#8203;c
  abc;
  @&#8203;x
  @&#8203;y
  @&#8203;z
  xyz;
}

// New output
class Foo {
  @&#8203;a @&#8203;b @&#8203;c abc;
  @&#8203;x @&#8203;y @&#8203;z xyz;
}

`v0.19.7`

Compare Source

Add support for bundling code that uses import attributes (#3384)

JavaScript is gaining new syntax for associating a map of string key-value pairs with individual ESM imports. The proposal is still a work in progress and is still undergoing significant changes before being finalized. However, the first iteration has already been shipping in Chromium-based browsers for a while, and the second iteration has landed in V8 and is now shipping in node, so it makes sense for esbuild to support it. Here are the two major iterations of this proposal (so far):
1. Import assertions (deprecated, will not be standardized)
  - Uses the assert keyword
  - Does not affect module resolution
  - Causes an error if the assertion fails
  - Shipping in Chrome 91+ (and in esbuild 0.11.22+)
2. Import attributes (currently set to become standardized)
  - Uses the with keyword
  - Affects module resolution
  - Unknown attributes cause an error
  - Shipping in node 21+
You can already use esbuild to bundle code that uses import assertions (the first iteration). However, this feature is mostly useless for bundlers because import assertions are not allowed to affect module resolution. It's basically only useful as an annotation on external imports, which esbuild will then preserve in the output for use in a browser (which would otherwise refuse to load certain imports).

With this release, esbuild now supports bundling code that uses import attributes (the second iteration). This is much more useful for bundlers because they are allowed to affect module resolution, which means the key-value pairs can be provided to plugins. Here's an example, which uses esbuild's built-in support for the upcoming JSON module standard:
```
// On static imports
import foo from './package.json' with { type: 'json' }
console.log(foo)

// On dynamic imports
const bar = await import('./package.json', { with: { type: 'json' } })
console.log(bar)
```
One important consequence of the change in semantics between import assertions and import attributes is that two imports with identical paths but different import attributes are now considered to be different modules. This is because the import attributes are provided to the loader, which might then use those attributes during loading. For example, you could imagine an image loader that produces an image of a different size depending on the import attributes.

Import attributes are now reported in the metafile and are now provided to on-load plugins as a map in the with property. For example, here's an esbuild plugin that turns all imports with a type import attribute equal to 'cheese' into a module that exports the cheese emoji:
```
const cheesePlugin = {
  name: 'cheese',
  setup(build) {
    build.onLoad({ filter: /.*/ }, args => {
      if (args.with.type === 'cheese') return {
        contents: `export default "🧀"`,
      }
    })
  }
}

require('esbuild').build({
  bundle: true,
  write: false,
  stdin: {
    contents: `
      import foo from 'data:text/javascript,' with { type: 'cheese' }
      console.log(foo)
    `,
  },
  plugins: [cheesePlugin],
}).then(result => {
  const code = new Function(result.outputFiles[0].text)
  code()
})
```
Warning: It's possible that the second iteration of this feature may change significantly again even though it's already shipping in real JavaScript VMs (since it has already happened once before). In that case, esbuild may end up adjusting its implementation to match the eventual standard behavior. So keep in mind that by using this, you are using an unstable upcoming JavaScript feature that may undergo breaking changes in the future.
Adjust TypeScript experimental decorator behavior (#3230, #3326, #3394)

With this release, esbuild will now allow TypeScript experimental decorators to access both static class properties and #private class names. For example:
```
const check =
  <T,>(a: T, b: T): PropertyDecorator =>
    () => console.log(a === b)

async function test() {
  class Foo {
    static #foo = 1
    static bar = 1 + Foo.#foo
    @&#8203;check(Foo.#foo, 1) a: any
    @&#8203;check(Foo.bar, await Promise.resolve(2)) b: any
  }
}

test().then(() => console.log('pass'))
```
This will now print true true pass when compiled by esbuild. Previously esbuild evaluated TypeScript decorators outside of the class body, so it didn't allow decorators to access Foo or #foo. Now esbuild does something different, although it's hard to concisely explain exactly what esbuild is doing now (see the background section below for more information).

Note that TypeScript's experimental decorator support is currently buggy: TypeScript's compiler passes this test if only the first @check is present or if only the second @check is present, but TypeScript's compiler fails this test if both checks are present together. I haven't changed esbuild to match TypeScript's behavior exactly here because I'm waiting for TypeScript to fix these bugs instead.

Some background: TypeScript experimental decorators don't have consistent semantics regarding the context that the decorators are evaluated in. For example, TypeScript will let you use await within a decorator, which implies that the decorator runs outside the class body (since await isn't supported inside a class body), but TypeScript will also let you use #private names, which implies that the decorator runs inside the class body (since #private names are only supported inside a class body). The value of this in a decorator is also buggy (the run-time value of this changes if any decorator in the class uses a #private name but the type of this doesn't change, leading to the type checker no longer matching reality). These inconsistent semantics make it hard for esbuild to implement this feature as decorator evaluation happens in some superposition of both inside and outside the class body that is particular to the internal implementation details of the TypeScript compiler.
Forbid --keep-names when targeting old browsers (#3477)

The --keep-names setting needs to be able to assign to the name property on functions and classes. However, before ES6 this property was non-configurable, and attempting to assign to it wo

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (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 has been generated by Mend Renovate. View repository job log here.

renovate bot added the type: dependency Pull requests that update a dependency file label Dec 1, 2023

renovate bot temporarily deployed to staging-114 December 1, 2023 01:04 Inactive

renovate bot temporarily deployed to staging-114-docs December 1, 2023 01:04 Inactive