Skip to content
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

chore(deps): update all non-major dependencies #835

Merged
merged 2 commits into from
May 16, 2024
Merged

chore(deps): update all non-major dependencies #835

merged 2 commits into from
May 16, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 3, 2024 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@aws-sdk/client-ec2 (source) 3.556.0 -> 3.577.0 age adoption passing confidence
@aws-sdk/client-ssm (source) 3.556.0 -> 3.577.0 age adoption passing confidence
@aws-sdk/client-sts (source) 3.556.0 -> 3.577.0 age adoption passing confidence
@aws-sdk/types (source) 3.535.0 -> 3.577.0 age adoption passing confidence
@semantic-release/github 10.0.3 -> 10.0.4 age adoption passing confidence
@semantic-release/npm 12.0.0 -> 12.0.1 age adoption passing confidence
@types/lodash (source) 4.17.0 -> 4.17.1 age adoption passing confidence
@types/node (source) 20.12.7 -> 20.12.12 age adoption passing confidence
@typescript-eslint/eslint-plugin (source) 7.8.0 -> 7.9.0 age adoption passing confidence
@typescript-eslint/parser (source) 7.8.0 -> 7.9.0 age adoption passing confidence
dts-bundle-generator 9.4.0 -> 9.5.1 age adoption passing confidence
esbuild 0.20.2 -> 0.21.3 age adoption passing confidence
eslint (source) 9.1.1 -> 9.2.0 age adoption passing confidence
eslint-plugin-jest 28.3.0 -> 28.5.0 age adoption passing confidence
semantic-release 23.0.8 -> 23.1.1 age adoption passing confidence
yarn (source) 4.1.1 -> 4.2.2 age adoption passing confidence

Release Notes

aws/aws-sdk-js-v3 (@​aws-sdk/client-ec2)

v3.577.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ec2

v3.576.0

Compare Source

3.576.0(2024-05-14)
Chores
New Features
  • clients: update client endpoints as of 2024-05-14 (8d305635)
  • client-s3: Updated a few x-id in the http uri traits (dcde25ac)
  • client-connect: Amazon Connect provides enhanced search capabilities for flows & flow modules on the Connect admin website and programmatically using APIs. You can search for flows and flow modules by name, description, type, status, and tags, to filter and identify a specific flow in your Connect instances. (43f9444b)

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

v3.575.0

Compare Source

3.575.0(2024-05-13)
Chores
New Features
  • clients: update client endpoints as of 2024-05-13 (2fd7ca7e)
  • client-eventbridge: Amazon EventBridge introduces KMS customer-managed key (CMK) encryption support for custom and partner events published on EventBridge Event Bus (including default bus) and UpdateEventBus API. (529b5fb6)
  • client-vpc-lattice: This release adds TLS Passthrough support. It also increases max number of target group per rule to 10. (1f626402)

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

v3.574.0

Compare Source

3.574.0(2024-05-10)
New Features
  • clients: update client endpoints as of 2024-05-10 (f98b8d49)
  • client-application-discovery-service: add v2 smoke tests and smithy smokeTests trait for SDK testing (807fcd73)
  • client-sso-oidc: Updated request parameters for PKCE support. (a25b371e)
  • client-greengrassv2: Mark ComponentVersion in ComponentDeploymentSpecification as required. (d56a60ae)
  • client-sagemaker: Introduced support for G6 instance types on Sagemaker Notebook Instances and on SageMaker Studio for JupyterLab and CodeEditor applications. (0f5cee89)
Bug Fixes

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

v3.572.0

Compare Source

3.572.0(2024-05-08)
Chores
Documentation Changes
  • client-fms: The policy scope resource tag is always a string value, either a non-empty string or an empty string. (4f544d7c)
New Features
  • clients: update client endpoints as of 2024-05-08 (1e71a11f)
  • client-sqs: This release adds MessageSystemAttributeNames to ReceiveMessageRequest to replace AttributeNames. (35284e8f)
  • client-polly: Add new engine - generative - that builds the most expressive conversational voices. (daf6bd4c)
  • client-ec2: Adding Precision Hardware Clock (PHC) to public API DescribeInstanceTypes (711a8ff4)
  • client-cognito-identity-provider: Add EXTERNAL_PROVIDER enum value to UserStatusType. (0189ee3a)
  • client-ecr: This release adds pull through cache rules support for GitLab container registry in Amazon ECR. (a05338f5)
Tests

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

v3.569.0

Compare Source

Bug Fixes
  • clients: add deps required by default credential providers (#​6055) (bfa8626)

v3.568.0

Compare Source

3.568.0(2024-05-02)
Chores
Documentation Changes
New Features
  • client-redshift-serverless: Update Redshift Serverless List Scheduled Actions Output Response to include Namespace Name. (044806b1)
  • client-dynamodb: This release adds support to specify an optional, maximum OnDemandThroughput for DynamoDB tables and global secondary indexes in the CreateTable or UpdateTable APIs. You can also override the OnDemandThroughput settings by calling the ImportTable, RestoreFromPointInTime, or RestoreFromBackup APIs. (7a4330dd)
  • client-personalize: This releases ability to delete users and their data, including their metadata and interactions data, from a dataset group. (3c7432b9)
  • client-ec2: This release includes a new API for retrieving the public endorsement key of the EC2 instance's Nitro Trusted Platform Module (NitroTPM). (0903d38f)

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

v3.567.0

Compare Source

3.567.0(2024-05-01)
Chores
Documentation Changes
  • client-ec2: Documentation updates for Amazon EC2. (044d712d)
New Features
  • clients: update client endpoints as of 2024-05-01 (365eb8c3)
  • client-personalize-runtime: This release adds support for a Reason attribute for predicted items generated by User-Personalization-v2. (a68c9997)
  • client-securityhub: Updated CreateMembers API request with limits. (1142738b)
  • client-bedrock-agent: This release adds support for using MongoDB Atlas as a vector store when creating a knowledge base. (93917f77)
  • client-sesv2: Fixes ListContacts and ListImportJobs APIs to use POST instead of GET. (56df20cf)
  • end support for Node.js 14.x (#​6034) (d1964111)

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

v3.565.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ec2

v3.564.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ec2

v3.563.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ec2

v3.562.0

Compare Source

Features
  • client-ec2: Launching capability for customers to enable or disable automatic assignment of public IPv4 addresses to their network interface (6121a23)

v3.561.0

Compare Source

Features
  • client-ec2: This release introduces EC2 AMI Deregistration Protection, a new AMI property that can be enabled by customers to protect an AMI against an unintended deregistration. This release also enables the AMI owners to view the AMI 'LastLaunchedTime' in DescribeImages API. (4fcf9f7)

v3.557.0

Compare Source

Features
  • client-ec2: Documentation updates for Elastic Compute Cloud (EC2). (08bd27c)
aws/aws-sdk-js-v3 (@​aws-sdk/client-ssm)

v3.577.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ssm

v3.576.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ssm

v3.575.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ssm

v3.574.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ssm

v3.572.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ssm

v3.569.0

Compare Source

Bug Fixes
  • clients: add deps required by default credential providers (#​6055) (bfa8626)

v3.568.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ssm

v3.567.0

Compare Source

Features

v3.565.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ssm

v3.564.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ssm

v3.563.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ssm

v3.562.0

Compare Source

Features
  • client-ssm: Add SSM DescribeInstanceProperties API to public AWS SDK. (aef9d12)
aws/aws-sdk-js-v3 (@​aws-sdk/client-sts)

v3.577.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-sts

v3.576.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-sts

v3.575.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-sts

v3.574.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-sts

v3.572.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-sts

v3.569.0

Compare Source

Bug Fixes
  • clients: add deps required by default credential providers (#​6055) (bfa8626)

v3.568.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-sts

v3.567.0

Compare Source

Features

v3.565.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-sts

aws/aws-sdk-js-v3 (@​aws-sdk/types)

v3.577.0

Compare Source

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

v3.575.0

Compare Source

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

v3.567.0

Compare Source

Features
semantic-release/github (@​semantic-release/github)

v10.0.4

Compare Source

Bug Fixes
  • introduce dedicated option for GitHub API endpoint (#​829) (908ff83)
semantic-release/npm (@​semantic-release/npm)

v12.0.1

Compare Source

Bug Fixes
  • deps: update dependency execa to v9 (9ac5ed0)
typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v7.9.0

Compare Source

🩹 Fixes
  • eslint-plugin: [explicit-function-return-types] fix false positive on default parameters
❤️ Thank You
  • Kirk Waiblinger
  • Sheetal Nandi
  • Vinccool96

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

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v7.9.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

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

timocov/dts-bundle-generator (dts-bundle-generator)

v9.5.1: 9.5.1

Compare Source

Fixed

v9.5.0: 9.5.0

Compare Source

Fixed
  • Constants declared by using object/array binding pattern syntax fail the build (see #​315 and #​317)

v9.4.1: 9.4.1

Compare Source

Fixed
  • Fixed issue when because of recursive types some of the types could get removed from the bundle (see #​318 and 897a5d5)
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.

v0.21.2

Compare Source

  • Correct this in field and accessor decorators (#​3761)

    This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:

    const dec = () => function() { this.bar = true }
class Foo { @​dec static foo }
console.log(Foo.bar) // Should be "true"

  • Allow es2023 as a target environment (#​3762)

    TypeScript recently added es2023 as a compilation target, so esbuild now supports this too. There is no difference between a target of es2022 and es2023 as far as esbuild is concerned since the 2023 edition of JavaScript doesn't introduce any new syntax features.

v0.21.1

Compare Source

  • Fix a regression with --keep-names (#​3756)

    The previous release introduced a regression with the --keep-names setting and object literals with get/set accessor methods, in which case the generated code contained syntax errors. This release fixes the regression:

    // Original code
x = { get y() {} }

// Output from version 0.21.0 (with --keep-names)
x = { get y: /* @​__PURE__ */ __name(function() {
}, "y") };

// Output from this version (with --keep-names)
x = { get y() {
} };

v0.21.0

Compare Source

This release doesn't contain any deliberately-breaking changes. However, it contains a very complex new feature and while all of esbuild's tests pass, I would not be surprised if an important edge case turns out to be broken. So I'm releasing this as a breaking change release to avoid causing any trouble. As usual, make sure to test your code when you upgrade.

  • Implement the JavaScript decorators proposal (#​104)

    With this release, esbuild now contains an implementation of the upcoming JavaScript decorators proposal. This is the same feature that shipped in TypeScript 5.0 and has been highly-requested on esbuild's issue tracker. You can read more about them in that blog post and in this other (now slightly outdated) extensive blog post here: https://2ality.com/2022/10/javascript-decorators.html. Here's a quick example:

    const log = (fn, context) => function() {
  console.log(`before ${context.name}`)
  const it = fn.apply(this, arguments)
  console.log(`after ${context.name}`)
  return it
}

class Foo {
  @​log static foo() {
    console.log('in foo')
  }
}

// Logs "before foo", "in foo", "after foo"
Foo.foo()

    Note that this feature is different than the existing "TypeScript experimental decorators" feature that esbuild already implements. It uses similar syntax but behaves very differently, and the two are not compatible (although it's sometimes possible to write decorators that work with both). TypeScript experimental decorators will still be supported by esbuild going forward as they have been around for a long time, are very widely used, and let you do certain things that are not possible with JavaScript decorators (such as decorating function parameters). By default esbuild will parse and transform JavaScript decorators, but you can tell esbuild to parse and transform TypeScript experimental decorators instead by setting "experimentalDecorators": true in your tsconfig.json file.

    Probably at least half of the work for this feature went into creating a test suite that exercises many of the proposal's edge cases: https://github.com/evanw/decorator-tests. It has given me a reasonable level of confidence that esbuild's initial implementation is acceptable. However, I don't have access to a significant sample of real code that uses JavaScript decorators. If you're currently using JavaScript decorators in a real code base, please try out esbuild's implementation and let me know if anything seems off.

    ⚠️ WARNING ⚠️

    This proposal has been in the works for a very long time (work began around 10 years ago in 2014) and it is finally getting close to becoming part of the JavaScript language. 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 decorators may need to be updated as the feature continues to evolve. The decorators proposal is pretty close to its final form but it can and likely will undergo some small behavioral adjustments before it ends up becoming a part of the standard. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

  • Optimize the generated code for private methods

    Previously when lowering private methods for old browsers, esbuild would generate one WeakSet for each private method. This mirrors similar logic for generating one WeakSet for each private field. Using a separate WeakMap for private fields is necessary as their assignment can be observable:

    let it
class Bar {
  constructor() {
    it = this
  }
}
class Foo extends Bar {
  #x = 1
  #y = null.foo
  static check() {
    console.log(#x in it, #y in it)
  }
}
try { new Foo } catch {}
Foo.check()

    This prints true false because this partially-initialized instance has #x but not #y. In other words, it's not true that all class instances will always have all of their private fields. However, the assignment of private methods to a class instance is not observable. In other words, it's true that all class instances will always have all of their private methods. This means esbuild can lower private methods into code where all methods share a single WeakSet, which is smaller, faster, and uses less memory. Other JavaScript processing tools such as the TypeScript compiler already make this optimization. Here's what this change looks like:

    // Original code
class Foo {
  #x() { return this.#x() }
  #y() { return this.#y() }
  #z() { return this.#z() }
}

// Old output (--supported:class-private-method=false)
var _x, x_fn, _y, y_fn, _z, z_fn;
class Foo {
  constructor() {
    __privateAdd(this, _x);
    __privateAdd(this, _y);
    __privateAdd(this, _z);
  }
}
_x = new WeakSet();
x_fn = function() {
  return __privateMethod(this, _x, x_fn).call(this);
};
_y = new WeakSet();
y_fn = function() {
  return __privateMethod(this, _y, y_fn).call(this);
};
_z = new WeakSet();
z_fn = function() {
  return __privateMethod(this, _z, z_fn).call(this);
};

// New output (--supported:class-private-method=false)
var _Foo_instances, x_fn, y_fn, z_fn;
class Foo {
  constructor() {
    __privateAdd(this, _Foo_instances);
  }
}
_Foo_instances = new WeakSet();
x_fn = function() {
  return __privateMethod(this, _Foo_instances, x_fn).call(this);
};
y_fn = function() {
  return __privateMethod(this, _Foo_instances, y_fn).call(this);
};
z_fn = function() {
  return __privateMethod(this, _Foo_instances, z_fn).call(this);
};

  • Fix an obscure bug with lowering class members with computed property keys

    When class members that use newer syntax features are transformed for older target environments, they sometimes need to be relocated. However, care must be taken to not reorder any side effects caused by computed property keys. For example, the following code must evaluate a() then b() then c():

    class Foo {
  [a()]() {}
  [b()];
  static { c() }
}

    Previously esbuild did this by shifting the computed property key forward to the next spot in the evaluation order. Classes evaluate all computed keys first and then all static class elements, so if the last computed key needs to be shifted, esbuild previously inserted a static block at start of the class body, ensuring it came before all other static class elements:

    var _a;
class Foo {
  constructor() {
    __publicField(this, _a);
  }
  static {
    _a = b();
  }
  [a()]() {
  }
  static {
    c();
  }
}

    However, this could cause esbuild to accidentally generate a syntax error if the computed property key contains code that isn't allowed in a static block, such as an await expression. With this release, esbuild fixes this problem by shifting the computed property key backward to the previous spot in the evaluation order instead, which may push it into the extends clause or even before the class itself:

    // Original code
class Foo {
  [a()]() {}
  [await b()];
  static { c() }
}

// Old output (with --supported:class-field=false)
var _a;
class Foo {
  constructor() {
    __publicField(this, _a);
  }
  static {
    _a = await b();
  }
  [a()]() {
  }
  static {
    c();
  }
}

// New output (with --supported:class-field=false)
var _a, _b;
class Foo {
  constructor() {
    __publicField(this, _a);
  }
  [(_b = a(), _a = await b(), _b)]() {
  }
  static {
    c();
  }
}

  • Fix some --keep-names edge cases

    The NamedEvaluation syntax-directed operation in the JavaScript specification gives certain anonymous expressions a name property depending on where they are in the syntax tree. For example, the following initializers convey a name value:

    var foo = function() {}
var bar = class {}
console.log(foo.name, bar.name)

    When you enable esbuild's --keep-names setting, esbuild generates additional code to represent this NamedEvaluation operation so that the value of the name property persists even when the identifiers are renamed (e.g. due to minification).

    However, I recently learned that esbuild's implementation of NamedEvaluation is missing a few cases. Specifically esbuild was missing property definitions, class initializers, logical-assignment operators. These cases should now all be handled:

    var obj = { foo: function() {} }
class Foo0 { foo = function() {} }
class Foo1 { static foo = function() {} }
class Foo2 { accessor foo = function() {} }
class Foo3 { static accessor foo = function() {} }
foo ||= function() {}
foo &&= function() {}
foo ??= function() {}
eslint/eslint (eslint)

v9.2.0

Compare Source

jest-community/eslint-plugin-jest (eslint-plugin-jest)

v28.5.0

Compare Source

Features
  • allow @typescript-eslint/utils v7 as a direct dependency (#​1567) (1476f10)

v28.4.0

Compare Source

Features
  • valid-expect: supporting automatically fixing missing await in some cases (#​1574) (a407098)
semantic-release/semantic-release (semantic-release)

v23.1.1

Compare Source

v23.1.0

Compare Source

yarnpkg/berry (yarn)

v4.2.2

Compare Source

[v4.2.1](https://togithub.com/yarnpkg/berry/compare/9a853e35cfe44d1cbd17b9739f68e90d1c79c96e...bf24f592eb0a7e8ac207387b0d60ea2ac7d66e

Configuration

📅 Schedule: Branch creation - "after 5pm on Friday,every weekend" (UTC), 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.

@renovate renovate bot enabled auto-merge (rebase) May 3, 2024 18:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 13 times, most recently from 8dd8eb7 to 32f824b Compare May 10, 2024 19:13
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 14 times, most recently from 89921df to 3ad170c Compare May 15, 2024 15:26
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 3ad170c to 10a8ac6 Compare May 16, 2024 00:30
@renovate Renovate
Copy link
Contributor Author

renovate bot commented May 16, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@sonarcloud SonarCloud
Copy link

sonarcloud bot commented May 16, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@renovate renovate bot merged commit d855f8a into master May 16, 2024
3 checks passed
@renovate renovate bot deleted the renovate/all-minor-patch branch May 16, 2024 04:29
@hoonoh
Copy link
Owner

hoonoh commented May 16, 2024

🎉 This PR is included in version 1.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
released
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@hoonoh