Skip to content

chore(release): 2.208.0 #35099

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 20 commits into from
Jul 29, 2025
Merged

chore(release): 2.208.0 #35099

merged 20 commits into from
Jul 29, 2025

Conversation

@aws-cdk-automation
Copy link
Collaborator

@aws-cdk-automation aws-cdk-automation commented Jul 29, 2025 •
edited
Loading

See CHANGELOG

Abogical and others added 17 commits July 24, 2025 12:34
@Abogical
ci: re-add tool to sync with project board with build fixes (#34823)
84e875a 
### Reason for this change

Note: this re-adds the tool introduced in #34776 with build fixes.

Adds a tool to sync issue metadata with project board. Github currently [does not support](https://github.com/orgs/community/discussions/5953#discussioncomment-13251662) filtering and sorting by creation and update date.

### Description of changes

Adds a GH Action to update and fill those issue metadata on the project board. Metadata includes Creation and update date.

### Describe any new or updated permissions being added

N/A.

### Description of how you validated changes

Unit tests added. Verified Action runs successfully on local fork [here](https://github.com/Abogical/aws-cdk/actions/runs/15898935881/job/44837087761).

### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@ozelalisen
chore(deps): upgrade axios version to 1.11.0 (#35037)
4373976 
### Issue # (if applicable)

Closes Dependabot alerts: [419](https://github.com/aws/aws-cdk/security/dependabot/419), [495](https://github.com/aws/aws-cdk/security/dependabot/495), [496](https://github.com/aws/aws-cdk/security/dependabot/496)

### Reason for this change

There are security issues with axios versions detected by dependabot. 

### Description of changes



- Upgraded axios versions
- Added _package.json for pnpm to make the updates for the future easier. 


### Describe any new or updated permissions being added



- None

### Description of how you validated changes



- Build the package 

### Checklist
- [X] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@dependabot
chore(deps): bump the npm_and_yarn group across 4 directories with 3 …
d996227 
…updates (#35056)

Bumps the npm_and_yarn group with 2 updates in the / directory: [esbuild](https://github.com/evanw/esbuild) and [axios](https://github.com/axios/axios).
Bumps the npm_and_yarn group with 1 update in the /packages/@aws-cdk-testing/framework-integ directory: [axios](https://github.com/axios/axios).
Bumps the npm_and_yarn group with 1 update in the /tools/@aws-cdk/construct-metadata-updater directory: [esbuild](https://github.com/evanw/esbuild).
Bumps the npm_and_yarn group with 1 update in the /tools/@aws-cdk/enum-updater directory: [esbuild](https://github.com/evanw/esbuild).

Updates `esbuild` from 0.24.2 to 0.25.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/evanw/esbuild/releases">esbuild's releases</a>.</em></p>
<blockquote>
<h2>v0.25.0</h2>
<p><strong>This release deliberately contains backwards-incompatible changes.</strong> To avoid automatically picking up releases like this, you should either be pinning the exact version of <code>esbuild</code> in your <code>package.json</code> file (recommended) or be using a version range syntax that only accepts patch upgrades such as <code>^0.24.0</code> or <code>~0.24.0</code>. See npm's documentation about <a href="https://docs.npmjs.com/cli/v6/using-npm/semver/">semver</a> for more information.</p>
<ul>
<li>
<p>Restrict access to esbuild's development server (<a href="https://github.com/evanw/esbuild/security/advisories/GHSA-67mh-4wv8-2f99">GHSA-67mh-4wv8-2f99</a>)</p>
<p>This change addresses esbuild's first security vulnerability report. Previously esbuild set the <code>Access-Control-Allow-Origin</code> header to <code>*</code> to allow esbuild's development server to be flexible in how it's used for development. However, this allows the websites you visit to make HTTP requests to esbuild's local development server, which gives read-only access to your source code if the website were to fetch your source code's specific URL. You can read more information in <a href="https://github.com/evanw/esbuild/security/advisories/GHSA-67mh-4wv8-2f99">the report</a>.</p>
<p>Starting with this release, <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS">CORS</a> will now be disabled, and requests will now be denied if the host does not match the one provided to <code>--serve=</code>. The default host is <code>0.0.0.0</code>, which refers to all of the IP addresses that represent the local machine (e.g. both <code>127.0.0.1</code> and <code>192.168.0.1</code>). If you want to customize anything about esbuild's development server, you can <a href="https://esbuild.github.io/api/#serve-proxy">put a proxy in front of esbuild</a> and modify the incoming and/or outgoing requests.</p>
<p>In addition, the <code>serve()</code> API call has been changed to return an array of <code>hosts</code> instead of a single <code>host</code> string. This makes it possible to determine all of the hosts that esbuild's development server will accept.</p>
<p>Thanks to <a href="https://github.com/sapphi-red"><code>@​sapphi-red</code></a> for reporting this issue.</p>
</li>
<li>
<p>Delete output files when a build fails in watch mode (<a href="https://redirect.github.com/evanw/esbuild/issues/3643">#3643</a>)</p>
<p>It has been requested for esbuild to delete files when a build fails in watch mode. Previously esbuild left the old files in place, which could cause people to not immediately realize that the most recent build failed. With this release, esbuild will now delete all output files if a rebuild fails. Fixing the build error and triggering another rebuild will restore all output files again.</p>
</li>
<li>
<p>Fix correctness issues with the CSS nesting transform (<a href="https://redirect.github.com/evanw/esbuild/issues/3620">#3620</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3877">#3877</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3933">#3933</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3997">#3997</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/4005">#4005</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4037">#4037</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4038">#4038</a>)</p>
<p>This release fixes the following problems:</p>
<ul>
<li>
<p>Naive expansion of CSS nesting can result in an exponential blow-up of generated CSS if each nesting level has multiple selectors. Previously esbuild sometimes collapsed individual nesting levels using <code>:is()</code> to limit expansion. However, this collapsing wasn't correct in some cases, so it has been removed to fix correctness issues.</p>
<pre lang="css"><code>/* Original code */
.parent {
  &gt; .a,
  &gt; .b1 &gt; .b2 {
    color: red;
  }
}
<p>/* Old output (with --supported:nesting=false) */<br />
.parent &gt; :is(.a, .b1 &gt; .b2) {<br />
color: red;<br />
}</p>
<p>/* New output (with --supported:nesting=false) */<br />
.parent &gt; .a,<br />
.parent &gt; .b1 &gt; .b2 {<br />
color: red;<br />
}<br />
</code></pre></p>
<p>Thanks to <a href="https://github.com/tim-we"><code>@​tim-we</code></a> for working on a fix.</p>
</li>
<li>
<p>The <code>&amp;</code> CSS nesting selector can be repeated multiple times to increase CSS specificity. Previously esbuild ignored this possibility and incorrectly considered <code>&amp;&amp;</code> to have the same specificity as <code>&amp;</code>. With this release, this should now work correctly:</p>
<pre lang="css"><code>/* Original code (color should be red) */
</code></pre>
</li>
</ul>
</li>
</ul>

</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md">esbuild's changelog</a>.</em></p>
<blockquote>
<h1>Changelog: 2024</h1>
<p>This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).</p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/evanw/esbuild/commit/e9174d671b1882758cd32ac5e146200f5bee3e45"><code>e9174d6</code></a> publish 0.25.0 to npm</li>
<li><a href="https://github.com/evanw/esbuild/commit/c27dbebb9e7a55dd9a084dd151dddd840787490e"><code>c27dbeb</code></a> fix <code>hosts</code> in <code>plugin-tests.js</code></li>
<li><a href="https://github.com/evanw/esbuild/commit/6794f602a453cf0255bcae245871de120a89a559"><code>6794f60</code></a> fix <code>hosts</code> in <code>node-unref-tests.js</code></li>
<li><a href="https://github.com/evanw/esbuild/commit/de85afd65edec9ebc44a11e245fd9e9a2e99760d"><code>de85afd</code></a> Merge commit from fork</li>
<li><a href="https://github.com/evanw/esbuild/commit/da1de1bf77a65f06654b49878d9ec4747ddaa21f"><code>da1de1b</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4065">#4065</a>: bitwise operators can return bigints</li>
<li><a href="https://github.com/evanw/esbuild/commit/f4e9d19fb20095a98bf40634f0380f6a16be91e7"><code>f4e9d19</code></a> switch case liveness: <code>default</code> is always last</li>
<li><a href="https://github.com/evanw/esbuild/commit/7aa47c3e778ea04849f97f18dd9959df88fa0886"><code>7aa47c3</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4028">#4028</a>: minify live/dead <code>switch</code> cases better</li>
<li><a href="https://github.com/evanw/esbuild/commit/22ecd306190b8971ec4474b5485266c20350e266"><code>22ecd30</code></a> minify: more constant folding for strict equality</li>
<li><a href="https://github.com/evanw/esbuild/commit/4cdf03c03697128044fa8fb76e5c478e9765b353"><code>4cdf03c</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4053">#4053</a>: reordering of <code>.tsx</code> in <code>node_modules</code></li>
<li><a href="https://github.com/evanw/esbuild/commit/dc719775b7140120916bd9e6777ca1cb8a1cdc0e"><code>dc71977</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/3692">#3692</a>: <code>0</code> now picks a random ephemeral port</li>
<li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.24.2...v0.25.0">compare view</a></li>
</ul>
</details>
<br />

Updates `axios` from 1.10.0 to 1.11.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/axios/axios/releases">axios's releases</a>.</em></p>
<blockquote>
<h2>Release v1.11.0</h2>
<h2>Release notes:</h2>
<h3>Bug Fixes</h3>
<ul>
<li>form-data npm pakcage (<a href="https://redirect.github.com/axios/axios/issues/6970">#6970</a>) (<a href="https://github.com/axios/axios/commit/e72c193722530db538b19e5ddaaa4544d226b253">e72c193</a>)</li>
<li>prevent RangeError when using large Buffers (<a href="https://redirect.github.com/axios/axios/issues/6961">#6961</a>) (<a href="https://github.com/axios/axios/commit/a2214ca1bc60540baf2c80573cea3a0ff91ba9d1">a2214ca</a>)</li>
<li><strong>types:</strong> resolve type discrepancies between ESM and CJS TypeScript declaration files (<a href="https://redirect.github.com/axios/axios/issues/6956">#6956</a>) (<a href="https://github.com/axios/axios/commit/8517aa16f8d082fc1d5309c642220fa736159110">8517aa1</a>)</li>
</ul>
<h3>Contributors to this release</h3>
<ul>
<li> <a href="https://github.com/izzygld" title="+186/-93 ([#6970](axios/axios#6970) )">izzy goldman</a></li>
<li> <a href="https://github.com/manishsahanidev" title="+70/-0 ([#6961](axios/axios#6961) )">Manish Sahani</a></li>
<li> <a href="https://github.com/noritaka1166" title="+12/-10 ([#6938](axios/axios#6938) [#6939](axios/axios#6939) )">Noritaka Kobayashi</a></li>
<li> <a href="https://github.com/jrnail23" title="+13/-2 ([#6956](axios/axios#6956) )">James Nail</a></li>
<li> <a href="https://github.com/Tejaswi1305" title="+1/-1 ([#6894](axios/axios#6894) )">Tejaswi1305</a></li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/axios/axios/blob/v1.x/CHANGELOG.md">axios's changelog</a>.</em></p>
<blockquote>
<h1><a href="https://github.com/axios/axios/compare/v1.10.0...v1.11.0">1.11.0</a> (2025-07-22)</h1>
<h3>Bug Fixes</h3>
<ul>
<li>form-data npm pakcage (<a href="https://redirect.github.com/axios/axios/issues/6970">#6970</a>) (<a href="https://github.com/axios/axios/commit/e72c193722530db538b19e5ddaaa4544d226b253">e72c193</a>)</li>
<li>prevent RangeError when using large Buffers (<a href="https://redirect.github.com/axios/axios/issues/6961">#6961</a>) (<a href="https://github.com/axios/axios/commit/a2214ca1bc60540baf2c80573cea3a0ff91ba9d1">a2214ca</a>)</li>
<li><strong>types:</strong> resolve type discrepancies between ESM and CJS TypeScript declaration files (<a href="https://redirect.github.com/axios/axios/issues/6956">#6956</a>) (<a href="https://github.com/axios/axios/commit/8517aa16f8d082fc1d5309c642220fa736159110">8517aa1</a>)</li>
</ul>
<h3>Contributors to this release</h3>
<ul>
<li> <a href="https://github.com/izzygld" title="+186/-93 ([#6970](axios/axios#6970) )">izzy goldman</a></li>
<li> <a href="https://github.com/manishsahanidev" title="+70/-0 ([#6961](axios/axios#6961) )">Manish Sahani</a></li>
<li> <a href="https://github.com/noritaka1166" title="+12/-10 ([#6938](axios/axios#6938) [#6939](axios/axios#6939) )">Noritaka Kobayashi</a></li>
<li> <a href="https://github.com/jrnail23" title="+13/-2 ([#6956](axios/axios#6956) )">James Nail</a></li>
<li> <a href="https://github.com/Tejaswi1305" title="+1/-1 ([#6894](axios/axios#6894) )">Tejaswi1305</a></li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/axios/axios/commit/b76c4ac6f871141dd011a21f3b7ca4e66bfc33ae"><code>b76c4ac</code></a> chore(release): v1.11.0 (<a href="https://redirect.github.com/axios/axios/issues/6974">#6974</a>)</li>
<li><a href="https://github.com/axios/axios/commit/e72c193722530db538b19e5ddaaa4544d226b253"><code>e72c193</code></a> fix: form-data npm pakcage (<a href="https://redirect.github.com/axios/axios/issues/6970">#6970</a>)</li>
<li><a href="https://github.com/axios/axios/commit/8517aa16f8d082fc1d5309c642220fa736159110"><code>8517aa1</code></a> fix(types): resolve type discrepancies between ESM and CJS TypeScript declara...</li>
<li><a href="https://github.com/axios/axios/commit/a2214ca1bc60540baf2c80573cea3a0ff91ba9d1"><code>a2214ca</code></a> fix: prevent RangeError when using large Buffers (<a href="https://redirect.github.com/axios/axios/issues/6961">#6961</a>)</li>
<li><a href="https://github.com/axios/axios/commit/6161947d9d3496ae75909a2ded98fa43ecb7e572"><code>6161947</code></a> refactor: use spread operator instead of '.apply()' (<a href="https://redirect.github.com/axios/axios/issues/6938">#6938</a>)</li>
<li><a href="https://github.com/axios/axios/commit/a1d16dd9c59af11abd687b42bbeab1d50d01654e"><code>a1d16dd</code></a> refactor: use an object spread instead of Object.assign (<a href="https://redirect.github.com/axios/axios/issues/6939">#6939</a>)</li>
<li><a href="https://github.com/axios/axios/commit/07183cd1496737dcd10d7241b66fa6d6a55c2aed"><code>07183cd</code></a> chore(sponsor): update sponsor block (<a href="https://redirect.github.com/axios/axios/issues/6952">#6952</a>)</li>
<li><a href="https://github.com/axios/axios/commit/ef36347fb559383b04c755b07f1a8d11897fab7f"><code>ef36347</code></a> docs(CONTRIBUTING): update docs link for accuracy (<a href="https://redirect.github.com/axios/axios/issues/6894">#6894</a>)</li>
<li><a href="https://github.com/axios/axios/commit/b29bd6a64121f9e6b7c7026b96fbe64df3cf7e0b"><code>b29bd6a</code></a> chore(sponsor): update sponsor block (<a href="https://redirect.github.com/axios/axios/issues/6948">#6948</a>)</li>
<li><a href="https://github.com/axios/axios/commit/a406a93e2d99c3317596f02f3537f5457a2a80fd"><code>a406a93</code></a> chore(sponsor): update sponsor block (<a href="https://redirect.github.com/axios/axios/issues/6937">#6937</a>)</li>
<li>See full diff in <a href="https://github.com/axios/axios/compare/v1.10.0...v1.11.0">compare view</a></li>
</ul>
</details>
<br />

Updates `form-data` from 4.0.3 to 4.0.4
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/form-data/form-data/blob/master/CHANGELOG.md">form-data's changelog</a>.</em></p>
<blockquote>
<h2><a href="https://github.com/form-data/form-data/compare/v4.0.3...v4.0.4">v4.0.4</a> - 2025-07-16</h2>
<h3>Commits</h3>
<ul>
<li>[meta] add <code>auto-changelog</code> <a href="https://github.com/form-data/form-data/commit/811f68282fab0315209d0e2d1c44b6c32ea0d479"><code>811f682</code></a></li>
<li>[Tests] handle predict-v8-randomness failures in node &lt; 17 and node &gt; 23 <a href="https://github.com/form-data/form-data/commit/1d11a76434d101f22fdb26b8aef8615f28b98402"><code>1d11a76</code></a></li>
<li>[Fix] Switch to using <code>crypto</code> random for boundary values <a href="https://github.com/form-data/form-data/commit/3d1723080e6577a66f17f163ecd345a21d8d0fd0"><code>3d17230</code></a></li>
<li>[Tests] fix linting errors <a href="https://github.com/form-data/form-data/commit/5e340800b5f8914213e4e0378c084aae71cfd73a"><code>5e34080</code></a></li>
<li>[meta] actually ensure the readme backup isn’t published <a href="https://github.com/form-data/form-data/commit/316c82ba93fd4985af757b771b9a1f26d3b709ef"><code>316c82b</code></a></li>
<li>[Dev Deps] update <code>@ljharb/eslint-config</code> <a href="https://github.com/form-data/form-data/commit/58c25d76406a5b0dfdf54045cf252563f2bbda8d"><code>58c25d7</code></a></li>
<li>[meta] fix readme capitalization <a href="https://github.com/form-data/form-data/commit/2300ca19595b0ee96431e868fe2a40db79e41c61"><code>2300ca1</code></a></li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/form-data/form-data/commit/41996f5ac73a867046d48512cab62e64fc846dad"><code>41996f5</code></a> v4.0.4</li>
<li><a href="https://github.com/form-data/form-data/commit/316c82ba93fd4985af757b771b9a1f26d3b709ef"><code>316c82b</code></a> [meta] actually ensure the readme backup isn’t published</li>
<li><a href="https://github.com/form-data/form-data/commit/2300ca19595b0ee96431e868fe2a40db79e41c61"><code>2300ca1</code></a> [meta] fix readme capitalization</li>
<li><a href="https://github.com/form-data/form-data/commit/811f68282fab0315209d0e2d1c44b6c32ea0d479"><code>811f682</code></a> [meta] add <code>auto-changelog</code></li>
<li><a href="https://github.com/form-data/form-data/commit/5e340800b5f8914213e4e0378c084aae71cfd73a"><code>5e34080</code></a> [Tests] fix linting errors</li>
<li><a href="https://github.com/form-data/form-data/commit/1d11a76434d101f22fdb26b8aef8615f28b98402"><code>1d11a76</code></a> [Tests] handle predict-v8-randomness failures in node &lt; 17 and node &gt; 23</li>
<li><a href="https://github.com/form-data/form-data/commit/58c25d76406a5b0dfdf54045cf252563f2bbda8d"><code>58c25d7</code></a> [Dev Deps] update <code>@ljharb/eslint-config</code></li>
<li><a href="https://github.com/form-data/form-data/commit/3d1723080e6577a66f17f163ecd345a21d8d0fd0"><code>3d17230</code></a> [Fix] Switch to using <code>crypto</code> random for boundary values</li>
<li>See full diff in <a href="https://github.com/form-data/form-data/compare/v4.0.3...v4.0.4">compare view</a></li>
</ul>
</details>
<br />

Updates `axios` from 1.10.0 to 1.11.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/axios/axios/releases">axios's releases</a>.</em></p>
<blockquote>
<h2>Release v1.11.0</h2>
<h2>Release notes:</h2>
<h3>Bug Fixes</h3>
<ul>
<li>form-data npm pakcage (<a href="https://redirect.github.com/axios/axios/issues/6970">#6970</a>) (<a href="https://github.com/axios/axios/commit/e72c193722530db538b19e5ddaaa4544d226b253">e72c193</a>)</li>
<li>prevent RangeError when using large Buffers (<a href="https://redirect.github.com/axios/axios/issues/6961">#6961</a>) (<a href="https://github.com/axios/axios/commit/a2214ca1bc60540baf2c80573cea3a0ff91ba9d1">a2214ca</a>)</li>
<li><strong>types:</strong> resolve type discrepancies between ESM and CJS TypeScript declaration files (<a href="https://redirect.github.com/axios/axios/issues/6956">#6956</a>) (<a href="https://github.com/axios/axios/commit/8517aa16f8d082fc1d5309c642220fa736159110">8517aa1</a>)</li>
</ul>
<h3>Contributors to this release</h3>
<ul>
<li> <a href="https://github.com/izzygld" title="+186/-93 ([#6970](axios/axios#6970) )">izzy goldman</a></li>
<li> <a href="https://github.com/manishsahanidev" title="+70/-0 ([#6961](axios/axios#6961) )">Manish Sahani</a></li>
<li> <a href="https://github.com/noritaka1166" title="+12/-10 ([#6938](axios/axios#6938) [#6939](axios/axios#6939) )">Noritaka Kobayashi</a></li>
<li> <a href="https://github.com/jrnail23" title="+13/-2 ([#6956](axios/axios#6956) )">James Nail</a></li>
<li> <a href="https://github.com/Tejaswi1305" title="+1/-1 ([#6894](axios/axios#6894) )">Tejaswi1305</a></li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/axios/axios/blob/v1.x/CHANGELOG.md">axios's changelog</a>.</em></p>
<blockquote>
<h1><a href="https://github.com/axios/axios/compare/v1.10.0...v1.11.0">1.11.0</a> (2025-07-22)</h1>
<h3>Bug Fixes</h3>
<ul>
<li>form-data npm pakcage (<a href="https://redirect.github.com/axios/axios/issues/6970">#6970</a>) (<a href="https://github.com/axios/axios/commit/e72c193722530db538b19e5ddaaa4544d226b253">e72c193</a>)</li>
<li>prevent RangeError when using large Buffers (<a href="https://redirect.github.com/axios/axios/issues/6961">#6961</a>) (<a href="https://github.com/axios/axios/commit/a2214ca1bc60540baf2c80573cea3a0ff91ba9d1">a2214ca</a>)</li>
<li><strong>types:</strong> resolve type discrepancies between ESM and CJS TypeScript declaration files (<a href="https://redirect.github.com/axios/axios/issues/6956">#6956</a>) (<a href="https://github.com/axios/axios/commit/8517aa16f8d082fc1d5309c642220fa736159110">8517aa1</a>)</li>
</ul>
<h3>Contributors to this release</h3>
<ul>
<li> <a href="https://github.com/izzygld" title="+186/-93 ([#6970](axios/axios#6970) )">izzy goldman</a></li>
<li> <a href="https://github.com/manishsahanidev" title="+70/-0 ([#6961](axios/axios#6961) )">Manish Sahani</a></li>
<li> <a href="https://github.com/noritaka1166" title="+12/-10 ([#6938](axios/axios#6938) [#6939](axios/axios#6939) )">Noritaka Kobayashi</a></li>
<li> <a href="https://github.com/jrnail23" title="+13/-2 ([#6956](axios/axios#6956) )">James Nail</a></li>
<li> <a href="https://github.com/Tejaswi1305" title="+1/-1 ([#6894](axios/axios#6894) )">Tejaswi1305</a></li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/axios/axios/commit/b76c4ac6f871141dd011a21f3b7ca4e66bfc33ae"><code>b76c4ac</code></a> chore(release): v1.11.0 (<a href="https://redirect.github.com/axios/axios/issues/6974">#6974</a>)</li>
<li><a href="https://github.com/axios/axios/commit/e72c193722530db538b19e5ddaaa4544d226b253"><code>e72c193</code></a> fix: form-data npm pakcage (<a href="https://redirect.github.com/axios/axios/issues/6970">#6970</a>)</li>
<li><a href="https://github.com/axios/axios/commit/8517aa16f8d082fc1d5309c642220fa736159110"><code>8517aa1</code></a> fix(types): resolve type discrepancies between ESM and CJS TypeScript declara...</li>
<li><a href="https://github.com/axios/axios/commit/a2214ca1bc60540baf2c80573cea3a0ff91ba9d1"><code>a2214ca</code></a> fix: prevent RangeError when using large Buffers (<a href="https://redirect.github.com/axios/axios/issues/6961">#6961</a>)</li>
<li><a href="https://github.com/axios/axios/commit/6161947d9d3496ae75909a2ded98fa43ecb7e572"><code>6161947</code></a> refactor: use spread operator instead of '.apply()' (<a href="https://redirect.github.com/axios/axios/issues/6938">#6938</a>)</li>
<li><a href="https://github.com/axios/axios/commit/a1d16dd9c59af11abd687b42bbeab1d50d01654e"><code>a1d16dd</code></a> refactor: use an object spread instead of Object.assign (<a href="https://redirect.github.com/axios/axios/issues/6939">#6939</a>)</li>
<li><a href="https://github.com/axios/axios/commit/07183cd1496737dcd10d7241b66fa6d6a55c2aed"><code>07183cd</code></a> chore(sponsor): update sponsor block (<a href="https://redirect.github.com/axios/axios/issues/6952">#6952</a>)</li>
<li><a href="https://github.com/axios/axios/commit/ef36347fb559383b04c755b07f1a8d11897fab7f"><code>ef36347</code></a> docs(CONTRIBUTING): update docs link for accuracy (<a href="https://redirect.github.com/axios/axios/issues/6894">#6894</a>)</li>
<li><a href="https://github.com/axios/axios/commit/b29bd6a64121f9e6b7c7026b96fbe64df3cf7e0b"><code>b29bd6a</code></a> chore(sponsor): update sponsor block (<a href="https://redirect.github.com/axios/axios/issues/6948">#6948</a>)</li>
<li><a href="https://github.com/axios/axios/commit/a406a93e2d99c3317596f02f3537f5457a2a80fd"><code>a406a93</code></a> chore(sponsor): update sponsor block (<a href="https://redirect.github.com/axios/axios/issues/6937">#6937</a>)</li>
<li>See full diff in <a href="https://github.com/axios/axios/compare/v1.10.0...v1.11.0">compare view</a></li>
</ul>
</details>
<br />

Updates `esbuild` from 0.24.2 to 0.25.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/evanw/esbuild/releases">esbuild's releases</a>.</em></p>
<blockquote>
<h2>v0.25.0</h2>
<p><strong>This release deliberately contains backwards-incompatible changes.</strong> To avoid automatically picking up releases like this, you should either be pinning the exact version of <code>esbuild</code> in your <code>package.json</code> file (recommended) or be using a version range syntax that only accepts patch upgrades such as <code>^0.24.0</code> or <code>~0.24.0</code>. See npm's documentation about <a href="https://docs.npmjs.com/cli/v6/using-npm/semver/">semver</a> for more information.</p>
<ul>
<li>
<p>Restrict access to esbuild's development server (<a href="https://github.com/evanw/esbuild/security/advisories/GHSA-67mh-4wv8-2f99">GHSA-67mh-4wv8-2f99</a>)</p>
<p>This change addresses esbuild's first security vulnerability report. Previously esbuild set the <code>Access-Control-Allow-Origin</code> header to <code>*</code> to allow esbuild's development server to be flexible in how it's used for development. However, this allows the websites you visit to make HTTP requests to esbuild's local development server, which gives read-only access to your source code if the website were to fetch your source code's specific URL. You can read more information in <a href="https://github.com/evanw/esbuild/security/advisories/GHSA-67mh-4wv8-2f99">the report</a>.</p>
<p>Starting with this release, <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS">CORS</a> will now be disabled, and requests will now be denied if the host does not match the one provided to <code>--serve=</code>. The default host is <code>0.0.0.0</code>, which refers to all of the IP addresses that represent the local machine (e.g. both <code>127.0.0.1</code> and <code>192.168.0.1</code>). If you want to customize anything about esbuild's development server, you can <a href="https://esbuild.github.io/api/#serve-proxy">put a proxy in front of esbuild</a> and modify the incoming and/or outgoing requests.</p>
<p>In addition, the <code>serve()</code> API call has been changed to return an array of <code>hosts</code> instead of a single <code>host</code> string. This makes it possible to determine all of the hosts that esbuild's development server will accept.</p>
<p>Thanks to <a href="https://github.com/sapphi-red"><code>@​sapphi-red</code></a> for reporting this issue.</p>
</li>
<li>
<p>Delete output files when a build fails in watch mode (<a href="https://redirect.github.com/evanw/esbuild/issues/3643">#3643</a>)</p>
<p>It has been requested for esbuild to delete files when a build fails in watch mode. Previously esbuild left the old files in place, which could cause people to not immediately realize that the most recent build failed. With this release, esbuild will now delete all output files if a rebuild fails. Fixing the build error and triggering another rebuild will restore all output files again.</p>
</li>
<li>
<p>Fix correctness issues with the CSS nesting transform (<a href="https://redirect.github.com/evanw/esbuild/issues/3620">#3620</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3877">#3877</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3933">#3933</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3997">#3997</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/4005">#4005</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4037">#4037</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4038">#4038</a>)</p>
<p>This release fixes the following problems:</p>
<ul>
<li>
<p>Naive expansion of CSS nesting can result in an exponential blow-up of generated CSS if each nesting level has multiple selectors. Previously esbuild sometimes collapsed individual nesting levels using <code>:is()</code> to limit expansion. However, this collapsing wasn't correct in some cases, so it has been removed to fix correctness issues.</p>
<pre lang="css"><code>/* Original code */
.parent {
  &gt; .a,
  &gt; .b1 &gt; .b2 {
    color: red;
  }
}
<p>/* Old output (with --supported:nesting=false) */<br />
.parent &gt; :is(.a, .b1 &gt; .b2) {<br />
color: red;<br />
}</p>
<p>/* New output (with --supported:nesting=false) */<br />
.parent &gt; .a,<br />
.parent &gt; .b1 &gt; .b2 {<br />
color: red;<br />
}<br />
</code></pre></p>
<p>Thanks to <a href="https://github.com/tim-we"><code>@​tim-we</code></a> for working on a fix.</p>
</li>
<li>
<p>The <code>&amp;</code> CSS nesting selector can be repeated multiple times to increase CSS specificity. Previously esbuild ignored this possibility and incorrectly considered <code>&amp;&amp;</code> to have the same specificity as <code>&amp;</code>. With this release, this should now work correctly:</p>
<pre lang="css"><code>/* Original code (color should be red) */
</code></pre>
</li>
</ul>
</li>
</ul>

</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md">esbuild's changelog</a>.</em></p>
<blockquote>
<h1>Changelog: 2024</h1>
<p>This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).</p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/evanw/esbuild/commit/e9174d671b1882758cd32ac5e146200f5bee3e45"><code>e9174d6</code></a> publish 0.25.0 to npm</li>
<li><a href="https://github.com/evanw/esbuild/commit/c27dbebb9e7a55dd9a084dd151dddd840787490e"><code>c27dbeb</code></a> fix <code>hosts</code> in <code>plugin-tests.js</code></li>
<li><a href="https://github.com/evanw/esbuild/commit/6794f602a453cf0255bcae245871de120a89a559"><code>6794f60</code></a> fix <code>hosts</code> in <code>node-unref-tests.js</code></li>
<li><a href="https://github.com/evanw/esbuild/commit/de85afd65edec9ebc44a11e245fd9e9a2e99760d"><code>de85afd</code></a> Merge commit from fork</li>
<li><a href="https://github.com/evanw/esbuild/commit/da1de1bf77a65f06654b49878d9ec4747ddaa21f"><code>da1de1b</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4065">#4065</a>: bitwise operators can return bigints</li>
<li><a href="https://github.com/evanw/esbuild/commit/f4e9d19fb20095a98bf40634f0380f6a16be91e7"><code>f4e9d19</code></a> switch case liveness: <code>default</code> is always last</li>
<li><a href="https://github.com/evanw/esbuild/commit/7aa47c3e778ea04849f97f18dd9959df88fa0886"><code>7aa47c3</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4028">#4028</a>: minify live/dead <code>switch</code> cases better</li>
<li><a href="https://github.com/evanw/esbuild/commit/22ecd306190b8971ec4474b5485266c20350e266"><code>22ecd30</code></a> minify: more constant folding for strict equality</li>
<li><a href="https://github.com/evanw/esbuild/commit/4cdf03c03697128044fa8fb76e5c478e9765b353"><code>4cdf03c</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4053">#4053</a>: reordering of <code>.tsx</code> in <code>node_modules</code></li>
<li><a href="https://github.com/evanw/esbuild/commit/dc719775b7140120916bd9e6777ca1cb8a1cdc0e"><code>dc71977</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/3692">#3692</a>: <code>0</code> now picks a random ephemeral port</li>
<li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.24.2...v0.25.0">compare view</a></li>
</ul>
</details>
<br />

Updates `esbuild` from 0.25.0 to 0.25.8
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/evanw/esbuild/releases">esbuild's releases</a>.</em></p>
<blockquote>
<h2>v0.25.0</h2>
<p><strong>This release deliberately contains backwards-incompatible changes.</strong> To avoid automatically picking up releases like this, you should either be pinning the exact version of <code>esbuild</code> in your <code>package.json</code> file (recommended) or be using a version range syntax that only accepts patch upgrades such as <code>^0.24.0</code> or <code>~0.24.0</code>. See npm's documentation about <a href="https://docs.npmjs.com/cli/v6/using-npm/semver/">semver</a> for more information.</p>
<ul>
<li>
<p>Restrict access to esbuild's development server (<a href="https://github.com/evanw/esbuild/security/advisories/GHSA-67mh-4wv8-2f99">GHSA-67mh-4wv8-2f99</a>)</p>
<p>This change addresses esbuild's first security vulnerability report. Previously esbuild set the <code>Access-Control-Allow-Origin</code> header to <code>*</code> to allow esbuild's development server to be flexible in how it's used for development. However, this allows the websites you visit to make HTTP requests to esbuild's local development server, which gives read-only access to your source code if the website were to fetch your source code's specific URL. You can read more information in <a href="https://github.com/evanw/esbuild/security/advisories/GHSA-67mh-4wv8-2f99">the report</a>.</p>
<p>Starting with this release, <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS">CORS</a> will now be disabled, and requests will now be denied if the host does not match the one provided to <code>--serve=</code>. The default host is <code>0.0.0.0</code>, which refers to all of the IP addresses that represent the local machine (e.g. both <code>127.0.0.1</code> and <code>192.168.0.1</code>). If you want to customize anything about esbuild's development server, you can <a href="https://esbuild.github.io/api/#serve-proxy">put a proxy in front of esbuild</a> and modify the incoming and/or outgoing requests.</p>
<p>In addition, the <code>serve()</code> API call has been changed to return an array of <code>hosts</code> instead of a single <code>host</code> string. This makes it possible to determine all of the hosts that esbuild's development server will accept.</p>
<p>Thanks to <a href="https://github.com/sapphi-red"><code>@​sapphi-red</code></a> for reporting this issue.</p>
</li>
<li>
<p>Delete output files when a build fails in watch mode (<a href="https://redirect.github.com/evanw/esbuild/issues/3643">#3643</a>)</p>
<p>It has been requested for esbuild to delete files when a build fails in watch mode. Previously esbuild left the old files in place, which could cause people to not immediately realize that the most recent build failed. With this release, esbuild will now delete all output files if a rebuild fails. Fixing the build error and triggering another rebuild will restore all output files again.</p>
</li>
<li>
<p>Fix correctness issues with the CSS nesting transform (<a href="https://redirect.github.com/evanw/esbuild/issues/3620">#3620</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3877">#3877</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3933">#3933</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3997">#3997</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/4005">#4005</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4037">#4037</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4038">#4038</a>)</p>
<p>This release fixes the following problems:</p>
<ul>
<li>
<p>Naive expansion of CSS nesting can result in an exponential blow-up of generated CSS if each nesting level has multiple selectors. Previously esbuild sometimes collapsed individual nesting levels using <code>:is()</code> to limit expansion. However, this collapsing wasn't correct in some cases, so it has been removed to fix correctness issues.</p>
<pre lang="css"><code>/* Original code */
.parent {
  &gt; .a,
  &gt; .b1 &gt; .b2 {
    color: red;
  }
}
<p>/* Old output (with --supported:nesting=false) */<br />
.parent &gt; :is(.a, .b1 &gt; .b2) {<br />
color: red;<br />
}</p>
<p>/* New output (with --supported:nesting=false) */<br />
.parent &gt; .a,<br />
.parent &gt; .b1 &gt; .b2 {<br />
color: red;<br />
}<br />
</code></pre></p>
<p>Thanks to <a href="https://github.com/tim-we"><code>@​tim-we</code></a> for working on a fix.</p>
</li>
<li>
<p>The <code>&amp;</code> CSS nesting selector can be repeated multiple times to increase CSS specificity. Previously esbuild ignored this possibility and incorrectly considered <code>&amp;&amp;</code> to have the same specificity as <code>&amp;</code>. With this release, this should now work correctly:</p>
<pre lang="css"><code>/* Original code (color should be red) */
</code></pre>
</li>
</ul>
</li>
</ul>

</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md">esbuild's changelog</a>.</em></p>
<blockquote>
<h1>Changelog: 2024</h1>
<p>This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).</p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/evanw/esbuild/commit/e9174d671b1882758cd32ac5e146200f5bee3e45"><code>e9174d6</code></a> publish 0.25.0 to npm</li>
<li><a href="https://github.com/evanw/esbuild/commit/c27dbebb9e7a55dd9a084dd151dddd840787490e"><code>c27dbeb</code></a> fix <code>hosts</code> in <code>plugin-tests.js</code></li>
<li><a href="https://github.com/evanw/esbuild/commit/6794f602a453cf0255bcae245871de120a89a559"><code>6794f60</code></a> fix <code>hosts</code> in <code>node-unref-tests.js</code></li>
<li><a href="https://github.com/evanw/esbuild/commit/de85afd65edec9ebc44a11e245fd9e9a2e99760d"><code>de85afd</code></a> Merge commit from fork</li>
<li><a href="https://github.com/evanw/esbuild/commit/da1de1bf77a65f06654b49878d9ec4747ddaa21f"><code>da1de1b</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4065">#4065</a>: bitwise operators can return bigints</li>
<li><a href="https://github.com/evanw/esbuild/commit/f4e9d19fb20095a98bf40634f0380f6a16be91e7"><code>f4e9d19</code></a> switch case liveness: <code>default</code> is always last</li>
<li><a href="https://github.com/evanw/esbuild/commit/7aa47c3e778ea04849f97f18dd9959df88fa0886"><code>7aa47c3</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4028">#4028</a>: minify live/dead <code>switch</code> cases better</li>
<li><a href="https://github.com/evanw/esbuild/commit/22ecd306190b8971ec4474b5485266c20350e266"><code>22ecd30</code></a> minify: more constant folding for strict equality</li>
<li><a href="https://github.com/evanw/esbuild/commit/4cdf03c03697128044fa8fb76e5c478e9765b353"><code>4cdf03c</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4053">#4053</a>: reordering of <code>.tsx</code> in <code>node_modules</code></li>
<li><a href="https://github.com/evanw/esbuild/commit/dc719775b7140120916bd9e6777ca1cb8a1cdc0e"><code>dc71977</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/3692">#3692</a>: <code>0</code> now picks a random ephemeral port</li>
<li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.24.2...v0.25.0">compare view</a></li>
</ul>
</details>
<br />


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 <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions
You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/aws/aws-cdk/network/alerts).

</details>
@mergify
Merge branch 'main' into merge-back/2.207.0
51d6893
@mergify
chore(merge-back): 2.207.0 (#35057)
c10f509 
See [CHANGELOG](https://github.com/aws/aws-cdk/blob/merge-back/2.207.0/CHANGELOG.md)
@Abogical
ci(project-sync): add project-sync to lerna package list (#35059)
e8a1962 
### Reason for this change

Internal build tool was failing as it could not bump the dependency version automatically for the project-sync tool.

### Description of changes

Added project-sync to list of tools on lerna.

### Describe any new or updated permissions being added

No permissions added.

### Description of how you validated changes

project-sync dependency version bumped when running `sh scripts/align-version.sh`.

### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@msambol
fix(logs): query strings can have multiple stats commands (#34590)
57ae6f9 
### Issue #34578

Closes #34578

### Checklist
- [ ] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@phuhung273
fix(s3-deployment): remove .js,.d.ts file from git (#35069)
6743acb 
### Issue # (if applicable)

Closes #35066

### Reason for this change
All PRs blocked from merging

### Description of changes
Remove .js, .d.ts file from version control

### Describe any new or updated permissions being added

### Description of how you validated changes


### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@phuhung273
chore(bedrock): add TwelveLabs Marengo 2.7 and Pegasus 1.2 (#35011)
569f0c3 
### Issue # (if applicable)
None

### Reason for this change
https://aws.amazon.com/about-aws/whats-new/2025/07/twelvelabs-models-fully-managed-amazon-bedrock/

### Description of how you validated changes
```console
$ aws bedrock list-foundation-models --region us-east-1 --query 'modelSummaries[].modelId'   --output table
--------------------------------------------------
|              ListFoundationModels              |
+--------------------------------------------------+
...
|  twelvelabs.marengo-embed-2-7-v1:0             |
+--------------------------------------------------+
$ aws bedrock list-foundation-models --region us-west-2 --query 'modelSummaries[].modelId'   --output table
----------------------------------------------------
|               ListFoundationModels               |
+--------------------------------------------------+
...
|  twelvelabs.pegasus-1-2-v1:0                     |
+--------------------------------------------------+
```

### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@leonmk-aws
chore(region-info): ap-southeast-6 (#35036)
1d35961 
### Issue # (if applicable)

Closes #35031

### Reason for this change

Add support for this new region

### Description of changes
Added the new region in the `fact-table` file and in the `aws-entities`.
Fixed the unit tests and the integ tests




### Description of how you validated changes

Ran integ tests

### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@mazyu36
feat(glue): throw ValidationError instead of untyped errors (#35084)
1e20df6 
### Issue # (if applicable)

`aws-glue-alpha` for #32569


### Description of changes
ValidationErrors everywhere



### Describe any new or updated permissions being added
N/A



### Description of how you validated changes
Existing tests. Exemptions granted as this is basically a refactor of existing code.



### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@Tietew
chore(rds): deprecate PostgreSQL versions 13.17, 13.19, 14.14, 14.16,…
1061988 
… 15.9, 15.11, 16.5, 16.7, 17.1, and 17.3 (#35009)

### Reason for this change

Some PostgreSQL engine versions have been removed from available engine versions.

### Description of changes

Deprecate following PostgreSQL engine versions:
- 13.17, 13.19
- 14.14, 14.16
- 15.9, 15.11
- 16.5, 16.7
- 17.1, 17.3

### Describe any new or updated permissions being added

N/A

### Description of how you validated changes

```console
$ aws --region us-east-1 rds describe-db-engine-versions --engine postgres --query 'DBEngineVersions[].EngineVersion' --output table
--------------------------
|DescribeDBEngineVersions|
+------------------------+
|  11.22                 |
|  11.22-rds.20240418    |
|  11.22-rds.20240509    |
|  11.22-rds.20240808    |
|  11.22-rds.20241121    |
|  11.22-rds.20250220    |
|  11.22-rds.20250508    |
|  12.22                 |
|  12.22-rds.20250220    |
|  12.22-rds.20250508    |
|  13.15                 |
|  13.16                 |
|  13.18                 |
|  13.20                 |
|  13.21                 |
|  14.12                 |
|  14.13                 |
|  14.15                 |
|  14.17                 |
|  14.18                 |
|  15.7                  |
|  15.8                  |
|  15.10                 |
|  15.12                 |
|  15.13                 |
|  16.3                  |
|  16.4                  |
|  16.6                  |
|  16.8                  |
|  16.9                  |
|  17.2                  |
|  17.4                  |
|  17.5                  |
+------------------------+
```

### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@dependabot
chore(deps): bump actions/cache from 3 to 4 (#35090)
adb9c64 
Bumps [actions/cache](https://github.com/actions/cache) from 3 to 4.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/actions/cache/releases">actions/cache's releases</a>.</em></p>
<blockquote>
<h2>v4.0.0</h2>
<h2>What's Changed</h2>
<ul>
<li>Update action to node20 by <a href="https://github.com/takost"><code>@​takost</code></a> in <a href="https://redirect.github.com/actions/cache/pull/1284">actions/cache#1284</a></li>
<li>feat: save-always flag by <a href="https://github.com/to-s"><code>@​to-s</code></a> in <a href="https://redirect.github.com/actions/cache/pull/1242">actions/cache#1242</a></li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/takost"><code>@​takost</code></a> made their first contribution in <a href="https://redirect.github.com/actions/cache/pull/1284">actions/cache#1284</a></li>
<li><a href="https://github.com/to-s"><code>@​to-s</code></a> made their first contribution in <a href="https://redirect.github.com/actions/cache/pull/1242">actions/cache#1242</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/actions/cache/compare/v3...v4.0.0">https://github.com/actions/cache/compare/v3...v4.0.0</a></p>
<h2>v3.4.3</h2>
<h2>What's Changed</h2>
<ul>
<li>Bump <code>@​actions/cache</code> to v4.0.2 by <a href="https://github.com/robherley"><code>@​robherley</code></a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/actions/cache/compare/v3.4.2...v3.4.3">https://github.com/actions/cache/compare/v3.4.2...v3.4.3</a></p>
<h2>v3.4.2</h2>
<h2>What's Changed</h2>
<blockquote>
<p>[!IMPORTANT]
As a reminder, there were important backend changes to release v3.4.0, see <a href="https://github.com/actions/cache/releases/tag/v3.4.0">those release notes</a> and <a href="https://github.com/actions/cache/discussions/1510">the announcement</a> for more details.</p>
</blockquote>
<ul>
<li>Bump <code>@​actions/cache</code> to v4.0.1 by <a href="https://github.com/robherley"><code>@​robherley</code></a> in <a href="https://redirect.github.com/actions/cache/pull/1554">actions/cache#1554</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/actions/cache/compare/v3.4.0...v3.4.2">https://github.com/actions/cache/compare/v3.4.0...v3.4.2</a></p>
<h2>v3.4.1</h2>
<blockquote>
<p>[!WARNING]
This version was incorrectly released using a SHA pointing to a newer version for <em><a href="https://redirect.github.com/github/roadmap/issues/592">immutable actions</a> only</em>. Please use <code>v3.4.2</code> (or <code>v3</code>) instead.</p>
</blockquote>
<h2>v3.4.0</h2>
<h2>⚠️ Important Changes</h2>
<p>The cache backend service has been rewritten from the ground up for improved performance and reliability. <a href="https://github.com/actions/cache">actions/cache</a> now integrates with the new cache service (v2) APIs.</p>
<p>The new service will gradually roll out as of <strong>February 1st, 2025</strong>. The legacy service will also be sunset on the same date. Changes in these release are <strong>fully backward compatible</strong>.</p>
<p><strong>We are deprecating some versions of this action</strong>. We recommend upgrading to version <code>v4</code> or <code>v3</code> as soon as possible before <strong>February 1st, 2025.</strong> (Upgrade instructions below).</p>
<p>If you are using pinned SHAs, please use the SHAs of versions <code>v4.2.0</code> or <code>v3.4.0</code></p>
<p>If you do not upgrade, all workflow runs using any of the deprecated <a href="https://github.com/actions/cache">actions/cache</a> will fail.</p>
<p>Upgrading to the recommended versions will not break your workflows.</p>
<p>Read more about the change &amp; access the migration guide: <a href="https://github.com/actions/cache/discussions/1510">reference to the announcement</a>.</p>
<h3>Minor changes</h3>

</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/actions/cache/blob/main/RELEASES.md">actions/cache's changelog</a>.</em></p>
<blockquote>
<h1>Releases</h1>
<h3>4.2.3</h3>
<ul>
<li>Bump <code>@actions/cache</code> to v4.0.3 (obfuscates SAS token in debug logs for cache entries)</li>
</ul>
<h3>4.2.2</h3>
<ul>
<li>Bump <code>@actions/cache</code> to v4.0.2</li>
</ul>
<h3>4.2.1</h3>
<ul>
<li>Bump <code>@actions/cache</code> to v4.0.1</li>
</ul>
<h3>4.2.0</h3>
<p>TLDR; The cache backend service has been rewritten from the ground up for improved performance and reliability. <a href="https://github.com/actions/cache">actions/cache</a> now integrates with the new cache service (v2) APIs.</p>
<p>The new service will gradually roll out as of <strong>February 1st, 2025</strong>. The legacy service will also be sunset on the same date. Changes in these release are <strong>fully backward compatible</strong>.</p>
<p><strong>We are deprecating some versions of this action</strong>. We recommend upgrading to version <code>v4</code> or <code>v3</code> as soon as possible before <strong>February 1st, 2025.</strong> (Upgrade instructions below).</p>
<p>If you are using pinned SHAs, please use the SHAs of versions <code>v4.2.0</code> or <code>v3.4.0</code></p>
<p>If you do not upgrade, all workflow runs using any of the deprecated <a href="https://github.com/actions/cache">actions/cache</a> will fail.</p>
<p>Upgrading to the recommended versions will not break your workflows.</p>
<h3>4.1.2</h3>
<ul>
<li>Add GitHub Enterprise Cloud instances hostname filters to inform API endpoint choices - <a href="https://redirect.github.com/actions/cache/pull/1474">#1474</a></li>
<li>Security fix: Bump braces from 3.0.2 to 3.0.3 - <a href="https://redirect.github.com/actions/cache/pull/1475">#1475</a></li>
</ul>
<h3>4.1.1</h3>
<ul>
<li>Restore original behavior of <code>cache-hit</code> output - <a href="https://redirect.github.com/actions/cache/pull/1467">#1467</a></li>
</ul>
<h3>4.1.0</h3>
<ul>
<li>Ensure <code>cache-hit</code> output is set when a cache is missed - <a href="https://redirect.github.com/actions/cache/pull/1404">#1404</a></li>
<li>Deprecate <code>save-always</code> input - <a href="https://redirect.github.com/actions/cache/pull/1452">#1452</a></li>
</ul>
<h3>4.0.2</h3>
<ul>
<li>Fixed restore <code>fail-on-cache-miss</code> not working.</li>
</ul>
<h3>4.0.1</h3>
<ul>
<li>Updated <code>isGhes</code> check</li>
</ul>

</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/actions/cache/commit/5a3ec84eff668545956fd18022155c47e93e2684"><code>5a3ec84</code></a> Merge pull request <a href="https://redirect.github.com/actions/cache/issues/1577">#1577</a> from salmanmkc/salmanmkc/4-test</li>
<li><a href="https://github.com/actions/cache/commit/7de21022a7b6824c106a9847befcbd8154b45b6a"><code>7de2102</code></a> Update releases.md</li>
<li><a href="https://github.com/actions/cache/commit/76d40dd347779762a1c829bbeeda5da4d81ca8c1"><code>76d40dd</code></a> Update to use the latest version of the cache package to obfuscate the SAS</li>
<li><a href="https://github.com/actions/cache/commit/76dd5eb692f606c28d4b7a4ea7cfdffc926ba06a"><code>76dd5eb</code></a> update cache with main</li>
<li><a href="https://github.com/actions/cache/commit/8c80c27c5e4498d5675b05fb1eff96a56c593b06"><code>8c80c27</code></a> new package</li>
<li><a href="https://github.com/actions/cache/commit/45cfd0e7fffd1869ea4d5bfb54a464d825c1f742"><code>45cfd0e</code></a> updates</li>
<li><a href="https://github.com/actions/cache/commit/edd449b9cf39c2a20dc7c3d505ff6dc193c48a02"><code>edd449b</code></a> updated cache with latest changes</li>
<li><a href="https://github.com/actions/cache/commit/0576707e373f92196b81695442ed3f80c347f9c7"><code>0576707</code></a> latest test before pr</li>
<li><a href="https://github.com/actions/cache/commit/3105dc9754dd9cd935ffcf45c091ed2cadbf42b9"><code>3105dc9</code></a> update</li>
<li><a href="https://github.com/actions/cache/commit/9450d42d15022999ad2fa60a8b91f01fc92a0563"><code>9450d42</code></a> mask</li>
<li>Additional commits viewable in <a href="https://github.com/actions/cache/compare/v3...v4">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=actions/cache&package-manager=github_actions&previous-version=3&new-version=4)](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>
@dependabot
chore(deps): bump esbuild from 0.24.2 to 0.25.0 in the npm_and_yarn g…
ef477dd 
…roup across 1 directory (#35095)

Bumps the npm_and_yarn group with 1 update in the / directory: [esbuild](https://github.com/evanw/esbuild).

Updates `esbuild` from 0.24.2 to 0.25.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/evanw/esbuild/releases">esbuild's releases</a>.</em></p>
<blockquote>
<h2>v0.25.0</h2>
<p><strong>This release deliberately contains backwards-incompatible changes.</strong> To avoid automatically picking up releases like this, you should either be pinning the exact version of <code>esbuild</code> in your <code>package.json</code> file (recommended) or be using a version range syntax that only accepts patch upgrades such as <code>^0.24.0</code> or <code>~0.24.0</code>. See npm's documentation about <a href="https://docs.npmjs.com/cli/v6/using-npm/semver/">semver</a> for more information.</p>
<ul>
<li>
<p>Restrict access to esbuild's development server (<a href="https://github.com/evanw/esbuild/security/advisories/GHSA-67mh-4wv8-2f99">GHSA-67mh-4wv8-2f99</a>)</p>
<p>This change addresses esbuild's first security vulnerability report. Previously esbuild set the <code>Access-Control-Allow-Origin</code> header to <code>*</code> to allow esbuild's development server to be flexible in how it's used for development. However, this allows the websites you visit to make HTTP requests to esbuild's local development server, which gives read-only access to your source code if the website were to fetch your source code's specific URL. You can read more information in <a href="https://github.com/evanw/esbuild/security/advisories/GHSA-67mh-4wv8-2f99">the report</a>.</p>
<p>Starting with this release, <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS">CORS</a> will now be disabled, and requests will now be denied if the host does not match the one provided to <code>--serve=</code>. The default host is <code>0.0.0.0</code>, which refers to all of the IP addresses that represent the local machine (e.g. both <code>127.0.0.1</code> and <code>192.168.0.1</code>). If you want to customize anything about esbuild's development server, you can <a href="https://esbuild.github.io/api/#serve-proxy">put a proxy in front of esbuild</a> and modify the incoming and/or outgoing requests.</p>
<p>In addition, the <code>serve()</code> API call has been changed to return an array of <code>hosts</code> instead of a single <code>host</code> string. This makes it possible to determine all of the hosts that esbuild's development server will accept.</p>
<p>Thanks to <a href="https://github.com/sapphi-red"><code>@​sapphi-red</code></a> for reporting this issue.</p>
</li>
<li>
<p>Delete output files when a build fails in watch mode (<a href="https://redirect.github.com/evanw/esbuild/issues/3643">#3643</a>)</p>
<p>It has been requested for esbuild to delete files when a build fails in watch mode. Previously esbuild left the old files in place, which could cause people to not immediately realize that the most recent build failed. With this release, esbuild will now delete all output files if a rebuild fails. Fixing the build error and triggering another rebuild will restore all output files again.</p>
</li>
<li>
<p>Fix correctness issues with the CSS nesting transform (<a href="https://redirect.github.com/evanw/esbuild/issues/3620">#3620</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3877">#3877</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3933">#3933</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3997">#3997</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/4005">#4005</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4037">#4037</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4038">#4038</a>)</p>
<p>This release fixes the following problems:</p>
<ul>
<li>
<p>Naive expansion of CSS nesting can result in an exponential blow-up of generated CSS if each nesting level has multiple selectors. Previously esbuild sometimes collapsed individual nesting levels using <code>:is()</code> to limit expansion. However, this collapsing wasn't correct in some cases, so it has been removed to fix correctness issues.</p>
<pre lang="css"><code>/* Original code */
.parent {
  &gt; .a,
  &gt; .b1 &gt; .b2 {
    color: red;
  }
}
<p>/* Old output (with --supported:nesting=false) */<br />
.parent &gt; :is(.a, .b1 &gt; .b2) {<br />
color: red;<br />
}</p>
<p>/* New output (with --supported:nesting=false) */<br />
.parent &gt; .a,<br />
.parent &gt; .b1 &gt; .b2 {<br />
color: red;<br />
}<br />
</code></pre></p>
<p>Thanks to <a href="https://github.com/tim-we"><code>@​tim-we</code></a> for working on a fix.</p>
</li>
<li>
<p>The <code>&amp;</code> CSS nesting selector can be repeated multiple times to increase CSS specificity. Previously esbuild ignored this possibility and incorrectly considered <code>&amp;&amp;</code> to have the same specificity as <code>&amp;</code>. With this release, this should now work correctly:</p>
<pre lang="css"><code>/* Original code (color should be red) */
</code></pre>
</li>
</ul>
</li>
</ul>

</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md">esbuild's changelog</a>.</em></p>
<blockquote>
<h1>Changelog: 2024</h1>
<p>This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).</p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/evanw/esbuild/commit/e9174d671b1882758cd32ac5e146200f5bee3e45"><code>e9174d6</code></a> publish 0.25.0 to npm</li>
<li><a href="https://github.com/evanw/esbuild/commit/c27dbebb9e7a55dd9a084dd151dddd840787490e"><code>c27dbeb</code></a> fix <code>hosts</code> in <code>plugin-tests.js</code></li>
<li><a href="https://github.com/evanw/esbuild/commit/6794f602a453cf0255bcae245871de120a89a559"><code>6794f60</code></a> fix <code>hosts</code> in <code>node-unref-tests.js</code></li>
<li><a href="https://github.com/evanw/esbuild/commit/de85afd65edec9ebc44a11e245fd9e9a2e99760d"><code>de85afd</code></a> Merge commit from fork</li>
<li><a href="https://github.com/evanw/esbuild/commit/da1de1bf77a65f06654b49878d9ec4747ddaa21f"><code>da1de1b</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4065">#4065</a>: bitwise operators can return bigints</li>
<li><a href="https://github.com/evanw/esbuild/commit/f4e9d19fb20095a98bf40634f0380f6a16be91e7"><code>f4e9d19</code></a> switch case liveness: <code>default</code> is always last</li>
<li><a href="https://github.com/evanw/esbuild/commit/7aa47c3e778ea04849f97f18dd9959df88fa0886"><code>7aa47c3</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4028">#4028</a>: minify live/dead <code>switch</code> cases better</li>
<li><a href="https://github.com/evanw/esbuild/commit/22ecd306190b8971ec4474b5485266c20350e266"><code>22ecd30</code></a> minify: more constant folding for strict equality</li>
<li><a href="https://github.com/evanw/esbuild/commit/4cdf03c03697128044fa8fb76e5c478e9765b353"><code>4cdf03c</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4053">#4053</a>: reordering of <code>.tsx</code> in <code>node_modules</code></li>
<li><a href="https://github.com/evanw/esbuild/commit/dc719775b7140120916bd9e6777ca1cb8a1cdc0e"><code>dc71977</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/3692">#3692</a>: <code>0</code> now picks a random ephemeral port</li>
<li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.24.2...v0.25.0">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=esbuild&package-manager=npm_and_yarn&previous-version=0.24.2&new-version=0.25.0)](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 <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions
You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/aws/aws-cdk/network/alerts).

</details>
@pahud
fix(custom-resources): use loggingFormat instead of deprecated logFor…
81fe660 
…mat (#35015)

Use loggingFormat instead of deprecated logFormat in the Provider class

### Issue # (if applicable)
Closes #35002

### Reason for this change
The `logFormat` property in Lambda Function is deprecated and will be removed in the next major release. This change updates the Provider class to use the recommended `loggingFormat` property instead, eliminating deprecation warnings.

### Description of changes
- Updated the Provider class in `provider.ts` to use `loggingFormat` instead of the deprecated `logFormat` property
- Added a test in `provider.test.ts` to verify that no deprecation warnings are emitted when creating a Provider
- Ensured backward compatibility by maintaining the same functionality

This change is minimal and focused on replacing the deprecated property with its recommended alternative. The functionality remains the same, but the code now follows best practices and avoids deprecation warnings.

### Describe any new or updated permissions being added
No new or updated IAM permissions are needed for this change.

### Description of how you validated changes
- Added a unit test that verifies no deprecation warnings are emitted when using the Provider class
- Manually verified that the Provider class still functions correctly with the new property
- Ensured backward compatibility by testing with existing code

### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----
*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@aws-cdk-automation
feat: update L1 CloudFormation resource definitions (#35054)
a2b3e78 
Updates the L1 CloudFormation resource definitions with the latest changes from `@aws-cdk/aws-service-spec`

**L1 CloudFormation resource definition changes:**
```
├[~] service aws-aiops
│ └ resources
│    └[~]  resource AWS::AIOps::InvestigationGroup
│       ├      - documentation: Creates an *investigation group* in your account. Creating an investigation group is a one-time setup task for each Region in your account. It is a necessary task to be able to perform investigations.
│       │      Settings in the investigation group help you centrally manage the common properties of your investigations, such as the following:
│       │      - Who can access the investigations
│       │      - Whether investigation data is encrypted with a customer managed AWS Key Management Service key.
│       │      - How long investigations and their data are retained by default.
│       │      Currently, you can have one investigation group in each Region in your account. Each investigation in a Region is a part of the investigation group in that Region
│       │      To create an investigation group and set up CloudWatch investigations, you must be signed in to an IAM principal that has the either the `AIOpsConsoleAdminPolicy` or the `AdministratorAccess` IAM policy attached, or to an account that has similar permissions.
│       │      > You can configure CloudWatch alarms to start investigations and add events to investigations. If you create your investigation group with `CreateInvestigationGroup` and you want to enable alarms to do this, you must use `PutInvestigationGroupPolicy` to create a resource policy that grants this permission to CloudWatch alarms.
│       │      > 
│       │      > For more information about configuring CloudWatch alarms to work with CloudWatch investigations, see
│       │      + documentation: Creates an *investigation group* in your account. Creating an investigation group is a one-time setup task for each Region in your account. It is a necessary task to be able to perform investigations.
│       │      Settings in the investigation group help you centrally manage the common properties of your investigations, such as the following:
│       │      - Who can access the investigations
│       │      - Whether investigation data is encrypted with a customer managed AWS Key Management Service key.
│       │      - How long investigations and their data are retained by default.
│       │      Currently, you can have one investigation group in each Region in your account. Each investigation in a Region is a part of the investigation group in that Region
│       │      To create an investigation group and set up CloudWatch investigations, you must be signed in to an IAM principal that has either the `AIOpsConsoleAdminPolicy` or the `AdministratorAccess` IAM policy attached, or to an account that has similar permissions.
│       │      > You can configure CloudWatch alarms to start investigations and add events to investigations. If you create your investigation group with `CreateInvestigationGroup` and you want to enable alarms to do this, you must use `PutInvestigationGroupPolicy` to create a resource policy that grants this permission to CloudWatch alarms.
│       │      > 
│       │      > For more information about configuring CloudWatch alarms, see [Using Amazon CloudWatch alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html)
│       └ properties
│          ├ CrossAccountConfigurations: (documentation changed)
│          ├ InvestigationGroupPolicy: (documentation changed)
│          └ Name: (documentation changed)
├[~] service aws-amazonmq
│ └ resources
│    └[~]  resource AWS::AmazonMQ::Broker
│       ├ attributes
│       │  └[+] ConsoleURLs: Array<string>
│       └ types
│          └[~] type User
│            └ properties
│               └[-] JolokiaApiAccess: string
├[~] service aws-appstream
│ └ resources
│    ├[~]  resource AWS::AppStream::Fleet
│    │  └ properties
│    │     └ InstanceType: (documentation changed)
│    └[~]  resource AWS::AppStream::ImageBuilder
│       └ properties
│          └ InstanceType: (documentation changed)
├[~] service aws-bedrock
│ └ resources
│    └[~]  resource AWS::Bedrock::Guardrail
│       ├ properties
│       │  └ CrossRegionConfig: (documentation changed)
│       └ types
│          ├[~] type ContentFilterConfig
│          │ └ properties
│          │    ├ InputAction: (documentation changed)
│          │    ├ InputEnabled: (documentation changed)
│          │    ├ InputModalities: (documentation changed)
│          │    ├ OutputAction: (documentation changed)
│          │    ├ OutputEnabled: (documentation changed)
│          │    └ OutputModalities: (documentation changed)
│          ├[~] type ContentFiltersTierConfig
│          │ ├      - documentation: Guardrail tier config for content policy
│          │ │      + documentation: The tier that your guardrail uses for content filters. Consider using a tier that balances performance, accuracy, and compatibility with your existing generative AI workflows.
│          │ └ properties
│          │    └ TierName: (documentation changed)
│          ├[~] type ContentPolicyConfig
│          │ └ properties
│          │    └ ContentFiltersTierConfig: (documentation changed)
│          ├[~] type ContextualGroundingFilterConfig
│          │ └ properties
│          │    ├ Action: (documentation changed)
│          │    └ Enabled: (documentation changed)
│          ├[~] type GuardrailCrossRegionConfig
│          │ └ properties
│          │    └ GuardrailProfileArn: (documentation changed)
│          ├[~] type ManagedWordsConfig
│          │ └ properties
│          │    ├ InputAction: (documentation changed)
│          │    ├ InputEnabled: (documentation changed)
│          │    ├ OutputAction: (documentation changed)
│          │    └ OutputEnabled: (documentation changed)
│          ├[~] type PiiEntityConfig
│          │ └ properties
│          │    ├ InputAction: (documentation changed)
│          │    ├ InputEnabled: (documentation changed)
│          │    ├ OutputAction: (documentation changed)
│          │    └ OutputEnabled: (documentation changed)
│          ├[~] type RegexConfig
│          │ └ properties
│          │    ├ InputAction: (documentation changed)
│          │    ├ InputEnabled: (documentation changed)
│          │    ├ OutputAction: (documentation changed)
│          │    └ OutputEnabled: (documentation changed)
│          ├[~] type TopicConfig
│          │ └ properties
│          │    ├ InputAction: (documentation changed)
│          │    ├ InputEnabled: (documentation changed)
│          │    ├ OutputAction: (documentation changed)
│          │    └ OutputEnabled: (documentation changed)
│          ├[~] type TopicPolicyConfig
│          │ └ properties
│          │    └ TopicsTierConfig: (documentation changed)
│          ├[~] type TopicsTierConfig
│          │ ├      - documentation: Guardrail tier config for topic policy
│          │ │      + documentation: The tier that your guardrail uses for denied topic filters. Consider using a tier that balances performance, accuracy, and compatibility with your existing generative AI workflows.
│          │ └ properties
│          │    └ TierName: (documentation changed)
│          └[~] type WordConfig
│            └ properties
│               ├ InputAction: (documentation changed)
│               ├ InputEnabled: (documentation changed)
│               ├ OutputAction: (documentation changed)
│               └ OutputEnabled: (documentation changed)
├[~] service aws-billing
│ └ resources
│    └[~]  resource AWS::Billing::BillingView
│       └ properties
│          └ Name: (documentation changed)
├[~] service aws-certificatemanager
│ └ resources
│    └[~]  resource AWS::CertificateManager::Certificate
│       └ properties
│          └[+] CertificateExport: string
├[~] service aws-cloudfront
│ └ resources
│    ├[~]  resource AWS::CloudFront::CachePolicy
│    │  └ types
│    │     └[~] type CachePolicyConfig
│    │       └      - documentation: A cache policy configuration.
│    │              This configuration determines the following:
│    │              - The values that CloudFront includes in the cache key. These values can include HTTP headers, cookies, and URL query strings. CloudFront uses the cache key to find an object in its cache that it can return to the viewer.
│    │              - The default, minimum, and maximum time to live (TTL) values that you want objects to stay in the CloudFront cache.
│    │              The headers, cookies, and query strings that are included in the cache key are also included in requests that CloudFront sends to the origin. CloudFront sends a request when it can't find a valid object in its cache that matches the request's cache key. If you want to send values to the origin but *not* include them in the cache key, use `OriginRequestPolicy` .
│    │              + documentation: A cache policy configuration.
│    │              This configuration determines the following:
│    │              - The values that CloudFront includes in the cache key. These values can include HTTP headers, cookies, and URL query strings. CloudFront uses the cache key to find an object in its cache that it can return to the viewer.
│    │              - The default, minimum, and maximum time to live (TTL) values that you want objects to stay in the CloudFront cache.
│    │              > If your minimum TTL is greater than 0, CloudFront will cache content for at least the duration specified in the cache policy's minimum TTL, even if the `Cache-Control: no-cache` , `no-store` , or `private` directives are present in the origin headers.
│    │              The headers, cookies, and query strings that are included in the cache key are also included in requests that CloudFront sends to the origin. CloudFront sends a request when it can't find a valid object in its cache that matches the request's cache key. If you want to send values to the origin but *not* include them in the cache key, use `OriginRequestPolicy` .
│    └[~]  resource AWS::CloudFront::Distribution
│       └ types
│          ├[~] type CacheBehavior
│          │ └      - documentation: A complex type that describes how CloudFront processes requests.
│          │        You must create at least as many cache behaviors (including the default cache behavior) as you have origins if you want CloudFront to serve objects from all of the origins. Each cache behavior specifies the one origin from which you want CloudFront to get objects. If you have two origins and only the default cache behavior, the default cache behavior will cause CloudFront to get objects from one of the origins, but the other origin is never used.
│          │        For the current quota (formerly known as limit) on the number of cache behaviors that you can add to a distribution, see [Quotas](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/cloudfront-limits.html) in the *Amazon CloudFront Developer Guide* .
│          │        If you don't want to specify any cache behaviors, include only an empty `CacheBehaviors` element. Don't specify an empty individual `CacheBehavior` element, because this is invalid. For more information, see [CacheBehaviors](https://docs.aws.amazon.com/cloudfront/latest/APIReference/API_CacheBehaviors.html) .
│          │        To delete all cache behaviors in an existing distribution, update the distribution configuration and include only an empty `CacheBehaviors` element.
│          │        To add, change, or remove one or more cache behaviors, update the distribution configuration and specify all of the cache behaviors that you want to include in the updated distribution.
│          │        For more information about cache behaviors, see [Cache Behavior Settings](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/distribution-web-values-specify.html#DownloadDistValuesCacheBehavior) in the *Amazon CloudFront Developer Guide* .
│          │        + documentation: A complex type that describes how CloudFront processes requests.
│          │        You must create at least as many cache behaviors (including the default cache behavior) as you have origins if you want CloudFront to serve objects from all of the origins. Each cache behavior specifies the one origin from which you want CloudFront to get objects. If you have two origins and only the default cache behavior, the default cache behavior will cause CloudFront to get objects from one of the origins, but the other origin is never used.
│          │        For the current quota (formerly known as limit) on the number of cache behaviors that you can add to a distribution, see [Quotas](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/cloudfront-limits.html) in the *Amazon CloudFront Developer Guide* .
│          │        If you don't want to specify any cache behaviors, include only an empty `CacheBehaviors` element. Don't specify an empty individual `CacheBehavior` element, because this is invalid. For more information, see [CacheBehaviors](https://docs.aws.amazon.com/cloudfront/latest/APIReference/API_CacheBehaviors.html) .
│          │        To delete all cache behaviors in an existing distribution, update the distribution configuration and include only an empty `CacheBehaviors` element.
│          │        To add, change, or remove one or more cache behaviors, update the distribution configuration and specify all of the cache behaviors that you want to include in the updated distribution.
│          │        > If your minimum TTL is greater than 0, CloudFront will cache content for at least the duration specified in the cache policy's minimum TTL, even if the `Cache-Control: no-cache` , `no-store` , or `private` directives are present in the origin headers. 
│          │        For more information about cache behaviors, see [Cache Behavior Settings](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/distribution-web-values-specify.html#DownloadDistValuesCacheBehavior) in the *Amazon CloudFront Developer Guide* .
│          ├[~] type DefaultCacheBehavior
│          │ └      - documentation: A complex type that describes the default cache behavior if you don't specify a `CacheBehavior` element or if request URLs don't match any of the values of `PathPattern` in `CacheBehavior` elements. You must create exactly one default cache behavior.
│          │        + documentation: A complex type that describes the default cache behavior if you don't specify a `CacheBehavior` element or if request URLs don't match any of the values of `PathPattern` in `CacheBehavior` elements. You must create exactly one default cache behavior.
│          │        > If your minimum TTL is greater than 0, CloudFront will cache content for at least the duration specified in the cache policy's minimum TTL, even if the `Cache-Control: no-cache` , `no-store` , or `private` directives are present in the origin headers.
│          └[~] type DistributionConfig
│            └ properties
│               └ ConnectionMode: (documentation changed)
├[~] service aws-connect
│ └ resources
│    ├[~]  resource AWS::Connect::EvaluationForm
│    │  └ types
│    │     └[~] type AutoEvaluationConfiguration
│    │       └ properties
│    │          └ Enabled: (documentation changed)
│    └[~]  resource AWS::Connect::Instance
│       └ types
│          └[~] type Attributes
│            └ properties
│               ├[+] EnhancedChatMonitoring: boolean
│               ├[+] EnhancedContactMonitoring: boolean
│               ├[+] HighVolumeOutBound: boolean
│               ├[+] MultiPartyChatConference: boolean
│               └[+] MultiPartyConference: boolean
├[~] service aws-customerprofiles
│ └ resources
│    ├[~]  resource AWS::CustomerProfiles::CalculatedAttributeDefinition
│    │  ├      - documentation: A calculated attribute definition for Customer Profiles
│    │  │      + documentation: A calculated attribute definition for Customer Profiles.
│    │  └ types
│    │     ├[~] type Range
│    │     │ └ properties
│    │     │    ├ TimestampFormat: (documentation changed)
│    │     │    ├ TimestampSource: (documentation changed)
│    │     │    └ ValueRange: (documentation changed)
│    │     ├[~] type Readiness
│    │     │ ├      - documentation: The readiness status of the calculated attribute.
│    │     │ │      + documentation: Information indicating if the Calculated Attribute is ready for use by confirming all historical data has been processed and reflected.
│    │     │ └ properties
│    │     │    ├ Message: (documentation changed)
│    │     │    └ ProgressPercentage: (documentation changed)
│    │     └[~] type ValueRange
│    │       ├      - documentation: A structure specifying the endpoints of the relative time period over which data is included in the aggregation.
│    │       │      + documentation: A structure letting customers specify a relative time window over which over which data is included in the Calculated Attribute. Use positive numbers to indicate that the endpoint is in the past, and negative numbers to indicate it is in the future. ValueRange overrides Value.
│    │       └ properties
│    │          ├ End: (documentation changed)
│    │          └ Start: (documentation changed)
│    └[~]  resource AWS::CustomerProfiles::SegmentDefinition
│       └ types
│          ├[~] type ProfileAttributes
│          │ └ properties
│          │    └ ProfileType: (documentation changed)
│          └[~] type ProfileTypeDimension
│            └ properties
│               ├ DimensionType: (documentation changed)
│               └ Values: (documentation changed)
├[~] service aws-docdb
│ └ resources
│    └[~]  resource AWS::DocDB::DBCluster
│       └ properties
│          └ GlobalClusterIdentifier: (documentation changed)
├[~] service aws-ec2
│ └ resources
│    ├[~]  resource AWS::EC2::CapacityReservation
│    │  └ properties
│    │     ├ InstanceCount: (documentation changed)
│    │     └ InstanceType: (documentation changed)
│    ├[~]  resource AWS::EC2::Instance
│    │  └ properties
│    │     └ KeyName: (documentation changed)
│    └[~]  resource AWS::EC2::TrafficMirrorSession
│       ├ properties
│       │  └[+] OwnerId: string
│       └ attributes
│          └ Id: (documentation changed)
├[~] service aws-ecs
│ └ resources
│    └[~]  resource AWS::ECS::Service
│       └ types
│          ├[+]  type AdvancedConfiguration
│          │  ├      documentation: The advanced settings for a load balancer used in blue/green deployments. Specify the alternate target group, listener rules, and IAM role required for traffic shifting during blue/green deployments. For more information, see [Required resources for Amazon ECS blue/green deployments](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/blue-green-deployment-implementation.html) in the *Amazon Elastic Container Service Developer Guide* .
│          │  │      name: AdvancedConfiguration
│          │  └ properties
│          │     ├ TestListenerRule: string
│          │     ├ AlternateTargetGroupArn: string (required)
│          │     ├ ProductionListenerRule: string
│          │     └ RoleArn: string
│          ├[~] type DeploymentConfiguration
│          │ └ properties
│          │    ├[+] BakeTimeInMinutes: integer
│          │    ├[+] LifecycleHooks: Array<DeploymentLifecycleHook>
│          │    └[+] Strategy: string
│          ├[+]  type DeploymentLifecycleHook
│          │  ├      documentation: A deployment lifecycle hook runs custom logic at specific stages of the deployment process. Currently, you can use Lambda functions as hook targets.
│          │  │      For more information, see [Lifecycle hooks for Amazon ECS service deployments](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-lifecycle-hooks.html) in the *Amazon Elastic Container Service Developer Guide* .
│          │  │      name: DeploymentLifecycleHook
│          │  └ properties
│          │     ├ LifecycleStages: Array<string> (required)
│          │     ├ HookTargetArn: string (required)
│          │     └ RoleArn: string (required)
│          ├[~] type LoadBalancer
│          │ └ properties
│          │    └[+] AdvancedConfiguration: AdvancedConfiguration
│          ├[~] type ServiceConnectClientAlias
│          │ └ properties
│          │    └[+] TestTrafficRules: ServiceConnectTestTrafficRules
│          ├[+]  type ServiceConnectTestTrafficRules
│          │  ├      documentation: The test traffic routing configuration for Amazon ECS blue/green deployments. This configuration allows you to define rules for routing specific traffic to the new service revision during the deployment process, allowing for safe testing before full production traffic shift.
│          │  │      For more information, see [Service Connect for Amazon ECS blue/green deployments](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect-blue-green.html) in the *Amazon Elastic Container Service Developer Guide* .
│          │  │      name: ServiceConnectTestTrafficRules
│          │  └ properties
│          │     └ Header: ServiceConnectTestTrafficRulesHeader (required)
│          ├[+]  type ServiceConnectTestTrafficRulesHeader
│          │  ├      name: ServiceConnectTestTrafficRulesHeader
│          │  └ properties
│          │     ├ Value: ServiceConnectTestTrafficRulesHeaderValue
│          │     └ Name: string (required)
│          └[+]  type ServiceConnectTestTrafficRulesHeaderValue
│             ├      name: ServiceConnectTestTrafficRulesHeaderValue
│             └ properties
│                └ Exact: string (required)
├[~] service aws-events
│ └ resources
│    └[~]  resource AWS::Events::EventBus
│       ├ properties
│       │  └[+] LogConfig: LogConfig
│       └ types
│          └[+]  type LogConfig
│             ├      documentation: The logging configuration settings for the event bus.
│             │      For more information, see [Configuring logs for event buses](https://docs.aws.amazon.com/eb-event-bus-logs.html) in the *EventBridge User Guide* .
│             │      name: LogConfig
│             └ properties
│                ├ IncludeDetail: string
│                └ Level: string
├[~] service aws-gamelift
│ └ resources
│    └[~]  resource AWS::GameLift::ContainerFleet
│       └ types
│          └[~] type LocationCapacity
│            └ properties
│               └ DesiredEC2Instances: (documentation changed)
├[~] service aws-guardduty
│ └ resources
│    ├[~]  resource AWS::GuardDuty::IPSet
│    │  └ properties
│    │     └[+] ExpectedBucketOwner: string
│    └[~]  resource AWS::GuardDuty::ThreatIntelSet
│       └ properties
│          └[+] ExpectedBucketOwner: string
├[~] service aws-kinesisfirehose
│ └ resources
│    └[~]  resource AWS::KinesisFirehose::DeliveryStream
│       └ types
│          ├[~] type CatalogConfiguration
│          │ └ properties
│          │    └[+] WarehouseLocation: string
│          ├[~] type DestinationTableConfiguration
│          │ └ properties
│          │    └[+] PartitionSpec: PartitionSpec
│          ├[~] type IcebergDestinationConfiguration
│          │ └ properties
│          │    ├[+] SchemaEvolutionConfiguration: SchemaEvolutionConfiguration
│          │    └[+] TableCreationConfiguration: TableCreationConfiguration
│          ├[+]  type PartitionField
│          │  ├      documentation: Represents a single field in a `PartitionSpec` .
│          │  │      Amazon Data Firehose is in preview release and is subject to change.
│          │  │      name: PartitionField
│          │  └ properties
│          │     └ SourceName: string (required)
│          ├[+]  type PartitionSpec
│          │  ├      documentation: Represents how to produce partition data for a table. Partition data is produced by transforming columns in a table. Each column transform is represented by a named `PartitionField` .
│          │  │      Here is an example of the schema in JSON.
│          │  │      `"partitionSpec": { "identity": [ {"sourceName": "column1"}, {"sourceName": "column2"}, {"sourceName": "column3"} ] }`
│          │  │      Amazon Data Firehose is in preview release and is subject to change.
│          │  │      name: PartitionSpec
│          │  └ properties
│          │     └ Identity: Array<PartitionField>
│          ├[+]  type SchemaEvolutionConfiguration
│          │  ├      documentation: The configuration to enable schema evolution.
│          │  │      Amazon Data Firehose is in preview release and is subject to change.
│          │  │      name: SchemaEvolutionConfiguration
│          │  └ properties
│          │     └ Enabled: boolean
│          └[+]  type TableCreationConfiguration
│             ├      documentation: The configuration to enable automatic table creation.
│             │      Amazon Data Firehose is in preview release and is subject to change.
│             │      name: TableCreationConfiguration
│             └ properties
│                └ Enabled: boolean
├[~] service aws-mediapackagev2
│ └ resources
│    └[~]  resource AWS::MediaPackageV2::OriginEndpoint
│       └ types
│          ├[+]  type DashBaseUrl
│          │  ├      documentation: The base URLs to use for retrieving segments. You can specify multiple locations and indicate the priority and weight for when each should be used, for use in mutli-CDN workflows.
│          │  │      name: DashBaseUrl
│          │  └ properties
│          │     ├ Url: string (required)
│          │     ├ ServiceLocation: string
│          │     ├ DvbPriority: integer
│          │     └ DvbWeight: integer
│          ├[+]  type DashDvbFontDownload
│          │  ├      documentation: For use with DVB-DASH profiles only. The settings for font downloads that you want AWS Elemental MediaPackage to pass through to the manifest.
│          │  │      name: DashDvbFontDownload
│          │  └ properties
│          │     ├ Url: string
│          │     ├ MimeType: string
│          │     └ FontFamily: string
│          ├[+]  type DashDvbMetricsReporting
│          │  ├      documentation: For use with DVB-DASH profiles only. The settings for error reporting from the playback device that you want AWS Elemental MediaPackage to pass through to the manifest.
│          │  │      name: DashDvbMetricsReporting
│          │  └ properties
│          │     ├ ReportingUrl: string (required)
│          │     └ Probability: integer
│          ├[+]  type DashDvbSettings
│          │  ├      documentation: For endpoints that use the DVB-DASH profile only. The font download and error reporting information that you want MediaPackage to pass through to the manifest.
│          │  │      name: DashDvbSettings
│          │  └ properties
│          │     ├ FontDownload: DashDvbFontDownload
│          │     └ ErrorMetrics: Array<DashDvbMetricsReporting>
│          ├[~] type DashManifestConfiguration
│          │ └ properties
│          │    ├[+] BaseUrls: Array<DashBaseUrl>
│          │    ├[+] Compactness: string
│          │    ├[+] DvbSettings: DashDvbSettings
│          │    ├[+] Profiles: Array<string>
│          │    ├[+] ProgramInformation: DashProgramInformation
│          │    └[+] SubtitleConfiguration: DashSubtitleConfiguration
│          ├[+]  type DashProgramInformation
│          │  ├      documentation: Details about the content that you want MediaPackage to pass through in the manifest to the playback device.
│          │  │      name: DashProgramInformation
│          │  └ properties
│          │     ├ Title: string
│          │     ├ Source: string
│          │     ├ Copyright: string
│          │     ├ LanguageCode: string
│          │     └ MoreInformationUrl: string
│          ├[+]  type DashSubtitleConfiguration
│          │  ├      documentation: The configuration for DASH subtitles.
│          │  │      name: DashSubtitleConfiguration
│          │  └ properties
│          │     └ TtmlConfiguration: DashTtmlConfiguration
│          └[+]  type DashTtmlConfiguration
│             ├      documentation: The settings for TTML subtitles.
│             │      name: DashTtmlConfiguration
│             └ properties
│                └ TtmlProfile: string (required)
├[~] service aws-omics
│ └ resources
│    ├[~]  resource AWS::Omics::RunGroup
│    │  └      - documentation: You can optionally create a run group to limit the compute resources for the runs that you add to the group.
│    │         + documentation: Creates a run group to limit the compute resources for the runs that are added to the group. Returns an ARN, ID, and tags for the run group.
│    ├[~]  resource AWS::Omics::Workflow
│    │  ├      - documentation: Creates a private workflow.Private workflows depend on a variety of resources that you create and configure before creating the workflow:
│    │  │      - *Input data* : Input data for the workflow, stored in an S3 bucket or a AWS HealthOmics sequence store.
│    │  │      - *Workflow definition files* : Define your workflow in one or more workflow definition files, written in WDL, Nextflow, or CWL. The workflow definition specifies the inputs and outputs for runs that use the workflow. It also includes specifications for the runs and run tasks for your workflow, including compute and memory requirements.
│    │  │      - (Optional) *Parameter template* - You can create a parameter template file that defines the run parameters, or AWS HealthOmics can generate the parameter template for you.
│    │  │      - *ECR container images* : Create one or more container images for the workflow. Store the images in a private ECR repository.
│    │  │      - (Optional) *Sentieon licenses* : Request a Sentieon license if you plan to use Sentieon software in a private workflow.
│    │  │      For more information, see [Creating or updating a private workflow in AWS HealthOmics](https://docs.aws.amazon.com/omics/latest/dev/creating-private-workflows.html) in the AWS HealthOmics User Guide.
│    │  │      + documentation: Creates a private workflow. Before you create a private workflow, you must create and configure these required resources:
│    │  │      - *Workflow definition files* : Define your workflow in one or more workflow definition files, written in WDL, Nextflow, or CWL. The workflow definition specifies the inputs and outputs for runs that use the workflow. It also includes specifications for the runs and run tasks for your workflow, including compute and memory requirements. The workflow definition file must be in .zip format.
│    │  │      - (Optional) *Parameter template* : You can create a parameter template file that defines the run parameters, or AWS HealthOmics can generate the parameter template for you.
│    │  │      - *ECR container images* : Create one or more container images for the workflow. Store the images in a private ECR repository.
│    │  │      - (Optional) *Sentieon licenses* : Request a Sentieon license if using the Sentieon software in a private workflow.
│    │  │      For more information, see [Creating or updating a private workflow in AWS HealthOmics](https://docs.aws.amazon.com/omics/latest/dev/creating-private-workflows.html) in the *AWS HealthOmics User Guide* .
│    │  └ properties
│    │     └ StorageCapacity: (documentation changed)
│    └[~]  resource AWS::Omics::WorkflowVersion
│       └      - documentation: Creates a new workflow version for the workflow that you specify with the `workflowId` parameter.
│              When you create a new version of a workflow, you need to specify the configuration for the new version. It doesn't inherit any configuration values from the workflow.
│              Provide a version name that is unique for this workflow. You cannot change the name after HealthOmics creates the version.
│              > Don’t include any personally identifiable information (PII) in the version name. Version names appear in the workflow version ARN. 
│              For more information, see [Workflow versioning in AWS HealthOmics](https://docs.aws.amazon.com/omics/latest/dev/workflow-versions.html) in the AWS HealthOmics User Guide.
│              + documentation: Creates a new workflow version for the workflow that you specify with the `workflowId` parameter.
│              When you create a new version of a workflow, you need to specify the configuration for the new version. It doesn't inherit any configuration values from the workflow.
│              Provide a version name that is unique for this workflow. You cannot change the name after HealthOmics creates the version.
│              > Don’t include any personally identifiable information (PII) in the version name. Version names appear in the workflow version ARN. 
│              For more information, see [Workflow versioning in AWS HealthOmics](https://docs.aws.amazon.com/omics/latest/dev/workflow-versions.html) in the *AWS HealthOmics User Guide* .
├[~] service aws-quicksight
│ └ resources
│    ├[~]  resource AWS::QuickSight::DataSource
│    │  └ types
│    │     ├[~] type AthenaParameters
│    │     │ └ properties
│    │     │    └[+] IdentityCenterConfiguration: IdentityCenterConfiguration
│    │     ├[~] type OracleParameters
│    │     │ └ properties
│    │     │    └ UseServiceName: (documentation changed)
│    │     └[~] type RedshiftParameters
│    │       └ properties
│    │          └ IdentityCenterConfiguration: - json ⇐ IdentityCenterConfiguration
│    │                                         + IdentityCenterConfiguration
│    └[~]  resource AWS::QuickSight::Topic
│       ├      - tagInformation: undefined
│       │      + tagInformation: {"tagPropertyName":"Tags","variant":"standard"}
│       └ properties
│          └[+] Tags: Array<tag> (immutable)
├[~] service aws-rds
│ └ resources
│    ├[~]  resource AWS::RDS::DBCluster
│    │  └ properties
│    │     └[+] DeleteAutomatedBackups: boolean
│    └[~]  resource AWS::RDS::DBInstance
│       └ attributes
│          ├[+] DBInstanceStatus: string
│          ├[+] InstanceCreateTime: string
│          ├[+] IsStorageConfigUpgradeAvailable: boolean
│          ├[+] LatestRestorableTime: string
│          ├[+] ListenerEndpoint: Endpoint
│          ├[+] ListenerEndpoint.Address: string
│          ├[+] ListenerEndpoint.HostedZoneId: string
│          ├[+] ListenerEndpoint.Port: string
│          ├[+] ReadReplicaDBClusterIdentifiers: Array<string>
│          └[+] ReadReplicaDBInstanceIdentifiers: Array<string>
├[~] service aws-redshift
│ └ resources
│    ├[~]  resource AWS::Redshift::ClusterSubnetGroup
│    │  └      - tagInformation: undefined
│    │         + tagInformation: {"tagPropertyName":"Tags","variant":"standard"}
│    └[~]  resource AWS::Redshift::EventSubscription
│       └      - tagInformation: undefined
│              + tagInformation: {"tagPropertyName":"Tags","variant":"standard"}
├[~] service aws-s3
│ └ resources
│    └[~]  resource AWS::S3::Bucket
│       ├ properties
│       │  └[+] MetadataConfiguration: MetadataConfiguration
│       ├ attributes
│       │  ├[+] MetadataConfiguration.Destination: MetadataDestination
│       │  ├[+] MetadataConfiguration.InventoryTableConfiguration.TableArn: string
│       │  ├[+] MetadataConfiguration.InventoryTableConfiguration.TableName: string
│       │  ├[+] MetadataConfiguration.JournalTableConfiguration.TableArn: string
│       │  └[+] MetadataConfiguration.JournalTableConfiguration.TableName: string
│       └ types
│          ├[+]  type InventoryTableConfiguration
│          │  ├      documentation: The inventory table configuration for an S3 Metadata configuration.
│          │  │      name: InventoryTableConfiguration
│          │  └ properties
│          │     ├ TableName: string
│          │     ├ TableArn: string
│          │     ├ ConfigurationState: string (required)
│          │     └ EncryptionConfiguration: MetadataTableEncryptionConfiguration
│          ├[+]  type JournalTableConfiguration
│          │  ├      documentation: The journal table configuration for an S3 Metadata configuration.
│          │  │      name: JournalTableConfiguration
│          │  └ properties
│          │     ├ TableName: string
│          │     ├ TableArn: string
│          │     ├ RecordExpiration: RecordExpiration (required)
│          │     └ EncryptionConfiguration: MetadataTableEncryptionConfiguration (immutable)
│          ├[+]  type MetadataConfiguration
│          │  ├      documentation: Creates a V2 Amazon S3 Metadata configuration of a general purpose bucket. For more information, see [Accelerating data discovery with S3 Metadata](https://docs.aws.amazon.com/AmazonS3/latest/userguide/metadata-tables-overview.html) in the *Amazon S3 User Guide* .
│          │  │      name: MetadataConfiguration
│          │  └ properties
│          │     ├ Destination: MetadataDestination
│          │     ├ JournalTableConfiguration: JournalTableConfiguration (required)
│          │     └ InventoryTableConfiguration: InventoryTableConfiguration
│          ├[+]  type MetadataDestination
│          │  ├      documentation: The destination information for the S3 Metadata configuration.
│          │  │      name: MetadataDestination
│          │  └ properties
│          │     ├ TableBucketType: string (required)
│          │     ├ TableBucketArn: string
│          │     └ TableNamespace: string
│          ├[~] type MetadataTableConfiguration
│          │ └      - documentation: The metadata table configuration of an Amazon S3 general purpose bucket. For more information, see [Accelerating data discovery with S3 Metadata](https://docs.aws.amazon.com/AmazonS3/latest/userguide/metadata-tables-overview.html) and [Setting up permissions for configuring metadata tables](https://docs.aws.amazon.com/AmazonS3/latest/userguide/metadata-tables-permissions.html) .
│          │        + documentation: > We recommend that you create your S3 Metadata configurations by using the V2 [MetadataConfiguration](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-s3-bucket-metadataconfiguration.html) resource type. We no longer recommend using the V1 `MetadataTableConfiguration` resource type.
│          │        > 
│          │        > If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete and re-create your configuration by using the [MetadataConfiguration](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-s3-bucket-metadataconfiguration.html) resource type so that you can expire journal table records and create a live inventory table. 
│          │        Creates a V1 S3 Metadata configuration for a general purpose bucket. For more information, see [Accelerating data discovery with S3 Metadata](https://docs.aws.amazon.com/AmazonS3/latest/userguide/metadata-tables-overview.html) in the *Amazon S3 User Guide* .
│          ├[+]  type MetadataTableEncryptionConfiguration
│          │  ├      documentation: The encryption settings for an S3 Metadata journal table or inventory table configuration.
│          │  │      name: MetadataTableEncryptionConfiguration
│          │  └ properties
│          │     ├ SseAlgorithm: string (required)
│          │     └ KmsKeyArn: string
│          ├[+]  type RecordExpiration
│          │  ├      documentation: The journal table record expiration settings for a journal table in an S3 Metadata configuration.
│          │  │      name: RecordExpiration
│          │  └ properties
│          │     ├ Expiration: string (required)
│          │     └ Days: integer
│          └[~] type S3TablesDestination
│            └      - documentation: The destination information for a V1 S3 Metadata configuration. The destination table bucket must be in the same Region and AWS account as the general purpose bucket. The specified metadata table name must be unique within the `aws_s3_metadata` namespace in the destination table bucket.
│                   > If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete and re-create your configuration by using [CreateBucketMetadataConfiguration](https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucketMetadataConfiguration.html) so that you can expire journal table records and create a live inventory table.
│                   + documentation: The destination information for a V1 S3 Metadata configuration. The destination table bucket must be in the same Region and AWS account as the general purpose bucket. The specified metadata table name must be unique within the `aws_s3_metadata` namespace in the destination table bucket.
├[~] service aws-s3express
│ └ resources
│    └[~]  resource AWS::S3Express::DirectoryBucket
│       ├      - tagInformation: undefined
│       │      + tagInformation: {"tagPropertyName":"Tags","variant":"standard"}
│       └ properties
│          └[+] Tags: Array<tag>
├[~] service aws-s3tables
│ └ resources
│    └[+]  resource AWS::S3Tables::TablePolicy
│       ├      name: TablePolicy
│       │      cloudFormationType: AWS::S3Tables::TablePolicy
│       │      documentation: Creates a new maintenance configuration or replaces an existing table policy for a table. For more information, see [Adding a table policy](https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-tables-table-policy.html#table-policy-add) in the *Amazon Simple Storage Service User Guide* .
│       │      - **Permissions** - You must have the `s3tables:PutTablePolicy` permission to use this operation.
│       │      scrutinizable: ResourcePolicyResource
│       ├ properties
│       │  ├ ResourcePolicy: json | string (required)
│       │  └ TableARN: string (required, immutable)
│       └ attributes
│          ├ TableBucketARN: string
│          ├ Namespace: string
│          └ TableName: string
├[~] service aws-sagemaker
│ └ resources
│    ├[~]  resource AWS::SageMaker::Domain
│    │  └ properties
│    │     ├ SubnetIds: - Array<string> (required, immutable)
│    │     │            + Array<string> (immutable)
│    │     └ VpcId: - string (required, immutable)
│    │              + string (immutable)
│    ├[~]  resource AWS::SageMaker::Project
│    │  ├ properties
│    │  │  ├ ServiceCatalogProvisioningDetails: - ServiceCatalogProvisioningDetails ⇐ json (required, immutable)
│    │  │  │                                    + ServiceCatalogProvisioningDetails ⇐ json (immutable)
│    │  │  └[+] TemplateProviderDetails: Array<TemplateProviderDetail> (immutable)
│    │  └ types
│    │     ├[+]  type CfnStackParameter
│    │     │  ├      documentation: A key-value pair representing a parameter used in the CloudFormation stack.
│    │     │  │      name: CfnStackParameter
│    │     │  └ properties
│    │     │     ├ Key: string (required)
│    │     │     └ Value: string (required)
│    │     ├[+]  type CfnTemplateProviderDetail
│    │     │  ├      documentation: Details about a CloudFormation template provider configuration and associated provisioning information.
│    │     │  │      name: CfnTemplateProviderDetail
│    │     │  └ properties
│    │     │     ├ Parameters: Array<CfnStackParameter>
│    │     │     ├ RoleARN: string
│    │     │     ├ TemplateName: string (required)
│    │     │     └ TemplateURL: string (required)
│    │     └[+]  type TemplateProviderDetail
│    │        ├      documentation: Details about a template provider configuration and associated provisioning information.
│    │        │      name: TemplateProviderDetail
│    │        └ properties
│    │           └ CfnTemplateProviderDetail: CfnTemplateProviderDetail (required)
│    └[~]  resource AWS::SageMaker::Space
│       └ types
│          └[~] type SpaceSettings
│            └ properties
│               ├[+] RemoteAccess: string
│               └[+] SpaceManagedResources: string
├[~] service aws-ssm
│ └ resources
│    └[~]  resource AWS::SSM::PatchBaseline
│       └ properties
│          └[+] AvailableSecurityUpdatesComplianceStatus: string
├[~] service aws-timestream
│ └ resources
│    └[~]  resource AWS::Timestream::InfluxDBInstance
│       └ properties
│          ├ AllocatedStorage: - integer (immutable)
│          │                   + integer
│          └ DbStorageType: - string (immutable)
│                           + string
├[~] service aws-transfer
│ └ resources
│    └[~]  resource AWS::Transfer::Server
│       └ properties
│          └[+] IpAddressType: string
└[~] service aws-wisdom
  └ resources
     ├[~]  resource AWS::Wisdom::MessageTemplate
     │  ├ properties
     │  │  └[+] MessageTemplateAttachments: Array<MessageTemplateAttachment>
     │  └ types
     │     └[+]  type MessageTemplateAttachment
     │        ├      documentation: Information about the message template attachment.
     │        │      name: MessageTemplateAttachment
     │        └ properties
     │           ├ AttachmentId: string
     │           ├ AttachmentName: string (required)
     │           └ S3PresignedUrl: string (required)
     └[+]  resource AWS::Wisdom::QuickResponse
        ├      name: QuickResponse
        │      cloudFormationType: AWS::Wisdom::QuickResponse
        │      documentation: Creates an Amazon Q in Connect quick response.
        │      tagInformation: {"tagPropertyName":"Tags","variant":"standard"}
        ├ properties
        │  ├ ContentType: string
        │  ├ KnowledgeBaseArn: string (required, immutable)
        │  ├ Name: string (required)
        │  ├ Channels: Array<string>
        │  ├ Content: QuickResponseContentProvider (required)
        │  ├ Description: string
        │  ├ GroupingConfiguration: GroupingConfiguration
        │  ├ IsActive: boolean
        │  ├ Language: string
        │  ├ ShortcutKey: string
        │  └ Tags: Array<tag>
        ├ attributes
        │  ├ QuickResponseId: string
        │  ├ QuickResponseArn: string
        │  ├ Status: string
        │  └ Contents: QuickResponseContents
        └ types
           ├ type GroupingConfiguration
           │ ├      documentation: The configuration information of the grouping of Amazon Q in Connect users.
           │ │      name: GroupingConfiguration
           │ └ properties
           │    ├ Criteria: string (required)
           │    └ Values: Array<string> (required)
           ├ type QuickResponseContentProvider
           │ ├      documentation: The container quick response content.
           │ │      name: QuickResponseContentProvider
           │ └ properties
           │    └ Content: string
           └ type QuickResponseContents
             ├      documentation: The content of the quick response stored in different media types.
             │      name: QuickResponseContents
             └ properties
                ├ Markdown: QuickResponseContentProvider
                └ PlainText: QuickResponseContentProvider
```
chore(release): 2.208.0
5aaa5bc
@aws-cdk-automation aws-cdk-automation requested a review from a team as a code owner July 29, 2025 11:46
@aws-cdk-automation aws-cdk-automation added auto-approve pr/no-squash This PR should be merged instead of squash-merging it labels Jul 29, 2025
@aws-cdk-automation aws-cdk-automation requested a review from a team July 29, 2025 11:46
@github-actions github-actions bot added the p2 label Jul 29, 2025
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Jul 29, 2025
@alvazjor alvazjor added the pr/do-not-merge This PR should not be merged at this time. label Jul 29, 2025
@alvazjor alvazjor removed the pr/do-not-merge This PR should not be merged at this time. label Jul 29, 2025
@mergify
Copy link
Contributor

mergify bot commented Jul 29, 2025

Thank you for contributing! Your pull request will be automatically updated and merged without squashing (do not update manually, and be sure to allow changes to be pushed to your fork).

@aws-cdk-automation
Copy link
Collaborator Author

aws-cdk-automation commented Jul 29, 2025

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
  • Commit ID: 8ea7d29
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify mergify bot merged commit ed7db6f into v2-release Jul 29, 2025
21 checks passed
@mergify mergify bot deleted the bump/2.208.0 branch July 29, 2025 12:34
@github-actions
Copy link
Contributor

github-actions bot commented Jul 29, 2025

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 29, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

@github-actions github-actions[bot] github-actions[bot] approved these changes

Assignees

No one assigned

Labels

auto-approve contribution/core This is a PR that came from AWS. p2 pr/no-squash This PR should be merged instead of squash-merging it

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

10 participants

@aws-cdk-automation @alvazjor @Abogical @ozelalisen @msambol @phuhung273 @leonmk-aws @mazyu36 @Tietew @pahud