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

cu-infra-svc-git · 2024-03-18T00:14:50Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@aws-sdk/client-secrets-manager (source)	`^3.533.0` -> `^3.714.0`
@types/aws-lambda (source)	`^8.10.136` -> `^8.10.146`
@types/jest (source)	`^29.5.12` -> `^29.5.14`
esbuild	`^0.20.1` -> `^0.24.0`
eslint-import-resolver-typescript	`^3.6.1` -> `^3.7.0`
eslint-plugin-import	`^2.29.1` -> `^2.31.0`
eslint-plugin-prettier	`^5.1.3` -> `^5.2.1`
ioredis	`^5.3.2` -> `^5.4.1`
jsii-diff (source)	`^1.95.0` -> `^1.106.0`
jsii-docgen	`^10.3.22` -> `^10.6.1`
jsii-pacmak (source)	`^1.95.0` -> `^1.106.0`
jsii-release	`^0.2.803` -> `^0.2.926`
prettier (source)	`^3.2.5` -> `^3.4.2`
ts-jest (source)	`^29.1.2` -> `^29.2.5`

Release Notes

aws/aws-sdk-js-v3 (@aws-sdk/client-secrets-manager)

`v3.714.0`

Compare Source

Features

clients: profile setting for clients (#6728) (afd9eea)

`v3.713.0`

Compare Source

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

`v3.712.0`

Compare Source

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

`v3.709.0`

Compare Source

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

`v3.699.0`

Compare Source

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

`v3.696.0`

Compare Source

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

`v3.693.0`

Compare Source

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

`v3.692.0`

Compare Source

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

`v3.691.0`

Compare Source

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

`v3.687.0`

Compare Source

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

`v3.686.0`

Compare Source

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

`v3.682.0`

Compare Source

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

`v3.679.0`

Compare Source

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

`v3.678.0`

Compare Source

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

`v3.677.0`

Compare Source

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

`v3.675.0`

Compare Source

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

`v3.674.0`

Compare Source

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

`v3.670.0`

Compare Source

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

`v3.669.0`

Compare Source

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

`v3.668.0`

Compare Source

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

`v3.667.0`

Compare Source

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

`v3.666.0`

Compare Source

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

`v3.665.0`

Compare Source

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

`v3.664.0`

Compare Source

Features

middleware-user-agent: add client config for userAgentAppId (#6524) (2990ea8)

`v3.662.0`

Compare Source

Bug Fixes

s3-request-presigner: enable overriding hoistable headers (#6535) (3c2e59c)

3.658.1 (2024-09-25)

Bug Fixes

clients: allow empty string field values for headers (#6511) (1273ff3)

`v3.658.1`

Compare Source

Bug Fixes

clients: allow empty string field values for headers (#6511) (1273ff3)

`v3.658.0`

Compare Source

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

`v3.654.0`

Compare Source

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

3.651.1 (2024-09-13)

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

`v3.651.1`

Compare Source

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

`v3.650.0`

Compare Source

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

`v3.649.0`

Compare Source

Features

endpoints: codegen sync for request creation performance improvements (#6449) (c8e8f28)

`v3.645.0`

Compare Source

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

`v3.637.0`

Compare Source

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

`v3.635.0`

Compare Source

Features

codegen: add Smithy RPCv2 CBOR to list of protocols (#6096) (5154d4f)

`v3.632.0`

Compare Source

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

`v3.631.0`

Compare Source

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

`v3.629.0`

Compare Source

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

`v3.624.0`

Compare Source

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

`v3.623.0`

Compare Source

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

`v3.622.0`

Compare Source

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

`v3.621.0`

Compare Source

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

3.620.1 (2024-07-29)

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

`v3.620.1`

Compare Source

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

`v3.620.0`

Compare Source

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

`v3.616.0`

Compare Source

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

`v3.614.0`

Compare Source

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

`v3.613.0`

Compare Source

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

`v3.609.0`

Compare Source

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

`v3.606.0`

Compare Source

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

`v3.600.0`

Compare Source

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

`v3.599.0`

Compare Source

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

`v3.598.0`

Compare Source

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

`v3.596.0`

Compare Source

Features

client-secrets-manager: Introducing RotationToken parameter for PutSecretValue API (57ae98d)

`v3.592.0`

Compare Source

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

`v3.590.0`

Compare Source

Bug Fixes

codegen: consistently add region as config option when generated client is Sigv4 but not AWS (#6156) (06f51cc)

`v3.588.0`

Compare Source

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

`v3.587.0`

Compare Source

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

`v3.583.0`

Compare Source

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

`v3.582.0`

Compare Source

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

`v3.580.0`

Compare Source

Features

client-secrets-manager: add v2 smoke tests and smithy smokeTests trait for SDK testing (b63da55)

`v3.578.0`

Compare Source

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

`v3.577.0`

Compare Source

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

`v3.576.0`

Compare Source

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

`v3.575.0`

Compare Source

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

evanw/esbuild (esbuild)

`v0.24.0`

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~0.23.0. See npm's documentation about semver for more information.

Drop support for older platforms (#3902)

This release drops support for the following operating system:
- macOS 10.15 Catalina
This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:
```
git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild --version
```
Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.
Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.
Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.
Work around more issues with Deno 1.31+ (#3917)

This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

This fix was contributed by @Joshix-1.

`v0.23.1`

Compare Source

Allow using the node: import prefix with es* targets (#3821)

The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:
```
// Original code
import fs from 'node:fs'
fs.open

// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "fs";
fs.open;

// New output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "node:fs";
fs.open;
```
Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.
Fix incorrect location of certain error messages (#3845)

This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.
Print comments before case clauses in switch statements (#3838)

With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).
Fix a memory leak with pluginData (#3825)

With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

`v0.23.0`

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.

Revert the recent change to avoid bundling dependencies for node (#3819)

This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.
Fix preserving collapsed JSX whitespace (#3818)

When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:
```
// Original code
<Foo>
  <Bar />
</Foo>

// Old output (with --jsx=preserve)
<Foo><Bar /></Foo>;

// New output (with --jsx=preserve)
<Foo>
  <Bar />
</Foo>;
```

`v0.22.0`

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.21.0 or ~0.21.0. See npm's documentation about semver for more information.

Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)

This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).
Drop support for older platforms (#3802)

This release drops support for the following operating systems:
- Windows 7
- Windows 8
- Windows Server 2008
- Windows Server 2012
This is because the Go programming language dropped support for these operating system versions in Go 1.21, and this release updates esbuild from Go 1.20 to Go 1.22.

Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.21). That might look something like this:
```
git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild.exe --version
```
In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's release schedule for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the esbuild-wasm package and versions of node before node 17.4 (specifically the crypto.getRandomValues function).
Update await using behavior to match TypeScript

TypeScript 5.5 subtly changes the way await using behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.
Allow es2024 as a target environment

The ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html. The only addition that's relevant for esbuild is the regular expression /v flag. With --target=es2024, regular expressions that use the /v flag will now be passed through untransformed instead of being transformed into a call to new RegExp.
Publish binaries for OpenBSD on 64-bit ARM (#3665, #3674)

With this release, you should now be able to install the esbuild npm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.

This was contributed by @ikmckenz.
Publish binaries for WASI (WebAssembly System Interface) preview 1 (#3300, #3779)

The upcoming WASI (WebAssembly System Interface) standard is going to be a way to run WebAssembly outside of a JavaScript host environment. In this scenario you only need a .wasm file without any supporting JavaScript code. Instead of JavaScript providing the APIs for the host environment, the WASI standard specifies a "system interface" that WebAssembly code can access directly (e.g. for file system access).

Development versions of the WASI specification are being released using preview numbers. The people behind WASI are currently working on preview 2 but the Go compiler has released support for preview 1, which from what I understand is now considered an unsupported legacy release. However, some people have requested that esbuild publish binary executables that support WASI preview 1 so they can experiment with them.

This release publishes esbuild precompiled for WASI preview 1 to the @esbuild/wasi-preview1 package on npm (specifically the file @esbuild/wasi-preview1/esbuild.wasm). This binary executable has not been tested and won't be officially supported, as it's for an old preview release of a specification that has since moved in another direction. If it works for you, great! If not, then you'll likely have to wait for the ecosystem to evolve before using esbuild with WASI. For example, it sounds like perhaps WASI preview 1 doesn't include support for opening network sockets so esbuild's local development server is unlikely to work with WASI preview 1.
Warn about onResolve plugins not setting a path (#3790)

Plugins that return values from onResolve without resolving the path (i.e. without setting either path or external: true) will now cause a warning. This is because esbuild only uses return values from onResolve if it successfully resolves the path, and it's not good for invalid input to be silently ignored.
Add a new Go API for running the CLI with plugins (#3539)

With esbuild's Go API, you can now call cli.RunWithPlugins(args, plugins) to pass an array of esbuild plugins to be used during the build process. This allows you to create a CLI that behaves similarly to esbuild's CLI but with additional Go plugins enabled.

This was contributed by @edewit.

`v0.21.5`

Compare Source

Fix Symbol.metadata on classes without a class decorator (#3781)

This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.
Allow unknown import attributes to be used with the copy loader (#3792)

Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:
```
// This is an error with "--bundle" without also using "--external:./bagel.js"
import tasty from "./bagel.js" with { type: "bagel" }
```
Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):
```
// This is no longer an error with "--bundle" and "--loader:.bagel=copy"
import tasty from "./tasty.bagel" with { type: "bagel" }
```
Support import attributes with glob-style imports (#3797)

This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:
```
async function loadLocale(locale: string): Locale {
  const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
  return unpackLocale(locale, data)
}
```
Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:
```
✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data

    example.ts:2:28:
      2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
        ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~
```
In addition, this change means plugins can now access the contents of with for glob-style imports.
Support ${configDir} in tsconfig.json files (#3782)

This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:
```
{
  "compilerOptions": {
    "paths": {
      "js/*": ["${configDir}/dist/js/*"]
    }
  }
}
```
You can r

Configuration

📅 Schedule: Branch creation - "before 2am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, 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 Renovate Bot.

codecov · 2024-11-25T01:23:07Z

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (main@2570562). Learn more about missing BASE report.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #15   +/-   ##
=======================================
  Coverage        ?   58.33%           
=======================================
  Files           ?        4           
  Lines           ?      408           
  Branches        ?        6           
=======================================
  Hits            ?      238           
  Misses          ?      170           
  Partials        ?        0

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2570562...c14f5a3. Read the comment docs.

cu-infra-svc-git added the renovate label Mar 18, 2024

cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 2 times, most recently from c9831e8 to 281863b Compare March 25, 2024 00:13

cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 3 times, most recently from f192aa3 to 4771c75 Compare April 1, 2024 00:15

cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 6 times, most recently from bad1296 to fa29dfa Compare April 12, 2024 00:13

cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 3 times, most recently from 439d7e2 to 2883897 Compare April 18, 2024 00:13

cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 4 times, most recently from 10cfd23 to a9bfab2 Compare April 30, 2024 00:12

cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 6 times, most recently from 8987d44 to ecf8669 Compare May 8, 2024 00:11

cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 5 times, most recently from 6cc81f0 to 5ff3d6e Compare May 14, 2024 22:28

cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 5 times, most recently from ccff1aa to 8e12202 Compare November 4, 2024 01:21

cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 5 times, most recently from 165bbe4 to 3953697 Compare November 12, 2024 01:21

cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 4 times, most recently from 8fb575f to 64dbdd5 Compare November 20, 2024 01:21

cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 2 times, most recently from dceacab to 29a0a40 Compare November 25, 2024 01:21

cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 3 times, most recently from 8aa71af to 55c594d Compare November 29, 2024 01:21

cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 4 times, most recently from 6b7c221 to d3b2097 Compare December 11, 2024 01:21

cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 4 times, most recently from 1c909cf to 97a598b Compare December 18, 2024 01:21

fix(deps): update all non-major dependencies

c14f5a3

cu-infra-svc-git force-pushed the renovate/all-minor-patch branch from 97a598b to c14f5a3 Compare December 19, 2024 01:21

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

cu-infra-svc-git commented Mar 18, 2024 •

edited

Loading

codecov bot commented Nov 25, 2024 •

edited

Loading

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

Are you sure you want to change the base?

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

Conversation

cu-infra-svc-git commented Mar 18, 2024 • edited Loading

Release Notes

Features

Features

Bug Fixes

3.658.1 (2024-09-25)

Bug Fixes

Bug Fixes

3.651.1 (2024-09-13)

Features

Features

3.620.1 (2024-07-29)

Features

Bug Fixes

Features

Configuration

codecov bot commented Nov 25, 2024 • edited Loading

Codecov Report

cu-infra-svc-git commented Mar 18, 2024 •

edited

Loading

codecov bot commented Nov 25, 2024 •

edited

Loading