chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@pulumi/aws (source)	6.35.0 -> 6.36.0
@pulumi/pulumi (source)	3.116.0 -> 3.116.1
@types/aws-lambda (source)	8.10.137 -> 8.10.138
esbuild	0.21.2 -> 0.21.3
swagger-ui-react	5.17.9 -> 5.17.10

---

Release Notes

pulumi/pulumi-aws (@​pulumi/aws)

v6.36.0

Compare Source

What's Changed

• upstream v5.49.0 by @​flostadler in https://github.com/pulumi/pulumi-aws/pull/3936
• fix: sns topic creation fails in non-standard partitions by @​corymhall in https://github.com/pulumi/pulumi-aws/pull/3932
• fix: wafv2 permanent diff issues (#​3880 #​3306 #​3190 #​3454)
• Enroll aws_wafv2_rule_group in PlanResourceChange by @​flostadler in https://github.com/pulumi/pulumi-aws/pull/3948
• Upgrade pulumi-terraform-bridge to v3.82.0 by @​flostadler in https://github.com/pulumi/pulumi-aws/pull/3929
• Dependencies: terraform converter v1.0.17 by @​t0yv0 in https://github.com/pulumi/pulumi-aws/pull/3923

Full Changelog: pulumi/pulumi-aws@v6.35.0...v6.36.0

pulumi/pulumi (@​pulumi/pulumi)

v3.116.1

Compare Source

3.116.1 (2024-05-15)

Features

• [docs] Resource docs: bump the number of displayed supporting types from 200 to 1000 by default
  #​16185

• [sdk/go] Prefer pluginDownloadURLOverrides over PluginDownloadURL specified in the package
  #​16186

Bug Fixes

• [engine] Fix panic when using pulumi up --refresh --continue-on-error
  #​16184

evanw/esbuild (esbuild)

v0.21.3

Compare Source

• Implement the decorator metadata proposal (#​3760)

  This release implements the decorator metadata proposal, which is a sub-proposal of the decorators proposal. Microsoft shipped the decorators proposal in TypeScript 5.0 and the decorator metadata proposal in TypeScript 5.2, so it's important that esbuild also supports both of these features. Here's a quick example:

  // Shim the "Symbol.metadata" symbol
  Symbol.metadata ??= Symbol('Symbol.metadata')
  
  const track = (_, context) => {
    (context.metadata.names ||= []).push(context.name)
  }
  
  class Foo {
    @​track foo = 1
    @​track bar = 2
  }
  
  // Prints ["foo", "bar"]
  console.log(Foo[Symbol.metadata].names)

  ⚠️ WARNING ⚠️

  This proposal has been marked as "stage 3" which means "recommended for implementation". However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

• Fix bundled decorators in derived classes (#​3768)

  In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:

  class Foo extends Object {
    @​(x => x) foo() {
      return Foo
    }
  }
  console.log(new Foo().foo())

• Fix tsconfig.json files inside symlinked directories (#​3767)

  This release fixes an issue with a scenario involving a tsconfig.json file that extends another file from within a symlinked directory that uses the paths feature. In that case, the implicit baseURL value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for tsconfig.json because it's special-cased (the regular path resolver can't be used because the information inside tsconfig.json is involved in path resolution). Note that this fix no longer applies if the --preserve-symlinks setting is enabled.

swagger-api/swagger-ui (swagger-ui-react)

v5.17.10: Swagger UI v5.17.10 Released!

Compare Source

Bug Fixes

• components: add support for oneOf/anyOf JSON Schema keywords in parameter-row rendering (#​9934) (9037acf), closes #​7912
• oas31: fix initial rendering of the Webhooks section (#​9938) (b5c84f4), closes #​9937

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[github-actions]

💻 Website Preview

The latest changes are available as preview in: https://bedcbccf.fets.pages.dev

[github-actions]

✅ Benchmark Results

     ✓ no_errors{server:node-http,mode:no-schema}
     ✓ expected_result{server:node-http,mode:no-schema}
     ✓ no_errors{server:node-http,mode:json-schema}
     ✓ expected_result{server:node-http,mode:json-schema}
     ✓ no_errors{server:uWebSockets,mode:no-schema}
     ✓ expected_result{server:uWebSockets,mode:no-schema}
     ✓ no_errors{server:uWebSockets,mode:json-schema}
     ✓ expected_result{server:uWebSockets,mode:json-schema}

     checks......................................: 100.00% ✓ 891964      ✗ 0     
     data_received...............................: 81 MB   674 kB/s
     data_sent...................................: 57 MB   472 kB/s
     http_req_blocked............................: avg=1.58µs   min=912ns    med=1.51µs   max=5.57ms   p(90)=1.98µs   p(95)=2.13µs  
     http_req_connecting.........................: avg=12ns     min=0s       med=0s       max=5.18ms   p(90)=0s       p(95)=0s      
     http_req_duration...........................: avg=189.51µs min=127.65µs med=179.03µs max=8.99ms   p(90)=203.25µs p(95)=211.39µs
       { expected_response:true }................: avg=189.51µs min=127.65µs med=179.03µs max=8.99ms   p(90)=203.25µs p(95)=211.39µs
     ✓ { server:node-http,mode:json-schema }.....: avg=202.62µs min=148.69µs med=191.18µs max=7.38ms   p(90)=213.25µs p(95)=220.39µs
     ✓ { server:node-http,mode:no-schema }.......: avg=194.79µs min=138.99µs med=180.73µs max=8.55ms   p(90)=203.42µs p(95)=212.1µs 
     ✓ { server:uWebSockets,mode:json-schema }...: avg=185.19µs min=136.33µs med=176.53µs max=6.89ms   p(90)=197.35µs p(95)=203.37µs
     ✓ { server:uWebSockets,mode:no-schema }.....: avg=176.94µs min=127.65µs med=167.67µs max=8.99ms   p(90)=188.9µs  p(95)=195.52µs
     http_req_failed.............................: 0.00%   ✓ 0           ✗ 445982
     http_req_receiving..........................: avg=23.42µs  min=12.66µs  med=23.05µs  max=6.06ms   p(90)=28.28µs  p(95)=30.14µs 
     http_req_sending............................: avg=8.91µs   min=5.23µs   med=9.06µs   max=815.56µs p(90)=11.83µs  p(95)=12.9µs  
     http_req_tls_handshaking....................: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting............................: avg=157.17µs min=102.56µs med=146.82µs max=8.94ms   p(90)=168.87µs p(95)=176.62µs
     http_reqs...................................: 445982  3716.477307/s
     iteration_duration..........................: avg=264.24µs min=181.61µs med=253.2µs  max=9.65ms   p(90)=279.72µs p(95)=289.78µs
     iterations..................................: 445982  3716.477307/s
     vus.........................................: 1       min=1         max=1   
     vus_max.....................................: 2       min=2         max=2