Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.620.0
->3.623.0
3.620.0
->3.623.0
3.620.0
->3.623.0
3.620.0
->3.623.0
1.18.1
->1.19.0
7.17.0
->7.18.0
7.17.0
->7.18.0
9.1.3
->9.1.4
15.2.7
->15.2.8
Release Notes
aws/aws-sdk-js-v3 (@aws-sdk/client-lambda)
v3.623.0
Compare Source
Note: Version bump only for package @aws-sdk/client-lambda
v3.622.0
Compare Source
Note: Version bump only for package @aws-sdk/client-lambda
v3.621.0
Compare Source
Note: Version bump only for package @aws-sdk/client-lambda
3.620.1 (2024-07-29)
Note: Version bump only for package @aws-sdk/client-lambda
v3.620.1
Compare Source
Note: Version bump only for package @aws-sdk/client-lambda
aws/aws-sdk-js-v3 (@aws-sdk/client-secrets-manager)
v3.623.0
Compare Source
Note: Version bump only for package @aws-sdk/client-secrets-manager
v3.622.0
Compare Source
Note: Version bump only for package @aws-sdk/client-secrets-manager
v3.621.0
Compare Source
Note: Version bump only for package @aws-sdk/client-secrets-manager
3.620.1 (2024-07-29)
Note: Version bump only for package @aws-sdk/client-secrets-manager
v3.620.1
Compare Source
Note: Version bump only for package @aws-sdk/client-secrets-manager
aws/aws-sdk-js-v3 (@aws-sdk/client-sqs)
v3.623.0
Compare Source
Note: Version bump only for package @aws-sdk/client-sqs
v3.622.0
Compare Source
Note: Version bump only for package @aws-sdk/client-sqs
v3.621.0
Compare Source
Note: Version bump only for package @aws-sdk/client-sqs
3.620.1 (2024-07-29)
Note: Version bump only for package @aws-sdk/client-sqs
v3.620.1
Compare Source
Note: Version bump only for package @aws-sdk/client-sqs
aws/aws-sdk-js-v3 (@aws-sdk/credential-provider-node)
v3.623.0
Compare Source
Note: Version bump only for package @aws-sdk/credential-provider-node
v3.622.0
Compare Source
Note: Version bump only for package @aws-sdk/credential-provider-node
v3.621.0
Compare Source
Note: Version bump only for package @aws-sdk/credential-provider-node
3.620.1 (2024-07-29)
Note: Version bump only for package @aws-sdk/credential-provider-node
v3.620.1
Compare Source
Note: Version bump only for package @aws-sdk/credential-provider-node
Redocly/redocly-cli (@redocly/cli)
v1.19.0
Compare Source
Minor Changes
Patch Changes
patternProperties
incorrectly caused linting errors due to a missingPatternProperties
node.typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v7.18.0
Compare Source
🩹 Fixes
eslint-plugin: [no-unnecessary-type-assertion] prevent runtime error when asserting a variable declared in default TS lib
eslint-plugin: [unbound-method] report on destructuring in function parameters
eslint-plugin: [no-duplicate-type-constituents] shouldn't report on error types
eslint-plugin: [strict-boolean-expressions] support branded booleans
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v7.18.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.
typicode/husky (husky)
v9.1.4
Compare Source
lint-staged/lint-staged (lint-staged)
v15.2.8
Compare Source
Patch Changes
f0480f0
Thanks @iiroj! - In the previous version the nativegit rev-parse --show-toplevel
command was taken into use for resolving the current git repo root. This version switched the--show-toplevel
flag with--show-cdup
, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.jschild_process
. The new flag returns a path relative to the working directory, avoiding the issue.The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.
Configuration
📅 Schedule: Branch creation - "after 2pm on Saturday" in timezone Europe/Zurich, 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.
This PR was generated by Mend Renovate. View the repository job log.