Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [github.com/evanw/esbuild](https://togithub.com/evanw/esbuild) | require | patch | `v0.16.3` -> `v0.16.7` | | [github.com/go-test/deep](https://togithub.com/go-test/deep) | require | minor | `v1.0.8` -> `v1.1.0` | | [github.com/onsi/ginkgo/v2](https://togithub.com/onsi/ginkgo) | require | minor | `v2.5.1` -> `v2.6.1` | | [github.com/onsi/gomega](https://togithub.com/onsi/gomega) | require | patch | `v1.24.1` -> `v1.24.2` | | [golang.org/x/exp](https://togithub.com/golang/exp) | require | digest | `732eee0` -> `0915cd7` | | [golang.org/x/mod](https://togithub.com/golang/mod) | require | minor | `v0.6.0` -> `v0.7.0` | | [helm.sh/helm/v3](https://togithub.com/helm/helm) | require | patch | `v3.10.2` -> `v3.10.3` | | [k8s.io/apimachinery](https://togithub.com/kubernetes/apimachinery) | require | minor | `v0.25.5` -> `v0.26.0` | --- ### ⚠ Dependency Lookup Warnings ⚠ Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>evanw/esbuild</summary> ### [`v0.16.7`](https://togithub.com/evanw/esbuild/releases/tag/v0.16.7) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.16.6...v0.16.7) - Include `file` loader strings in metafile imports ([#​2731](https://togithub.com/evanw/esbuild/issues/2731)) Bundling a file with the `file` loader copies that file to the output directory and imports a module with the path to the copied file in the `default` export. Previously when bundling with the `file` loader, there was no reference in the metafile from the JavaScript file containing the path string to the copied file. With this release, there will now be a reference in the metafile in the `imports` array with the kind `file-loader`: ```diff { ... "outputs": { "out/image-55CCFTCE.svg": { ... }, "out/entry.js": { "imports": [ + { + "path": "out/image-55CCFTCE.svg", + "kind": "file-loader" + } ], ... } } } ``` - Fix byte counts in metafile regarding references to other output files ([#​2071](https://togithub.com/evanw/esbuild/issues/2071)) Previously files that contained references to other output files had slightly incorrect metadata for the byte counts of input files which contributed to that output file. So for example if `app.js` imports `image.png` using the file loader and esbuild generates `out.js` and `image-LSAMBFUD.png`, the metadata for how many bytes of `out.js` are from `app.js` was slightly off (the metadata for the byte count of `out.js` was still correct). The reason is because esbuild substitutes the final paths for references between output files toward the end of the build to handle cyclic references, and the byte counts needed to be adjusted as well during the path substitution. This release fixes these byte counts (specifically the `bytesInOutput` values). - The alias feature now strips a trailing slash ([#​2730](https://togithub.com/evanw/esbuild/issues/2730)) People sometimes add a trailing slash to the name of one of node's built-in modules to force node to import from the file system instead of importing the built-in module. For example, importing `util` imports node's built-in module called `util` but importing `util/` tries to find a package called `util` on the file system. Previously attempting to use esbuild's package alias feature to replace imports to `util` with a specific file would fail because the file path would also gain a trailing slash (e.g. mapping `util` to `./file.js` turned `util/` into `./file.js/`). With this release, esbuild will now omit the path suffix if it's a single trailing slash, which should now allow you to successfully apply aliases to these import paths. ### [`v0.16.6`](https://togithub.com/evanw/esbuild/releases/tag/v0.16.6) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.16.5...v0.16.6) - Do not mark subpath imports as external with `--packages=external` ([#​2741](https://togithub.com/evanw/esbuild/issues/2741)) Node has a feature called [subpath imports](https://nodejs.org/api/packages.html#subpath-imports) where special import paths that start with `#` are resolved using the `imports` field in the `package.json` file of the enclosing package. The intent of the newly-added `--packages=external` setting is to exclude a package's dependencies from the bundle. Since a package's subpath imports are only accessible within that package, it's wrong for them to be affected by `--packages=external`. This release changes esbuild so that `--packages=external` no longer affects subpath imports. - Forbid invalid numbers in JSON files Previously esbuild parsed numbers in JSON files using the same syntax as JavaScript. But starting from this release, esbuild will now parse them with JSON syntax instead. This means the following numbers are no longer allowed by esbuild in JSON files: - Legacy octal literals (non-zero integers starting with `0`) - The `0b`, `0o`, and `0x` numeric prefixes - Numbers containing `_` such as `1_000` - Leading and trailing `.` such as `0.` and `.0` - Numbers with a space after the `-` such as `- 1` - Add external imports to metafile ([#​905](https://togithub.com/evanw/esbuild/issues/905), [#​1768](https://togithub.com/evanw/esbuild/issues/1768), [#​1933](https://togithub.com/evanw/esbuild/issues/1933), [#​1939](https://togithub.com/evanw/esbuild/issues/1939)) External imports now appear in `imports` arrays in the metafile (which is present when bundling with `metafile: true`) next to normal imports, but additionally have `external: true` to set them apart. This applies both to files in the `inputs` section and the `outputs` section. Here's an example: ```diff { "inputs": { "style.css": { "bytes": 83, "imports": [ + { + "path": "https://cdn.jsdelivr.net/npm/bootstrap@5.2.3/dist/css/bootstrap.min.css", + "kind": "import-rule", + "external": true + } ] }, "app.js": { "bytes": 100, "imports": [ + { + "path": "https://cdn.jsdelivr.net/npm/bootstrap@5.2.3/dist/js/bootstrap.min.js", + "kind": "import-statement", + "external": true + }, { "path": "style.css", "kind": "import-statement" } ] } }, "outputs": { "out/app.js": { "imports": [ + { + "path": "https://cdn.jsdelivr.net/npm/bootstrap@5.2.3/dist/js/bootstrap.min.js", + "kind": "require-call", + "external": true + } ], "exports": [], "entryPoint": "app.js", "cssBundle": "out/app.css", "inputs": { "app.js": { "bytesInOutput": 113 }, "style.css": { "bytesInOutput": 0 } }, "bytes": 528 }, "out/app.css": { "imports": [ + { + "path": "https://cdn.jsdelivr.net/npm/bootstrap@5.2.3/dist/css/bootstrap.min.css", + "kind": "import-rule", + "external": true + } ], "inputs": { "style.css": { "bytesInOutput": 0 } }, "bytes": 100 } } } ``` One additional useful consequence of this is that the `imports` array is now populated when bundling is disabled. So you can now use esbuild with bundling disabled to inspect a file's imports. ### [`v0.16.5`](https://togithub.com/evanw/esbuild/releases/tag/v0.16.5) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.16.4...v0.16.5) - Make it easy to exclude all packages from a bundle ([#​1958](https://togithub.com/evanw/esbuild/issues/1958), [#​1975](https://togithub.com/evanw/esbuild/issues/1975), [#​2164](https://togithub.com/evanw/esbuild/issues/2164), [#​2246](https://togithub.com/evanw/esbuild/issues/2246), [#​2542](https://togithub.com/evanw/esbuild/issues/2542)) When bundling for node, it's often necessary to exclude npm packages from the bundle since they weren't designed with esbuild bundling in mind and don't work correctly after being bundled. For example, they may use `__dirname` and run-time file system calls to load files, which doesn't work after bundling with esbuild. Or they may compile a native `.node` extension that has similar expectations about the layout of the file system that are no longer true after bundling (even if the `.node` extension is copied next to the bundle). The way to get this to work with esbuild is to use the `--external:` flag. For example, the [`fsevents`](https://www.npmjs.com/package/fsevents) package contains a native `.node` extension and shouldn't be bundled. To bundle code that uses it, you can pass `--external:fsevents` to esbuild to exclude it from your bundle. You will then need to ensure that the `fsevents` package is still present when you run your bundle (e.g. by publishing your bundle to npm as a package with a dependency on `fsevents`). It was possible to automatically do this for all of your dependencies, but it was inconvenient. You had to write some code that read your `package.json` file and passed the keys of the `dependencies`, `devDependencies`, `peerDependencies`, and/or `optionalDependencies` maps to esbuild as external packages (either that or write a plugin to mark all package paths as external). Previously esbuild's recommendation for making this easier was to do `--external:./node_modules/*` (added in version 0.14.13). However, this was a bad idea because it caused compatibility problems with many node packages as it caused esbuild to mark the post-resolve path as external instead of the pre-resolve path. Doing that could break packages that are published as both CommonJS and ESM if esbuild's bundler is also used to do a module format conversion. With this release, you can now do the following to automatically exclude all packages from your bundle: - CLI: esbuild --bundle --packages=external - JS: ```js esbuild.build({ bundle: true, packages: 'external', }) ``` - Go: ```go api.Build(api.BuildOptions{ Bundle: true, Packages: api.PackagesExternal, }) ``` Doing `--external:./node_modules/*` is still possible and still has the same behavior, but is no longer recommended. I recommend that you use the new `packages` feature instead. - Fix some subtle bugs with tagged template literals This release fixes a bug where minification could incorrectly change the value of `this` within tagged template literal function calls: ```js // Original code function f(x) { let z = y.z return z`` } // Old output (with --minify) function f(n){return y.z``} // New output (with --minify) function f(n){return(0,y.z)``} ``` This release also fixes a bug where using optional chaining with `--target=es2019` or earlier could incorrectly change the value of `this` within tagged template literal function calls: ```js // Original code var obj = { foo: function() { console.log(this === obj); } }; (obj?.foo)``; // Old output (with --target=es6) var obj = { foo: function() { console.log(this === obj); } }; (obj == null ? void 0 : obj.foo)``; // New output (with --target=es6) var __freeze = Object.freeze; var __defProp = Object.defineProperty; var __template = (cooked, raw) => __freeze(__defProp(cooked, "raw", { value: __freeze(raw || cooked.slice()) })); var _a; var obj = { foo: function() { console.log(this === obj); } }; (obj == null ? void 0 : obj.foo).call(obj, _a || (_a = __template([""]))); ``` - Some slight minification improvements The following minification improvements were implemented: - `if (~a !== 0) throw x;` => `if (~a) throw x;` - `if ((a | b) !== 0) throw x;` => `if (a | b) throw x;` - `if ((a & b) !== 0) throw x;` => `if (a & b) throw x;` - `if ((a ^ b) !== 0) throw x;` => `if (a ^ b) throw x;` - `if ((a << b) !== 0) throw x;` => `if (a << b) throw x;` - `if ((a >> b) !== 0) throw x;` => `if (a >> b) throw x;` - `if ((a >>> b) !== 0) throw x;` => `if (a >>> b) throw x;` - `if (!!a || !!b) throw x;` => `if (a || b) throw x;` - `if (!!a && !!b) throw x;` => `if (a && b) throw x;` - `if (a ? !!b : !!c) throw x;` => `if (a ? b : c) throw x;` ### [`v0.16.4`](https://togithub.com/evanw/esbuild/releases/tag/v0.16.4) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.16.3...v0.16.4) - Fix binary downloads from the `@esbuild/` scope for Deno ([#​2729](https://togithub.com/evanw/esbuild/issues/2729)) Version 0.16.0 of esbuild moved esbuild's binary executables into npm packages under the `@esbuild/` scope, which accidentally broke the binary downloader script for Deno. This release fixes this script so it should now be possible to use esbuild version 0.16.4+ with Deno. </details> <details> <summary>go-test/deep</summary> ### [`v1.1.0`](https://togithub.com/go-test/deep/blob/HEAD/CHANGES.md#v110-released-2022-12-09) [Compare Source](https://togithub.com/go-test/deep/compare/v1.0.9...v1.1.0) - Add optional flags: `Equal(a, b, flags..)` and `FLAG_IGNORE_SLICE_ORDER` (issue [#​28](https://togithub.com/go-test/deep/issues/28), PR [#​56](https://togithub.com/go-test/deep/issues/56)) ([@​alenkacz](https://togithub.com/alenkacz)) *** ### [`v1.0.9`](https://togithub.com/go-test/deep/blob/HEAD/CHANGES.md#v109-released-2022-12-09) [Compare Source](https://togithub.com/go-test/deep/compare/v1.0.8...v1.0.9) - Fixed issue [#​45](https://togithub.com/go-test/deep/issues/45): Panic when comparing errors in unexported fields (PR [#​54](https://togithub.com/go-test/deep/issues/54)) ([@​seveas](https://togithub.com/seveas)) - Fixed issue [#​46](https://togithub.com/go-test/deep/issues/46): Functions are handled differently from reflect.DeepEqual (PR [#​55](https://togithub.com/go-test/deep/issues/55)) ([@​countcb](https://togithub.com/countcb)) - Updated matrix to go1.17, go1.18, and go1.19 and moved testing to GitHub Actions </details> <details> <summary>onsi/ginkgo</summary> ### [`v2.6.1`](https://togithub.com/onsi/ginkgo/releases/tag/v2.6.1) [Compare Source](https://togithub.com/onsi/ginkgo/compare/v2.6.0...v2.6.1) #### 2.6.1 ##### Features - Override formatter colors from envvars - this is a new feature but an alternative approach involving config files might be taken in the future ([#​1095](https://togithub.com/onsi/ginkgo/issues/1095)) \[[`60240d1`](https://togithub.com/onsi/ginkgo/commit/60240d1)] ##### Fixes - GinkgoRecover now supports ignoring panics that match a specific, hidden, interface \[[`301f3e2`](https://togithub.com/onsi/ginkgo/commit/301f3e2)] ##### Maintenance - Bump github.com/onsi/gomega from 1.24.0 to 1.24.1 ([#​1077](https://togithub.com/onsi/ginkgo/issues/1077)) \[[`3643823`](https://togithub.com/onsi/ginkgo/commit/3643823)] - Bump golang.org/x/tools from 0.2.0 to 0.4.0 ([#​1090](https://togithub.com/onsi/ginkgo/issues/1090)) \[[`f9f856e`](https://togithub.com/onsi/ginkgo/commit/f9f856e)] - Bump nokogiri from 1.13.9 to 1.13.10 in /docs ([#​1091](https://togithub.com/onsi/ginkgo/issues/1091)) \[[`0d7087e`](https://togithub.com/onsi/ginkgo/commit/0d7087e)] ### [`v2.6.0`](https://togithub.com/onsi/ginkgo/releases/tag/v2.6.0) [Compare Source](https://togithub.com/onsi/ginkgo/compare/v2.5.1...v2.6.0) #### 2.6.0 ##### Features - `ReportBeforeSuite` provides access to the suite report before the suite begins. - Add junit config option for omitting leafnodetype ([#​1088](https://togithub.com/onsi/ginkgo/issues/1088)) \[[`956e6d2`](https://togithub.com/onsi/ginkgo/commit/956e6d2)] - Add support to customize junit report config to omit spec labels ([#​1087](https://togithub.com/onsi/ginkgo/issues/1087)) \[[`de44005`](https://togithub.com/onsi/ginkgo/commit/de44005)] ##### Fixes - Fix stack trace pruning so that it has a chance of working on windows \[[`2165648`](https://togithub.com/onsi/ginkgo/commit/2165648)] </details> <details> <summary>onsi/gomega</summary> ### [`v1.24.2`](https://togithub.com/onsi/gomega/releases/tag/v1.24.2) [Compare Source](https://togithub.com/onsi/gomega/compare/v1.24.1...v1.24.2) #### 1.24.2 ##### Fixes - Correctly handle assertion failure panics for eventually/consistnetly "g Gomega"s in a goroutine \[[`78f1660`](https://togithub.com/onsi/gomega/commit/78f1660)] - docs:Fix typo "you an" -> "you can" ([#​607](https://togithub.com/onsi/gomega/issues/607)) \[[`3187c1f`](https://togithub.com/onsi/gomega/commit/3187c1f)] - fixes issue [#​600](https://togithub.com/onsi/gomega/issues/600) ([#​606](https://togithub.com/onsi/gomega/issues/606)) \[[`808d192`](https://togithub.com/onsi/gomega/commit/808d192)] ##### Maintenance - Bump golang.org/x/net from 0.2.0 to 0.4.0 ([#​611](https://togithub.com/onsi/gomega/issues/611)) \[[`6ebc0bf`](https://togithub.com/onsi/gomega/commit/6ebc0bf)] - Bump nokogiri from 1.13.9 to 1.13.10 in /docs ([#​612](https://togithub.com/onsi/gomega/issues/612)) \[[`258cfc8`](https://togithub.com/onsi/gomega/commit/258cfc8)] - Bump github.com/onsi/ginkgo/v2 from 2.5.0 to 2.5.1 ([#​609](https://togithub.com/onsi/gomega/issues/609)) \[[`e6c3eb9`](https://togithub.com/onsi/gomega/commit/e6c3eb9)] </details> <details> <summary>golang/mod</summary> ### [`v0.7.0`](https://togithub.com/golang/mod/compare/v0.6.0...v0.7.0) [Compare Source](https://togithub.com/golang/mod/compare/v0.6.0...v0.7.0) </details> <details> <summary>helm/helm</summary> ### [`v3.10.3`](https://togithub.com/helm/helm/releases/tag/v3.10.3): Helm v3.10.3 [Compare Source](https://togithub.com/helm/helm/compare/v3.10.2...v3.10.3) #### v3.10.3 Helm v3.10.3 is a security (patch) release. Users are strongly recommended to update to this release. While fuzz testing Helm, provided by the CNCF: - a possible stack overflow was discovered with the *strvals* package. Stack overflow cannot be recovered from in Go. This can potentially be used to produce a denial of service (DOS) for SDK users. More details are available in [the advisory](https://togithub.com/helm/helm/security/advisories/GHSA-6rx9-889q-vv2r). - a possible segmentation violation was discovered with the *repo* package. Some segmentation violations cannot be recovered from in Go. This can potentially be used to produce a denial of service (DOS) for SDK users. More details are available in [the advisory](https://togithub.com/helm/helm/security/advisories/GHSA-53c4-hhmh-vw5q). - a possible segmentation violation was discovered with the *chartutil* package. This can potentially be used to produce a denial of service (DOS) for SDK users. More details are available in [the advisory](https://togithub.com/helm/helm/security/advisories/GHSA-67fx-wx78-jx33) The community keeps growing, and we'd love to see you there! - Join the discussion in [Kubernetes Slack](https://kubernetes.slack.com): - for questions and just to hang out - for discussing PRs, code, and bugs - Hang out at the Public Developer Call: Thursday, 9:30 Pacific via [Zoom](https://zoom.us/j/696660622) - Test, debug, and contribute charts: [ArtifactHub/packages](https://artifacthub.io/packages/search?kind=0) #### Installation and Upgrading Download Helm v3.10.3. The common platform binaries are here: - [MacOS amd64](https://get.helm.sh/helm-v3.10.3-darwin-amd64.tar.gz) ([checksum](https://get.helm.sh/helm-v3.10.3-darwin-amd64.tar.gz.sha256sum) / 77a94ebd37eab4d14aceaf30a372348917830358430fcd7e09761eed69f08be5) - [MacOS arm64](https://get.helm.sh/helm-v3.10.3-darwin-arm64.tar.gz) ([checksum](https://get.helm.sh/helm-v3.10.3-darwin-arm64.tar.gz.sha256sum) / 4f3490654349d6fee8d4055862efdaaf9422eca1ffd2a15393394fd948ae3377) - [Linux amd64](https://get.helm.sh/helm-v3.10.3-linux-amd64.tar.gz) ([checksum](https://get.helm.sh/helm-v3.10.3-linux-amd64.tar.gz.sha256sum) / 950439759ece902157cf915b209b8d694e6f675eaab5099fb7894f30eeaee9a2) - [Linux arm](https://get.helm.sh/helm-v3.10.3-linux-arm.tar.gz) ([checksum](https://get.helm.sh/helm-v3.10.3-linux-arm.tar.gz.sha256sum) / dca718eb68c72c51fc7157c4c2ebc8ce7ac79b95fc9355c5427ded99e913ec4c) - [Linux arm64](https://get.helm.sh/helm-v3.10.3-linux-arm64.tar.gz) ([checksum](https://get.helm.sh/helm-v3.10.3-linux-arm64.tar.gz.sha256sum) / 260cda5ff2ed5d01dd0fd6e7e09bc80126e00d8bdc55f3269d05129e32f6f99d) - [Linux i386](https://get.helm.sh/helm-v3.10.3-linux-386.tar.gz) ([checksum](https://get.helm.sh/helm-v3.10.3-linux-386.tar.gz.sha256sum) / 592e98a492cb782aa7cd67e9afad76e51cd68f5160367600fe542c2d96aa0ad4) - [Linux ppc64le](https://get.helm.sh/helm-v3.10.3-linux-ppc64le.tar.gz) ([checksum](https://get.helm.sh/helm-v3.10.3-linux-ppc64le.tar.gz.sha256sum) / 93cdf398abc68e388d1b46d49d8e1197544930ecd3e81cc58d0a87a4579d60ed) - [Linux s390x](https://get.helm.sh/helm-v3.10.3-linux-s390x.tar.gz) ([checksum](https://get.helm.sh/helm-v3.10.3-linux-s390x.tar.gz.sha256sum) / 6cfa0b9078221f980ef400dc40c95eb71be81d14fdf247ca55efedb068e1d4fa) - [Windows amd64](https://get.helm.sh/helm-v3.10.3-windows-amd64.zip) ([checksum](https://get.helm.sh/helm-v3.10.3-windows-amd64.zip.sha256sum) / 5d97aa26830c1cd6c520815255882f148040587fd7cdddb61ef66e4c081566e0) This release was signed with ` F126 1BDE 9290 12C8 FF2E 501D 6EA5 D759 8529 A53E ` and can be found at [@​hickeyma](https://togithub.com/hickeyma) [keybase account](https://keybase.io/hickeyma). Please use the attached signatures for verifying this release using `gpg`. The [Quickstart Guide](https://helm.sh/docs/intro/quickstart/) will get you going from there. For **upgrade instructions** or detailed installation notes, check the [install guide](https://helm.sh/docs/intro/install/). You can also use a [script to install](https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3) on any system with `bash`. #### What's Next - 3.11.0 is the next feature release and will be on January 18, 2023. #### Changelog - Fix backwards compatibility [`835b733`](https://togithub.com/helm/helm/commit/835b7334cfe2e5e27870ab3ed4135f136eecc704) (Martin Hickey) - Update string handling [`3caf8b5`](https://togithub.com/helm/helm/commit/3caf8b586b47e838e492f9ec05396bf8c5851b92) (Martin Hickey) - Update repo handling [`7c0e203`](https://togithub.com/helm/helm/commit/7c0e203529d4b9d51c5fe57c9e0bd9df1bd95ab4) (Martin Hickey) - Update schema validation handling [`f4b9322`](https://togithub.com/helm/helm/commit/f4b93226c6066e009a5162d0b08debbf3d82a67f) (Martin Hickey) </details> <details> <summary>kubernetes/apimachinery</summary> ### [`v0.26.0`](https://togithub.com/kubernetes/apimachinery/compare/v0.25.5...v0.26.0) [Compare Source](https://togithub.com/kubernetes/apimachinery/compare/v0.25.5...v0.26.0) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), 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](https://togithub.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/aspect-build/silo). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNC41MS4wIiwidXBkYXRlZEluVmVyIjoiMzQuNTQuMiJ9--> Signed-off-by: Thulio Ferraz Assis <3149049+f0rmiga@users.noreply.github.com> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Thulio Ferraz Assis <3149049+f0rmiga@users.noreply.github.com>
](https://renovatebot.com){kind=link}
- Loading branch information
1 parent
c2bf8da
commit 53fa12d