Sourced from @​aws-sdk/lib-storage's releases.

v3.658.1

3.658.1(2024-09-25)

Chores

• deps: bump rollup from 3.29.1 to 3.29.5 (#6510) (c5124c11)

Documentation Changes

• client-fsx: Doc-only update to address Lustre S3 hard-coded names. (becefa3a)
• client-ec2: Updates to documentation for the transit gateway security group referencing feature. (7fad2247)
• client-cloudtrail: Doc-only update for CloudTrail network activity events release (in preview) (082bad80)

New Features

• clients: update client endpoints as of 2024-09-25 (cf0e4097)

Bug Fixes

• codegen: preprocess AwsQuery error to shapeId in waiter errorType (#6501) (b92df203)
• clients: allow empty string field values for headers (#6511) (1273ff31)

---

For list of updated packages, view updated-packages.md in assets-3.658.1.zip

v3.658.0

3.658.0(2024-09-24)

New Features

• clients: update client endpoints as of 2024-09-24 (452f091a)
• client-budgets: Releasing minor partitional endpoint updates (80633075)
• client-bedrock: Add support for Cross Region Inference in Bedrock Model Evaluations. (707b3877)
• client-sagemaker: Adding HiddenInstanceTypes and HiddenSageMakerImageVersionAliases attribute to SageMaker API (6b99b6b6)
• client-pinpoint-sms-voice-v2: AWS End User Messaging SMS-Voice V2 has added support for resource policies. Use the three new APIs to create, view, edit, and delete resource policies. (b449c450)
• client-kinesis: This release includes support to add tags when creating a stream (82129957)

Bug Fixes

• core: add compatibility types for submodules (#6509) (3a5d854a)

---

For list of updated packages, view updated-packages.md in assets-3.658.0.zip

v3.657.0

3.657.0(2024-09-23)

... (truncated)

Sourced from @​aws-sdk/lib-storage's changelog.

3.658.1 (2024-09-25)

Bug Fixes

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

3.658.0 (2024-09-24)

Note: Version bump only for package @​aws-sdk/lib-storage

3.657.0 (2024-09-23)

Note: Version bump only for package @​aws-sdk/lib-storage

• ecd9d89 Publish v3.658.1
• 1273ff3 fix(clients): allow empty string field values for headers (#6511)
• f796530 Publish v3.658.0
• b06a8b7 Publish v3.657.0
• See full diff in compare view

Sourced from inquirer's releases.

inquirer@11.1.0

• Now exports base utility Typescript types: import type { Question, DistinctQuestion, Answers } from 'inquirer';

You should use as follow to keep the inference working properly:

const questions = [
    { ... }
] as const satisfies Question[];
// If you're not using inquirer plugins, `Question` could alternatively be replaced by `DistinctQuestion` for stricter checks.

inquirer@11.0.2

• Fix #1555: when behaviour changed unexpectedly when returning a falsy value.

• c07851d Publish
• 0218e93 Chore: Fix prettier/lint-staged failing on unknown files
• 66a675e feat(inquirer): export types Question, DistinctQuestion and Answers (#1559)
• eeffe0c Chore(deps): Bump rollup from 4.21.3 to 4.22.4 in the npm_and_yarn group (#1566)
• 1de6d13 Chore(deps-dev): Bump @​eslint/js from 9.10.0 to 9.11.0 (#1565)
• 5a7cd1a Chore(deps-dev): Bump @​arethetypeswrong/cli from 0.16.2 to 0.16.4 (#1563)
• f719291 Chore(deps-dev): Bump typescript-eslint from 8.5.0 to 8.6.0 (#1564)
• ef45c60 Chore(deps-dev): Bump eslint from 9.10.0 to 9.11.0 (#1562)
• bd45397 Chore(deps): Bump vite from 5.2.8 to 5.4.6 in the npm_and_yarn group (#1558)
• 95674a1 Publish
• Additional commits viewable in compare view

Sourced from esbuild's releases.

v0.24.0

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

• Drop support for older platforms (#3902)

  This release drops support for the following operating system:

  • macOS 10.15 Catalina

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

  Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

  git clone https://github.com/evanw/esbuild.git
  cd esbuild
  go build ./cmd/esbuild
  ./esbuild --version
  

• Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

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

• Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

  TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

• Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

  Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

• Work around more issues with Deno 1.31+ (#3917)

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

  This fix was contributed by @​Joshix-1.

v0.23.1

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

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

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

... (truncated)

Sourced from esbuild's changelog.

0.24.0

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

• Drop support for older platforms (#3902)

  This release drops support for the following operating system:

  • macOS 10.15 Catalina

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

  Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

  git clone https://github.com/evanw/esbuild.git
  cd esbuild
  go build ./cmd/esbuild
  ./esbuild --version
  

• Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

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

• Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

  TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

• Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

  Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

• Work around more issues with Deno 1.31+ (#3917)

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

  This fix was contributed by @​Joshix-1.

0.23.1

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

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

  // Original code
  import fs from 'node:fs'
  fs.open

... (truncated)

• d34e79e publish 0.24.0 to npm
• 045a87f fix #3887: omit dead export warning for default
• 6e049b8 fix #3913: useDefineForClassFields and decorators
• 9c26f98 lower decorators for useDefineForClassFields #3913
• 46fdb68 fix #3898: incorrect cyclic tsconfig.json warning
• b500443 fix #3917: running esbuild cli with deno
• b125e62 run make update-compat-table
• 112b9aa fix #3915: stack overflow with yarn + tsconfig
• ed5a555 wasm: catch and rethrow stack overflows (#3915)
• 11d3196 fix #3902: update go 1.22.5 => 1.23.1
• Additional commits viewable in compare view

Sourced from geckodriver's releases.

Release 4.5.0

• feat: support spawnOpts for geckodriver child process (#552) (3edaf8e)
• chore(deps): bump rollup from 4.21.3 to 4.22.4 (#551) (2b429a4)
• chore(deps-dev): bump @​typescript-eslint/parser from 8.5.0 to 8.6.0 (#548) (c24a4c6)
• chore(deps-dev): bump @​typescript-eslint/eslint-plugin (#549) (6437865)
• chore(deps): bump vite from 5.4.5 to 5.4.6 (#546) (9ad9e72)
• chore(deps-dev): bump husky from 9.1.5 to 9.1.6 (#540) (590a837)
• chore(deps-dev): bump @​types/node from 22.5.4 to 22.5.5 (#543) (e5f91da)
• chore(deps-dev): bump @​vitest/coverage-v8 from 2.0.5 to 2.1.1 (#544) (cc5c1aa)
• chore(deps-dev): bump npm-run-all2 from 6.2.2 to 6.2.3 (#538) (26d8383)
• chore(deps-dev): bump typescript from 5.5.4 to 5.6.2 (#542) (9c97480)
• chore(deps-dev): bump @​typescript-eslint/parser from 8.4.0 to 8.5.0 (#541) (4bd169d)
• chore(deps-dev): bump tsx from 4.19.0 to 4.19.1 (#539) (2e366a9)
• chore(deps-dev): bump @​types/node from 22.5.2 to 22.5.4 (#537) (78502e3)
• chore(deps-dev): bump @​typescript-eslint/parser from 8.3.0 to 8.4.0 (#533) (9f71ec5)
• chore(deps-dev): bump @​typescript-eslint/eslint-plugin (#531) (94aed15)
• chore(deps-dev): bump webdriverio from 9.0.7 to 9.0.9 (#534) (fd6c4a6)
• chore(deps-dev): bump eslint-plugin-import from 2.29.1 to 2.30.0 (#532) (ae42ebd)

• 1bdc27f Release 4.5.0
• 3edaf8e feat: support spawnOpts for geckodriver child process (#552)
• 2b429a4 chore(deps): bump rollup from 4.21.3 to 4.22.4 (#551)
• c24a4c6 chore(deps-dev): bump @​typescript-eslint/parser from 8.5.0 to 8.6.0 (#548)
• 6437865 chore(deps-dev): bump @​typescript-eslint/eslint-plugin (#549)
• 9ad9e72 chore(deps): bump vite from 5.4.5 to 5.4.6 (#546)
• 590a837 chore(deps-dev): bump husky from 9.1.5 to 9.1.6 (#540)
• e5f91da chore(deps-dev): bump @​types/node from 22.5.4 to 22.5.5 (#543)
• cc5c1aa chore(deps-dev): bump @​vitest/coverage-v8 from 2.0.5 to 2.1.1 (#544)
• 26d8383 chore(deps-dev): bump npm-run-all2 from 6.2.2 to 6.2.3 (#538)
• Additional commits viewable in compare view

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