v6.19.7

Compare Source

v0.0.47

Compare Source

0.0.47 (2024-03-11)

v7.2.0

Compare Source

🚀 Features

• support TS 5.4

• eslint-plugin: [prefer-string-starts-ends-with] add allowSingleElementEquality option

🩹 Fixes

• eslint-plugin: expose *-type-checked-only configs for extension

• eslint-plugin: [member-ordering] report alphabetical sorting for all groups instead of just the first failing group

• eslint-plugin: [no-var-requires, no-require-imports] support template literal

• eslint-plugin: [no-useless-template-literals] detect TemplateLiteral

• eslint-plugin: [no-unnecessary-condition] handle union array and tuple type

• eslint-plugin: [prefer-find] support ternary branches in prefer-find

❤️ Thank You

• Arka Pratim Chaudhuri
• auvred
• Chris Plummer
• Fotis Papadogeorgopoulos
• Josh Goldberg ✨
• Kirk Waiblinger
• Wayne Zhang
• YeonJuan

You can read about our versioning strategy and releases on our website.

v7.2.0

Compare Source

🚀 Features

• support TS 5.4

❤️ Thank You

• Arka Pratim Chaudhuri
• auvred
• Chris Plummer
• Fotis Papadogeorgopoulos
• Josh Goldberg ✨
• Kirk Waiblinger
• Wayne Zhang
• YeonJuan

You can read about our versioning strategy and releases on our website.

v2.133.0

Compare Source

Features

• CLI: improved nested stack diff (#​29172) (135b520)
• codepipeline: change default pipeline type to V2 (under feature flag) (#​29096) (e85231c), closes /github.com/aws/aws-cdk/pull/28538#discussion_r1471761574 /github.com/aws/aws-cdk/blob/main/packages/aws-cdk-lib/aws-codepipeline/lib/pipeline.ts#L492
• ec2: add APPCONFIG and APPCONFIGDATA to InterfaceVpcEndpointAwsService (#​29408) (baaa50c)
• ecs-patterns: support securityGroups in NetworkLoadBalancedFargateService (#​29431) (00e8a7b), closes #​29430 /github.com/aws/aws-cdk/pull/29186#issuecomment-1959231406
• opensearchservice: cold storage option (#​29387) (ce52c7e), closes #​29366
• rds: proxy for mariadb (#​29412) (6fef789), closes #​29402
• stepfunctions-tasks: start glue crawler (#​29016) (5592553), closes #​24188
• update L1 CloudFormation resource definitions (#​29438) (5b910f0)

Bug Fixes

• cli: cdk ls returns stack id instead of stack display name (#​29447) (77189be), closes #​29420
• lambda-nodejs: fixing esbuildArgs to take in account re-specified keys (#​29167) (919d16f), closes #​25385
• stepfunctions: the retry field in CustomState is not iterable (#​29403) (a1fbd51), closes #​29274

Reverts

• prevent changeset diff for non-deployed stacks (#​29485) (fac4a9c), closes #​29394 #​29172

Alpha modules (2.133.0-alpha.0)

v2.132.1

Compare Source

Bug Fixes

• cli: cdk ls returns stack id instead of stack display name (#​29447) (effad1c), closes #​29420

Alpha modules (2.132.1-alpha.0)

v2.1579.0

Compare Source

• feature: Backup: This release introduces a boolean attribute ManagedByAWSBackupOnly as part of ListRecoveryPointsByResource api to filter the recovery points based on ownership. This attribute can be used to filter out the recovery points protected by AWSBackup.
• feature: CodeBuild: AWS CodeBuild now supports overflow behavior on Reserved Capacity.
• feature: Connect: This release adds Hierarchy based Access Control fields to Security Profile public APIs and adds support for UserAttributeFilter to SearchUsers API.
• feature: EC2: Add media accelerator and neuron device information on the describe instance types API.
• feature: KinesisAnalyticsV2: Support for Flink 1.18 in Managed Service for Apache Flink
• feature: SageMaker: Adds m6i, m6id, m7i, c6i, c6id, c7i, r6i r6id, r7i, p5 instance type support to Sagemaker Notebook Instances and miscellaneous wording fixes for previous Sagemaker documentation.
• feature: WorkSpacesThinClient: Removed unused parameter kmsKeyArn from UpdateDeviceRequest

v2.1578.0

Compare Source

• bugfix: IoTRoborunner: Deprecate IoTRoborunner
• feature: EC2InstanceConnect: This release includes a new exception type "SerialConsoleSessionUnsupportedException" for SendSerialConsoleSSHPublicKey API.
• feature: Fis: This release adds support for previewing target resources before running a FIS experiment. It also adds resource ARNs for actions, experiments, and experiment templates to API responses.
• feature: TimestreamInfluxDB: This is the initial SDK release for Amazon Timestream for InfluxDB. Amazon Timestream for InfluxDB is a new time-series database engine that makes it easy for application developers and DevOps teams to run InfluxDB databases on AWS for near real-time time-series applications using open source APIs.

v2.1577.0

Compare Source

• feature: IVSRealTime: adds support for multiple new composition layout configuration options (grid, pip)
• feature: KinesisAnalyticsV2: Support new RuntimeEnvironmentUpdate parameter within UpdateApplication API allowing callers to change the Flink version upon which their application runs.
• feature: S3: This release makes the default option for S3 on Outposts request signing to use the SigV4A algorithm when using AWS Common Runtime (CRT).

v2.1576.0

Compare Source

• feature: Connect: This release increases MaxResults limit to 500 in request for SearchUsers, SearchQueues and SearchRoutingProfiles APIs of Amazon Connect.
• feature: Kafka: Added support for specifying the starting position of topic replication in MSK-Replicator.

v2.1575.0

Compare Source

• feature: CodeStarconnections: Added a sync configuration enum to disable publishing of deployment status to source providers (PublishDeploymentStatus). Added a sync configuration enum (TriggerStackUpdateOn) to only trigger changes.
• feature: MediaPackageV2: This release enables customers to safely update their MediaPackage v2 channel groups, channels and origin endpoints using entity tags.

v0.20.2

Compare Source

• Support TypeScript experimental decorators on abstract class fields (#​3684)

  With this release, you can now use TypeScript experimental decorators on abstract class fields. This was silently compiled incorrectly in esbuild 0.19.7 and below, and was an error from esbuild 0.19.8 to esbuild 0.20.1. Code such as the following should now work correctly:

  // Original code
  const log = (x: any, y: string) => console.log(y)
  abstract class Foo { @​log abstract foo: string }
  new class extends Foo { foo = '' }
  
  // Old output (with --loader=ts --tsconfig-raw={\"compilerOptions\":{\"experimentalDecorators\":true}})
  const log = (x, y) => console.log(y);
  class Foo {
  }
  new class extends Foo {
    foo = "";
  }();
  
  // New output (with --loader=ts --tsconfig-raw={\"compilerOptions\":{\"experimentalDecorators\":true}})
  const log = (x, y) => console.log(y);
  class Foo {
  }
  __decorateClass([
    log
  ], Foo.prototype, "foo", 2);
  new class extends Foo {
    foo = "";
  }();

• JSON loader now preserves __proto__ properties (#​3700)

  Copying JSON source code into a JavaScript file will change its meaning if a JSON object contains the __proto__ key. A literal __proto__ property in a JavaScript object literal sets the prototype of the object instead of adding a property named __proto__, while a literal __proto__ property in a JSON object literal just adds a property named __proto__. With this release, esbuild will now work around this problem by converting JSON to JavaScript with a computed property key in this case:

  // Original code
  import data from 'data:application/json,{"__proto__":{"fail":true}}'
  if (Object.getPrototypeOf(data)?.fail) throw 'fail'
  
  // Old output (with --bundle)
  (() => {
    // <data:application/json,{"__proto__":{"fail":true}}>
    var json_proto_fail_true_default = { __proto__: { fail: true } };
  
    // entry.js
    if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail)
      throw "fail";
  })();
  
  // New output (with --bundle)
  (() => {
    // <data:application/json,{"__proto__":{"fail":true}}>
    var json_proto_fail_true_default = { ["__proto__"]: { fail: true } };
  
    // example.mjs
    if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail)
      throw "fail";
  })();

• Improve dead code removal of switch statements (#​3659)

  With this release, esbuild will now remove switch statements in branches when minifying if they are known to never be evaluated:

  // Original code
  if (true) foo(); else switch (bar) { case 1: baz(); break }
  
  // Old output (with --minify)
  if(1)foo();else switch(bar){case 1:}
  
  // New output (with --minify)
  foo();

• Empty enums should behave like an object literal (#​3657)

  TypeScript allows you to create an empty enum and add properties to it at run time. While people usually use an empty object literal for this instead of a TypeScript enum, esbuild's enum transform didn't anticipate this use case and generated undefined instead of {} for an empty enum. With this release, you can now use an empty enum to generate an empty object literal.

  // Original code
  enum Foo {}
  
  // Old output (with --loader=ts)
  var Foo = /* @​__PURE__ */ ((Foo2) => {
  })(Foo || {});
  
  // New output (with --loader=ts)
  var Foo = /* @​__PURE__ */ ((Foo2) => {
    return Foo2;
  })(Foo || {});

• Handle Yarn Plug'n'Play edge case with tsconfig.json (#​3698)

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

• Work around issues with Deno 1.31+ (#​3682)

  Version 0.20.0 of esbuild changed how the esbuild child process is run in esbuild's API for Deno. Previously it used Deno.run but that API is being removed in favor of Deno.Command. As part of this change, esbuild is now calling the new unref function on esbuild's long-lived child process, which is supposed to allow Deno to exit when your code has finished running even though the child process is still around (previously you had to explicitly call esbuild's stop() function to terminate the child process for Deno to be able to exit).

  However, this introduced a problem for Deno's testing API which now fails some tests that use esbuild with error: Promise resolution is still pending but the event loop has already resolved. It's unclear to me why this is happening. The call to unref was recommended by someone on the Deno core team, and calling Node's equivalent unref API has been working fine for esbuild in Node for a long time. It could be that I'm using it incorrectly, or that there's some reference counting and/or garbage collection bug in Deno's internals, or that Deno's unref just works differently than Node's unref. In any case, it's not good for Deno tests that use esbuild to be failing.

  In this release, I am removing the call to unref to fix this issue. This means that you will now have to call esbuild's stop() function to allow Deno to exit, just like you did before esbuild version 0.20.0 when this regression was introduced.

  Note: This regression wasn't caught earlier because Deno doesn't seem to fail tests that have outstanding setTimeout calls, which esbuild's test harness was using to enforce a maximum test runtime. Adding a setTimeout was allowing esbuild's Deno tests to succeed. So this regression doesn't necessarily apply to all people using tests in Deno.

v1.6.8

Compare Source

Bug Fixes

• AxiosHeaders: fix AxiosHeaders conversion to an object during config merging ([#​6243](https://togithub.com/axios/axios/issue