chore(release): 1.87.0 #4226
Merged
chore(release): 1.87.0 #4226
Conversation
This file contains 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
The registration was done on the object's prototype, and the value from the constructor was always used, even if that was inherited, such that if a parent type had already been resolved previously, all child types would use the parent's FQN instead of their own. Addressed this by instead storing the associations in an external WeakMap, and added a test case to validate correct behavior. Fixes aws/aws-cdk#26604 Fixes #4202 Fixes #4203
…y installed in superchain (#4201) The packages were installed in a virtual environment, which is not subsequently re-activated in the image's ENTRYPOINT. Instead, install the packages 'globally'
Ran npm-check-updates and yarn upgrade to keep the `yarn.lock` file up-to-date.
…jsii_type__' (#4209) In the odd case where an opaque reference is returned (FQN is `Object`) and no interfaces are registered, the `InterfaceDynamicProxy` instance created to represent the value in Python did not have any delegate, resulting it in not having any visible properties; including a `__jsii_type__` value on the `__class__`, or the `__jsii_ref__` property, both of which are required for the vlaue to be able to correctly make it back to JavaScript. --- By submitting this pull request, I confirm that my contribution is made under the terms of the [Apache 2.0 license]. [Apache 2.0 license]: https://www.apache.org/licenses/LICENSE-2.0
In #4181, a faster method to load modules was introduced: symlinking instead of recursing through the directory tree, mostly affecting the load times of large modules. Since Windows Vista, non-Administrator users on Windows aren't allowed to create symlinks anymore, so this new loading method fails for users working in corporate Windows environments. Catch the error and fall back to the slower copying method if that happens. Fixes #4208. --- By submitting this pull request, I confirm that my contribution is made under the terms of the [Apache 2.0 license]. [Apache 2.0 license]: https://www.apache.org/licenses/LICENSE-2.0
Ran npm-check-updates and yarn upgrade to keep the `yarn.lock` file up-to-date.
The package cache mechanism that was turned on by default in #4181 works in theory under parallelism, but not in practice. Typically the CDK CLI will prevent CDK apps from running in parallel, but Python testing frameworks like `tox` use subprocess parallelism to speed up test runs, leading to the jsii imports being executed at the same time. Since jsii is sync, the locking needs to be sync. The sync locking feature of the `lockfile` library doesn't have wait support (for good reason), and so when a lock is already acquired by another process it quickly burns through its 12 retries in a hot loop, and then exits with an error. Two changes to address this: - (Ab)use `Atomics.wait()` to get a synchronous sleeping primitive; since `lockSync` doesn't support synchronous sleep, we build our own retry loop with synchronous sleep around `lockSync`. - Since the extracted directory is immutable: if the marker file in the extracted directory exists, we can treat it as evidence that the directory has been completely written and we can skip trying to vy for exclusive access to write it. This avoids all lock contention after the very first CDK app execution. Fixes #4207. --- By submitting this pull request, I confirm that my contribution is made under the terms of the [Apache 2.0 license]. [Apache 2.0 license]: https://www.apache.org/licenses/LICENSE-2.0
In #4201, we introduced a Python distribution built with `pyenv` in order to safely install some Python packages globally. However, using pyenv drives the build time of the images up from 30m to 3 hours. This PR switches back to the distro Python and installs `pipx` to do global installs of Python packages. `pipx` will give each tool its own venv (similar to how `npm install -g` would work). --- By submitting this pull request, I confirm that my contribution is made under the terms of the [Apache 2.0 license]. [Apache 2.0 license]: https://www.apache.org/licenses/LICENSE-2.0
…es/@jsii/go-runtime-test/project (#4220) Bumps [golang.org/x/tools](https://github.com/golang/tools) from 0.11.0 to 0.12.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/golang/tools/releases">golang.org/x/tools's releases</a>.</em></p> <blockquote> <h2>gopls/v0.12.0</h2> <p>This release contains a major rewrite of the way gopls computes and stores package information, with the goal of reducing memory usage and allowing gopls to scale to larger repositories. This change can also significantly reduce startup time when workspaces are reopened, as gopls now uses a file-based cache to persist data across sessions. With these optimizations, gopls is finally able to <a href="https://go.dev/issues/48738">fully analyze dependencies</a> using the <a href="https://pkg.go.dev/golang.org/x/tools/go/analysis">golang.org/x/tools/go/analysis</a> framework, resulting in improved accuracy for analysis diagnostics.</p> <p>You can install this release with <code>go install</code>:</p> <pre><code>go install golang.org/x/tools/gopls@v0.12.0 </code></pre> <h1>Support changes</h1> <p>As gopls matures, we're trying to simplify its configuration so that gopls Just Works in more scenarios, and so that we have fewer configuration combinations to test. This means that we will be gradually deprecating settings that affect the core behavior of gopls.</p> <h2>Removed experimental configuration options</h2> <p>As announced in the <a href="https://github.com/golang/tools/releases/tag/gopls%2Fv0.10.0">v0.10.0 release notes</a>, this release removes support for the <code>experimentalWorkspaceModule</code> and <code>experimentalWatchedFileDelay</code> settings. The <code>experimentalPackageCacheKey</code> setting is also removed, as it is irrelevant in the new design.</p> <p>The <code>experimentalWorkspaceModule</code> setting in particular may still be in use by some users. This setting has been superseded by built-in support for multi-module workspaces in the <code>go</code> command, via <a href="https://go.dev/doc/tutorial/workspaces">Go workspaces</a>. To get the equivalent behavior in gopls@v0.12.0, please create a <code>go.work</code> file in your workspace using all desired modules. To use all modules in your workspace, run:</p> <pre><code>go work use -r . </code></pre> <h2>Dropped support for Go 1.13-1.15, deprecated support for Go 1.16-1.17</h2> <p>As announced in the <a href="https://github.com/golang/tools/releases/tag/gopls%2Fv0.10.0">v0.10.0 release notes</a>, this release drops support for Go 1.13-1.15, and in fact does not build with these Go versions.</p> <p>Additionally, <code>gopls@v0.12.x</code> will be the final sequence of versions supporting Go 1.16-1.17, and therefore displays a deprecation notice when used with these Go versions.</p> <h2>Supported operating systems</h2> <p>Given that our users are almost entirely on Linux, Windows, or Darwin, we are discussing narrowing our support to focus on those operating systems, in <a href="https://redirect.github.com/golang/go/issues/59981">golang/go#59981</a>.</p> <h1>Performance improvements</h1> <p>The banner feature of this release is an internal redesign that significantly improves the way gopls scales in larger codebases. Performance, particularly memory usage, has <a href="https://redirect.github.com/golang/go/issues/36943">long</a> <a href="https://redirect.github.com/golang/go/issues/37790">been</a> <a href="https://redirect.github.com/golang/go/issues/43968">a</a> <a href="https://redirect.github.com/golang/go/issues/44981">pain</a> <a href="https://redirect.github.com/golang/go/issues/45363">point</a> <a href="https://redirect.github.com/golang/go/issues/45457">for</a> <a href="https://redirect.github.com/golang/go/issues/46897">our</a> <a href="https://redirect.github.com/golang/go/issues/47855">users</a>.</p> <h2>Reduced memory usage</h2> <p>Previous releases of gopls held typed syntax trees for all packages, in memory, all the time. With this release, these large data structures are ephemeral: as soon as they are constructed, an index of information derived from them is saved persistently to a file-based cache, and the data structures are recycled. The index for each package includes the locations of declaring and referring identifiers; the set of exported declarations and their types; the method sets of each interface; and any diagnostics and facts (see below) produced during analysis. The index holds all the information needed to serve global-scope LSP queries such as “references”, “implementations”, and so on.</p> <p>Moving package information to a file-based cache greatly reduces the amount of RAM gopls uses, by almost an order of magnitude in larger projects. The table below shows the reductions in steady-state memory usage for three open-source Go repositories.</p> <table> <thead> <tr> <th>Project</th> <th>Packages</th> <th>In-use bytes v0.11.0</th> <th>v0.12.0</th> <th>Change</th> </tr> </thead> <tbody> <tr> <td>gopls</td> <td>405</td> <td>497MB</td> <td>232MB</td> <td>-53%</td> </tr> <tr> <td>kubernetes</td> <td>3137</td> <td>3090MB</td> <td>832MB</td> <td>-73%</td> </tr> <tr> <td>google-cloud-go + submods</td> <td>7657</td> <td>5039MB</td> <td>863MB</td> <td>-83%</td> </tr> </tbody> </table> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/golang/tools/commit/229f8486be036a365bbcaf1172d01d089ea59965"><code>229f848</code></a> gopls/internal/lsp/source: enable new defers analyzer</li> <li><a href="https://github.com/golang/tools/commit/2dc7ebab284bdfe6bb7ae8b77c3cccb0049e13ce"><code>2dc7eba</code></a> go/analysis: use parser.SkipObjectResolution</li> <li><a href="https://github.com/golang/tools/commit/f91c023a9b093f57e379f719591d5e3725e07600"><code>f91c023</code></a> go.mod: update golang.org/x dependencies</li> <li><a href="https://github.com/golang/tools/commit/e0783a89e9a456f9b64aa66717db398a20e7921d"><code>e0783a8</code></a> internal/gcimporter: remove bug report on objectpath failure</li> <li><a href="https://github.com/golang/tools/commit/75f6f9c0b004228b5a2a6f4c6a7a9719321e29bd"><code>75f6f9c</code></a> gopls/internal/bug: add gopls/bug telemetry counter</li> <li><a href="https://github.com/golang/tools/commit/4b271f9c7195c9e700572e4ea43cf1121b12e6ee"><code>4b271f9</code></a> gopls: add gopls/client telemetry counters</li> <li><a href="https://github.com/golang/tools/commit/d0b18e25a0aba0090de3d8b744fb001bf16763cf"><code>d0b18e2</code></a> go/analysis/passes/copylock: fix infinite recursion</li> <li><a href="https://github.com/golang/tools/commit/5b4d4266651c799fcd0de7475fcaf3afd7512a58"><code>5b4d426</code></a> gopls/internal/hooks: clean language version before passing to gofumpt</li> <li><a href="https://github.com/golang/tools/commit/2160c5f15ff7f02edd7dce655540bb17619ca99b"><code>2160c5f</code></a> gopls/internal/lsp/analysis: fix stubmethods with variadic parameters</li> <li><a href="https://github.com/golang/tools/commit/3d20bbe0fb2f6c3c3b340ce4d0bbcd1ad880071c"><code>3d20bbe</code></a> internal/gcimporter: add a missing return if objectpath fails</li> <li>Additional commits viewable in <a href="https://github.com/golang/tools/compare/v0.11.0...v0.12.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
Our Docker image building matrix was gigantic, which was causing long build times and build nodes to run out of disk space and memory. Cut down on the flavors we build. --- By submitting this pull request, I confirm that my contribution is made under the terms of the [Apache 2.0 license]. [Apache 2.0 license]: https://www.apache.org/licenses/LICENSE-2.0
…es/@jsii/go-runtime/jsii-runtime-go (#4221) Bumps [golang.org/x/tools](https://github.com/golang/tools) from 0.11.0 to 0.12.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/golang/tools/releases">golang.org/x/tools's releases</a>.</em></p> <blockquote> <h2>gopls/v0.12.0</h2> <p>This release contains a major rewrite of the way gopls computes and stores package information, with the goal of reducing memory usage and allowing gopls to scale to larger repositories. This change can also significantly reduce startup time when workspaces are reopened, as gopls now uses a file-based cache to persist data across sessions. With these optimizations, gopls is finally able to <a href="https://go.dev/issues/48738">fully analyze dependencies</a> using the <a href="https://pkg.go.dev/golang.org/x/tools/go/analysis">golang.org/x/tools/go/analysis</a> framework, resulting in improved accuracy for analysis diagnostics.</p> <p>You can install this release with <code>go install</code>:</p> <pre><code>go install golang.org/x/tools/gopls@v0.12.0 </code></pre> <h1>Support changes</h1> <p>As gopls matures, we're trying to simplify its configuration so that gopls Just Works in more scenarios, and so that we have fewer configuration combinations to test. This means that we will be gradually deprecating settings that affect the core behavior of gopls.</p> <h2>Removed experimental configuration options</h2> <p>As announced in the <a href="https://github.com/golang/tools/releases/tag/gopls%2Fv0.10.0">v0.10.0 release notes</a>, this release removes support for the <code>experimentalWorkspaceModule</code> and <code>experimentalWatchedFileDelay</code> settings. The <code>experimentalPackageCacheKey</code> setting is also removed, as it is irrelevant in the new design.</p> <p>The <code>experimentalWorkspaceModule</code> setting in particular may still be in use by some users. This setting has been superseded by built-in support for multi-module workspaces in the <code>go</code> command, via <a href="https://go.dev/doc/tutorial/workspaces">Go workspaces</a>. To get the equivalent behavior in gopls@v0.12.0, please create a <code>go.work</code> file in your workspace using all desired modules. To use all modules in your workspace, run:</p> <pre><code>go work use -r . </code></pre> <h2>Dropped support for Go 1.13-1.15, deprecated support for Go 1.16-1.17</h2> <p>As announced in the <a href="https://github.com/golang/tools/releases/tag/gopls%2Fv0.10.0">v0.10.0 release notes</a>, this release drops support for Go 1.13-1.15, and in fact does not build with these Go versions.</p> <p>Additionally, <code>gopls@v0.12.x</code> will be the final sequence of versions supporting Go 1.16-1.17, and therefore displays a deprecation notice when used with these Go versions.</p> <h2>Supported operating systems</h2> <p>Given that our users are almost entirely on Linux, Windows, or Darwin, we are discussing narrowing our support to focus on those operating systems, in <a href="https://redirect.github.com/golang/go/issues/59981">golang/go#59981</a>.</p> <h1>Performance improvements</h1> <p>The banner feature of this release is an internal redesign that significantly improves the way gopls scales in larger codebases. Performance, particularly memory usage, has <a href="https://redirect.github.com/golang/go/issues/36943">long</a> <a href="https://redirect.github.com/golang/go/issues/37790">been</a> <a href="https://redirect.github.com/golang/go/issues/43968">a</a> <a href="https://redirect.github.com/golang/go/issues/44981">pain</a> <a href="https://redirect.github.com/golang/go/issues/45363">point</a> <a href="https://redirect.github.com/golang/go/issues/45457">for</a> <a href="https://redirect.github.com/golang/go/issues/46897">our</a> <a href="https://redirect.github.com/golang/go/issues/47855">users</a>.</p> <h2>Reduced memory usage</h2> <p>Previous releases of gopls held typed syntax trees for all packages, in memory, all the time. With this release, these large data structures are ephemeral: as soon as they are constructed, an index of information derived from them is saved persistently to a file-based cache, and the data structures are recycled. The index for each package includes the locations of declaring and referring identifiers; the set of exported declarations and their types; the method sets of each interface; and any diagnostics and facts (see below) produced during analysis. The index holds all the information needed to serve global-scope LSP queries such as “references”, “implementations”, and so on.</p> <p>Moving package information to a file-based cache greatly reduces the amount of RAM gopls uses, by almost an order of magnitude in larger projects. The table below shows the reductions in steady-state memory usage for three open-source Go repositories.</p> <table> <thead> <tr> <th>Project</th> <th>Packages</th> <th>In-use bytes v0.11.0</th> <th>v0.12.0</th> <th>Change</th> </tr> </thead> <tbody> <tr> <td>gopls</td> <td>405</td> <td>497MB</td> <td>232MB</td> <td>-53%</td> </tr> <tr> <td>kubernetes</td> <td>3137</td> <td>3090MB</td> <td>832MB</td> <td>-73%</td> </tr> <tr> <td>google-cloud-go + submods</td> <td>7657</td> <td>5039MB</td> <td>863MB</td> <td>-83%</td> </tr> </tbody> </table> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/golang/tools/commit/229f8486be036a365bbcaf1172d01d089ea59965"><code>229f848</code></a> gopls/internal/lsp/source: enable new defers analyzer</li> <li><a href="https://github.com/golang/tools/commit/2dc7ebab284bdfe6bb7ae8b77c3cccb0049e13ce"><code>2dc7eba</code></a> go/analysis: use parser.SkipObjectResolution</li> <li><a href="https://github.com/golang/tools/commit/f91c023a9b093f57e379f719591d5e3725e07600"><code>f91c023</code></a> go.mod: update golang.org/x dependencies</li> <li><a href="https://github.com/golang/tools/commit/e0783a89e9a456f9b64aa66717db398a20e7921d"><code>e0783a8</code></a> internal/gcimporter: remove bug report on objectpath failure</li> <li><a href="https://github.com/golang/tools/commit/75f6f9c0b004228b5a2a6f4c6a7a9719321e29bd"><code>75f6f9c</code></a> gopls/internal/bug: add gopls/bug telemetry counter</li> <li><a href="https://github.com/golang/tools/commit/4b271f9c7195c9e700572e4ea43cf1121b12e6ee"><code>4b271f9</code></a> gopls: add gopls/client telemetry counters</li> <li><a href="https://github.com/golang/tools/commit/d0b18e25a0aba0090de3d8b744fb001bf16763cf"><code>d0b18e2</code></a> go/analysis/passes/copylock: fix infinite recursion</li> <li><a href="https://github.com/golang/tools/commit/5b4d4266651c799fcd0de7475fcaf3afd7512a58"><code>5b4d426</code></a> gopls/internal/hooks: clean language version before passing to gofumpt</li> <li><a href="https://github.com/golang/tools/commit/2160c5f15ff7f02edd7dce655540bb17619ca99b"><code>2160c5f</code></a> gopls/internal/lsp/analysis: fix stubmethods with variadic parameters</li> <li><a href="https://github.com/golang/tools/commit/3d20bbe0fb2f6c3c3b340ce4d0bbcd1ad880071c"><code>3d20bbe</code></a> internal/gcimporter: add a missing return if objectpath fails</li> <li>Additional commits viewable in <a href="https://github.com/golang/tools/compare/v0.11.0...v0.12.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
Bumps [aws-actions/stale-issue-cleanup](https://github.com/aws-actions/stale-issue-cleanup) from 5 to 6. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/aws-actions/stale-issue-cleanup/releases">aws-actions/stale-issue-cleanup's releases</a>.</em></p> <blockquote> <h2>v6 release</h2> <h2>What's Changed</h2> <ul> <li>build(deps-dev): bump prettier from 2.2.1 to 2.6.2 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/141">aws-actions/stale-issue-cleanup#141</a></li> <li>build(deps): bump minimist from 1.2.5 to 1.2.6 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/140">aws-actions/stale-issue-cleanup#140</a></li> <li>build(deps): bump node-fetch from 2.6.1 to 2.6.7 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/143">aws-actions/stale-issue-cleanup#143</a></li> <li>build(deps-dev): bump dotenv from 8.2.0 to 16.0.1 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/146">aws-actions/stale-issue-cleanup#146</a></li> <li>Added environment variable/argument use-created-date-for-ancient which if set to true uses issue created date instead of modified date for determining an ancient issue. by <a href="https://github.com/ashishdhingra"><code>@ashishdhingra</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/151">aws-actions/stale-issue-cleanup#151</a></li> <li>build(deps): bump minimatch from 3.0.4 to 3.1.2 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/157">aws-actions/stale-issue-cleanup#157</a></li> <li>build(deps): bump json5 from 1.0.1 to 1.0.2 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/160">aws-actions/stale-issue-cleanup#160</a></li> <li>build(deps-dev): bump eslint-plugin-import from 2.22.1 to 2.26.0 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/145">aws-actions/stale-issue-cleanup#145</a></li> <li>build(deps): bump loglevel from 1.7.1 to 1.8.1 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/162">aws-actions/stale-issue-cleanup#162</a></li> <li>build(deps): bump actions/checkout from 2 to 2.3.4 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/86">aws-actions/stale-issue-cleanup#86</a></li> <li>build(deps): bump actions/checkout from 2.3.4 to 3.3.0 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/164">aws-actions/stale-issue-cleanup#164</a></li> <li>build(deps-dev): bump eslint-plugin-promise from 4.2.1 to 6.1.1 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/156">aws-actions/stale-issue-cleanup#156</a></li> <li>build(deps-dev): bump nock from 13.1.3 to 13.3.0 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/161">aws-actions/stale-issue-cleanup#161</a></li> <li>build(deps-dev): bump eslint-plugin-prettier from 3.4.0 to 4.2.1 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/163">aws-actions/stale-issue-cleanup#163</a></li> <li>build(deps-dev): bump eslint-plugin-import from 2.26.0 to 2.27.5 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/165">aws-actions/stale-issue-cleanup#165</a></li> <li>build(deps-dev): bump eslint from 7.32.0 to 8.32.0 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/166">aws-actions/stale-issue-cleanup#166</a></li> <li>build(deps-dev): bump eslint-config-prettier from 8.3.0 to 8.6.0 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/167">aws-actions/stale-issue-cleanup#167</a></li> <li>build(deps-dev): bump dotenv from 16.0.1 to 16.0.3 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/168">aws-actions/stale-issue-cleanup#168</a></li> <li>build(deps-dev): bump prettier from 2.6.2 to 2.8.3 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/170">aws-actions/stale-issue-cleanup#170</a></li> <li>build(deps-dev): bump jest from 27.3.0 to 29.4.0 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/169">aws-actions/stale-issue-cleanup#169</a></li> <li>Updated Dockerfile to use node:18-alpine3.16 image. by <a href="https://github.com/ashishdhingra"><code>@ashishdhingra</code></a> in <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/pull/173">aws-actions/stale-issue-cleanup#173</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/aws-actions/stale-issue-cleanup/compare/v5...v6">https://github.com/aws-actions/stale-issue-cleanup/compare/v5...v6</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/7de35968489e4142233d2a6812519a82e68b5c38"><code>7de3596</code></a> Updated Dockerfile to use node:18-alpine3.16 image. (<a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/issues/173">#173</a>)</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/f914f91e45e5ad011fade57b78eca9d929d6b930"><code>f914f91</code></a> Revert "Merge pull request <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/issues/169">#169</a> from aws-actions/dependabot/npm_and_yarn/jest...</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/d862d6ce51a6f0760f9a47783bfbc6e02000b172"><code>d862d6c</code></a> Merge pull request <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/issues/169">#169</a> from aws-actions/dependabot/npm_and_yarn/jest-29.4.0</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/b5fe9d4d1e85ad85b3c008e31d453e5695282721"><code>b5fe9d4</code></a> Merge branch 'main' into dependabot/npm_and_yarn/jest-29.4.0</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/a4517fbf09ab5b2995d21135cafefe5965d2f8db"><code>a4517fb</code></a> Merge pull request <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/issues/170">#170</a> from aws-actions/dependabot/npm_and_yarn/prettier-2.8.3</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/a934980b5b0c4e8e880931f51af2bacf962afc45"><code>a934980</code></a> build(deps-dev): bump jest from 27.3.0 to 29.4.0</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/ff03a0b6f15c9c4b00a4cd68ee35b39cfdac19dc"><code>ff03a0b</code></a> Merge branch 'main' into dependabot/npm_and_yarn/prettier-2.8.3</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/2f0c6c4255e4a1e877391bbb3b79dea8d50aec3b"><code>2f0c6c4</code></a> Merge pull request <a href="https://redirect.github.com/aws-actions/stale-issue-cleanup/issues/168">#168</a> from aws-actions/dependabot/npm_and_yarn/dotenv-16.0.3</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/047f077be8dce43edfb933481a7333ae50b34354"><code>047f077</code></a> build(deps-dev): bump prettier from 2.6.2 to 2.8.3</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/483cae46c42862743c95419f2e7516ec007e8c6b"><code>483cae4</code></a> build(deps-dev): bump dotenv from 16.0.1 to 16.0.3</li> <li>Additional commits viewable in <a href="https://github.com/aws-actions/stale-issue-cleanup/compare/v5...v6">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
This was erroneously deleted and is necessary because we want the `ssh-keyscan` command. Added: f95f88c Deleted: https://github.com/aws/jsii/pull/4219/files ``` /codebuild/output/tmp/script.sh: ssh-keyscan: not found ``` At least I think this is the solution because stack overflow tells me that `openssh-client` has `ssh-keyscan`: https://stackoverflow.com/questions/32665746/ssh-keyscan-not-found-in-dockerfile --- By submitting this pull request, I confirm that my contribution is made under the terms of the [Apache 2.0 license]. [Apache 2.0 license]: https://www.apache.org/licenses/LICENSE-2.0
aws-cdk-automation
added
the
pr/no-squash
rix0rrr
approved these changes
Aug 11, 2023
|
Thank you for contributing! ❤️ I will now look into making sure the PR is up-to-date, then proceed to try and merge it! |
|
Merging (no-squash)... |
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.
See CHANGELOG