chore(deps): update all non-major dependencies #124
Merged
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:
2.0.2
->2.0.3
2.0.2
->2.0.3
3.529.1
->3.535.0
^0.0.10
->^0.0.11
5.15.12
->5.15.13
5.15.12
->5.15.13
0.0.46
->0.0.47
20.11.25
->20.11.28
2.132.0
->2.133.0
2.132.0
->2.133.0
0.20.1
->0.20.2
18.2.64
->18.2.66
18.2.21
->18.2.22
5.1.5
->5.1.6
🔧 This Pull Request updates lock files to use the latest dependency versions.
Release Notes
aws-powertools/powertools-lambda-typescript (@aws-lambda-powertools/logger)
v2.0.3
Compare Source
feat(logger): improve regex in stack trace parsing (#2121) (ebe5eef)
fix(idempotency): transform private class fields (#2230) (aa6e6e0)
improv(commons):: expand type utils functions (#2191) (9208393)
feat(commons): add fromBase64 helper function (#2188) (133159b)
fix(layers):: add createRequire banner in esm build (#2231) (730bcc9)
aws/aws-sdk-js-v3 (@aws-sdk/client-secrets-manager)
v3.535.0
Compare Source
Note: Version bump only for package @aws-sdk/client-secrets-manager
v3.534.0
Compare Source
Note: Version bump only for package @aws-sdk/client-secrets-manager
v3.533.0
Compare Source
Note: Version bump only for package @aws-sdk/client-secrets-manager
3.529.1 (2024-03-08)
Note: Version bump only for package @aws-sdk/client-secrets-manager
SvenKirschbaum/cdk-cross-account-route53 (@fallobst22/cdk-cross-account-route53)
v0.0.11
Compare Source
0.0.11 (2024-03-16)
mui/material-ui (@mui/icons-material)
v5.15.13
Compare Source
Mar 12, 2024
A big thanks to the 15 contributors who made this release possible. Here are some highights ✨
@mui/[email protected]
slots
andslotProps
type to theme (#41324) @sai6855freeSolo
mode even when there are no options, causing style problems (#41300) @rakeshmusturipaperChannel
token (#41447) @siriwatknp@mui/[email protected]
@mui/[email protected]
@mui/[email protected]
@mui/[email protected]
FormControlOwnerState
type from index (#41287) @michaeldfoley@pigment-css/[email protected]
keyframes
serialize styles error (#41395) @siriwatknpDocs
Core
All contributors of this release in alphabetical order: @alexfauquette, @brijeshb42, @CGNonofr, @cipherlogs, @danilo-leal, @Janpot, @michaeldfoley, @mnajdova, @oliviertassinari, @peterwangsc, @rakeshmusturi, @sai6855, @siriwatknp, @zanivan, @ZeeshanTamboli
trautonen/cdk-dns-validated-certificate (@trautonen/cdk-dns-validated-certificate)
v0.0.47
Compare Source
0.0.47 (2024-03-11)
aws/aws-cdk (aws-cdk)
v2.133.0
Compare Source
Features
securityGroups
inNetworkLoadBalancedFargateService
(#29431) (00e8a7b), closes #29430 /github.com/aws/aws-cdk/pull/29186#issuecomment-1959231406Bug Fixes
cdk ls
returns stack id instead of stack display name (#29447) (77189be), closes #29420Reverts
Alpha modules (2.133.0-alpha.0)
v2.132.1
Compare Source
Bug Fixes
cdk ls
returns stack id instead of stack display name (#29447) (effad1c), closes #29420Alpha modules (2.132.1-alpha.0)
evanw/esbuild (esbuild)
v0.20.2
Compare Source
Support TypeScript experimental decorators on
abstract
class fields (#3684)With this release, you can now use TypeScript experimental decorators on
abstract
class fields. This was silently compiled incorrectly in esbuild 0.19.7 and below, and was an error from esbuild 0.19.8 to esbuild 0.20.1. Code such as the following should now work correctly:JSON loader now preserves
__proto__
properties (#3700)Copying JSON source code into a JavaScript file will change its meaning if a JSON object contains the
__proto__
key. A literal__proto__
property in a JavaScript object literal sets the prototype of the object instead of adding a property named__proto__
, while a literal__proto__
property in a JSON object literal just adds a property named__proto__
. With this release, esbuild will now work around this problem by converting JSON to JavaScript with a computed property key in this case:Improve dead code removal of
switch
statements (#3659)With this release, esbuild will now remove
switch
statements in branches when minifying if they are known to never be evaluated:Empty enums should behave like an object literal (#3657)
TypeScript allows you to create an empty enum and add properties to it at run time. While people usually use an empty object literal for this instead of a TypeScript enum, esbuild's enum transform didn't anticipate this use case and generated
undefined
instead of{}
for an empty enum. With this release, you can now use an empty enum to generate an empty object literal.Handle Yarn Plug'n'Play edge case with
tsconfig.json
(#3698)Previously a
tsconfig.json
file thatextends
another file in a package with anexports
map failed to work when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.Work around issues with Deno 1.31+ (#3682)
Version 0.20.0 of esbuild changed how the esbuild child process is run in esbuild's API for Deno. Previously it used
Deno.run
but that API is being removed in favor ofDeno.Command
. As part of this change, esbuild is now calling the newunref
function on esbuild's long-lived child process, which is supposed to allow Deno to exit when your code has finished running even though the child process is still around (previously you had to explicitly call esbuild'sstop()
function to terminate the child process for Deno to be able to exit).However, this introduced a problem for Deno's testing API which now fails some tests that use esbuild with
error: Promise resolution is still pending but the event loop has already resolved
. It's unclear to me why this is happening. The call tounref
was recommended by someone on the Deno core team, and calling Node's equivalentunref
API has been working fine for esbuild in Node for a long time. It could be that I'm using it incorrectly, or that there's some reference counting and/or garbage collection bug in Deno's internals, or that Deno'sunref
just works differently than Node'sunref
. In any case, it's not good for Deno tests that use esbuild to be failing.In this release, I am removing the call to
unref
to fix this issue. This means that you will now have to call esbuild'sstop()
function to allow Deno to exit, just like you did before esbuild version 0.20.0 when this regression was introduced.Note: This regression wasn't caught earlier because Deno doesn't seem to fail tests that have outstanding
setTimeout
calls, which esbuild's test harness was using to enforce a maximum test runtime. Adding asetTimeout
was allowing esbuild's Deno tests to succeed. So this regression doesn't necessarily apply to all people using tests in Deno.vitejs/vite (vite)
v5.1.6
Compare Source
Configuration
📅 Schedule: Branch creation - "on sunday" in timezone Europe/Berlin, 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.
This PR has been generated by Mend Renovate. View repository job log here.