Skip to content

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

Open
cu-infra-svc-git wants to merge 1 commit intomainfrom
renovate/all-minor-patch
Open

chore(deps): update all non-major dependencies#41
cu-infra-svc-git wants to merge 1 commit intomainfrom
renovate/all-minor-patch

Conversation

@cu-infra-svc-git
Copy link
Copy Markdown
Contributor

@cu-infra-svc-git cu-infra-svc-git commented Sep 8, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-plugin-prettier ^5.5.4 → ^5.5.5 age adoption passing confidence
jsii-diff (source) ^1.113.0 → ^1.127.0 age adoption passing confidence
jsii-pacmak (source) ^1.113.0 → ^1.127.0 age adoption passing confidence
jsii-release ^0.2.1013 → ^0.2.1039 age adoption passing confidence
prettier (source) ^3.6.2 → ^3.8.1 age adoption passing confidence
ts-jest (source) ^29.4.1 → ^29.4.9 age adoption passing confidence

Release Notes

prettier/eslint-plugin-prettier (eslint-plugin-prettier)

v5.5.5

Compare Source

Patch Changes
aws/jsii (jsii-diff)

v1.127.0

Compare Source

Bug Fixes
  • jsii-pacmak: remove GOSUMDB=off from Go target (#​5044) (0dbfb03)
  • spec: bundle validators to inline ajv runtime dependencies (#​5040) (f423bb6)
  • spec: pre-compile JSON schema validators at build time (#​5039) (43f0ec3)

v1.126.0

Compare Source

Features
Bug Fixes
  • jsii-pacmak: toString() on anonymous classes does not call JavaScript implementation (#​5027) (d6a243b)

v1.125.0

Compare Source

Bug Fixes
  • jsii-pacmak: --mvn-* arguments aren't passed through (#​5018) (68642d1)

v1.124.0

Compare Source

Bug Fixes
  • jsii-pacmak: Maven resolve-ranges command is missing repo settings (#​5015) (ec8ecf9)

v1.123.0

Compare Source

Bug Fixes
  • java-runtime: dependency ranges make Maven download too many files (#​5005) (ecdd223)
  • jsii-pacmak: collection-of-union arguments in static functions break compilation (#​5012) (2970397)
  • jsii-pacmak: underscore arguments conflict in Java (#​5011) (638b546)

v1.122.0

Compare Source

Bug Fixes

v1.121.0

Compare Source

Features
  • jsii-reflect: add parent assembly reference to Submodule (#​4992) (1232932)
  • jsii-reflect: track directory and package.json for Assembly (#​4991) (3232edf)
Bug Fixes
  • jsii-pacmak: compilation fails if a type is named "Object" (#​4990) (6a5fc58)
  • jsii-pacmak: inheritance between nested types fails (#​4993) (d5009c5)

v1.120.0

Compare Source

Bug Fixes

v1.119.0

Compare Source

Features
Bug Fixes
  • jsii-pacmak: Python interfaces sometimes violate MRO (#​4973) (cfb6580)
  • jsii-reflect: advertise jsii-query via bin entry of package.json (#​4974) (b6c0a35)

v1.118.0

Compare Source

Features
Bug Fixes

v1.117.0

Compare Source

Features
  • support class covariant overrides in kernel, tools and docs (#​4925) (cf4a0b6)
Bug Fixes
  • jsii-reflect: statically guarantee JsiiFeature subset (#​4956) (17bf498)

v1.116.0

Compare Source

Bug Fixes
  • type intersections don't work for Java class builders (#​4945) (8f6ecd9)

v1.115.0

Compare Source

Features
Bug Fixes

v1.114.1

Compare Source

Features
cdklabs/publib (jsii-release)

v0.2.1039

Compare Source

0.2.1039 (2026-03-30)

Bug Fixes

v0.2.1038

Compare Source

0.2.1038 (2026-03-23)

Bug Fixes

v0.2.1037

Compare Source

0.2.1037 (2026-03-16)

Bug Fixes

v0.2.1036

Compare Source

0.2.1036 (2026-03-09)

Bug Fixes

v0.2.1035

Compare Source

0.2.1035 (2026-03-02)

Bug Fixes

v0.2.1034

Compare Source

0.2.1034 (2026-02-23)

Bug Fixes

v0.2.1033

Compare Source

0.2.1033 (2026-02-17)

Bug Fixes

v0.2.1032

Compare Source

0.2.1032 (2026-02-09)

Bug Fixes

v0.2.1031

Compare Source

0.2.1031 (2026-02-02)

Bug Fixes

v0.2.1030

Compare Source

0.2.1030 (2026-01-26)

Bug Fixes

v0.2.1029

Compare Source

0.2.1029 (2026-01-19)

Bug Fixes

v0.2.1028

Compare Source

0.2.1028 (2026-01-12)

Bug Fixes

v0.2.1027

Compare Source

0.2.1027 (2026-01-05)

Bug Fixes

v0.2.1026

Compare Source

0.2.1026 (2025-12-31)

Features
  • Added logic to turn off trusted publishing when the string is false (#​1755) (49fc6c5)
Bug Fixes

v0.2.1025

Compare Source

0.2.1025 (2025-10-20)

Bug Fixes

v0.2.1024

Compare Source

0.2.1024 (2025-10-13)

Bug Fixes

v0.2.1023

Compare Source

0.2.1023 (2025-10-06)

Bug Fixes

v0.2.1022

Compare Source

0.2.1022 (2025-09-30)

Features
  • nuget: add trusted publisher support with OIDC authentication (#​1727) (b99b8a2)

v0.2.1021

Compare Source

0.2.1021 (2025-09-29)

Bug Fixes

v0.2.1020

Compare Source

0.2.1020 (2025-09-24)

Features
  • golang: optimize git operations for large repositories (#​1725) (d54a856)

v0.2.1019

Compare Source

0.2.1019 (2025-09-22)

Bug Fixes

v0.2.1018

Compare Source

0.2.1018 (2025-09-16)

Bug Fixes

v0.2.1017

Compare Source

0.2.1017 (2025-09-16)

Bug Fixes

v0.2.1016

Compare Source

0.2.1016 (2025-09-15)

Bug Fixes

v0.2.1015

Compare Source

0.2.1015 (2025-09-08)

Bug Fixes

v0.2.1014

Compare Source

0.2.1014 (2025-09-01)

Bug Fixes
prettier/prettier (prettier)

v3.8.1

Compare Source

diff

Include available printers in plugin type declarations (#​18706 by @​porada)
// Input
import * as prettierPluginEstree from "prettier/plugins/estree";

// Prettier 3.8.0
// Property 'printers' does not exist on type 'typeof import("prettier/plugins/estree")'. ts(2339)
prettierPluginEstree.printers.estree; //=> any

// Prettier 3.8.1
prettierPluginEstree.printers.estree; //=> Printer
prettierPluginEstree.printers["estree-json"]; //=> Printer

v3.8.0

Compare Source

diff

🔗 Release Notes

v3.7.4

Compare Source

diff

LWC: Avoid quote around interpolations (#​18383 by @​kovsu)
<!-- Input -->
<div foo={bar}>   </div>

<!-- Prettier 3.7.3 (--embedded-language-formatting off) -->
<div foo="{bar}"></div>

<!-- Prettier 3.7.4 (--embedded-language-formatting off) -->
<div foo={bar}></div>
TypeScript: Fix comment inside union type gets duplicated (#​18393 by @​fisker)
// Input
type Foo = (/** comment */ a | b) | c;

// Prettier 3.7.3
type Foo = /** comment */ (/** comment */ a | b) | c;

// Prettier 3.7.4
type Foo = /** comment */ (a | b) | c;
TypeScript: Fix unstable comment print in union type comments (#​18395 by @​fisker)
// Input
type X = (A | B) & (
  // comment
  A | B
);

// Prettier 3.7.3 (first format)
type X = (A | B) &
  (// comment
  A | B);

// Prettier 3.7.3 (second format)
type X = (
  | A
  | B // comment
) &
  (A | B);

// Prettier 3.7.4
type X = (A | B) &
  // comment
  (A | B);

v3.7.3

Compare Source

diff

API: Fix prettier.getFileInfo() change that breaks VSCode extension (#​18375 by @​fisker)

An internal refactor accidentally broke the VSCode extension plugin loading.

v3.7.2

Compare Source

diff

JavaScript: Fix string print when switching quotes (#​18351 by @​fisker)
// Input
console.log("A descriptor\\'s .kind must be \"method\" or \"field\".")

// Prettier 3.7.1
console.log('A descriptor\\'s .kind must be "method" or "field".');

// Prettier 3.7.2
console.log('A descriptor\\\'s .kind must be "method" or "field".');
JavaScript: Preserve quote for embedded HTML attribute values (#​18352 by @​kovsu)
// Input
const html = /* HTML */ ` <div class="${styles.banner}"></div> `;

// Prettier 3.7.1
const html = /* HTML */ ` <div class=${styles.banner}></div> `;

// Prettier 3.7.2
const html = /* HTML */ ` <div class="${styles.banner}"></div> `;
TypeScript: Fix comment in empty type literal (#​18364 by @​fisker)
// Input
export type XXX = {
  // tbd
};

// Prettier 3.7.1
export type XXX = { // tbd };

// Prettier 3.7.2
export type XXX = {
  // tbd
};

v3.7.1

Compare Source

diff

API: Fix performance regression in doc printer (#​18342 by @​fisker)

Prettier 3.7.0 can be very slow when formatting big files, the regression has been fixed.

v3.7.0

Compare Source

diff

🔗 Release Notes

kulshekhar/ts-jest (ts-jest)

v29.4.9

Compare Source

Please refer to CHANGELOG.md for details.

v29.4.8

Compare Source

v29.4.7

Compare Source

Features

v29.4.6

Compare Source

Bug Fixes

v29.4.5

Compare Source

Bug Fixes
  • allow filtering modern module warning message with diagnostic code (c290d4d), , closes #​5013

v29.4.4

Compare Source

Bug Fixes

v29.4.3

Compare Source

Bug Fixes

v29.4.2

Compare Source

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 2am on Monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, 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 Renovate Bot.

@codecov
Copy link
Copy Markdown

codecov bot commented Sep 8, 2025 •
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (efc8d5e) to head (62396c3).

Additional details and impacted files 
@@            Coverage Diff            @@
##              main       #41   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines          142       142           
  Branches         4         4           
=========================================
  Hits           142       142

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 2 times, most recently from c49708a to 9e24be5 Compare September 16, 2025 00:36
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 4 times, most recently from 964c5fd to ee6ffef Compare September 23, 2025 00:36
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 3 times, most recently from 9a9a4db to 06d60ba Compare October 1, 2025 00:42
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 2 times, most recently from 3835b06 to d365800 Compare October 13, 2025 00:40
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 2 times, most recently from db48c64 to 5fca1a6 Compare October 15, 2025 00:38
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 3 times, most recently from 3e24155 to cb7c9f8 Compare October 28, 2025 00:37
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 3 times, most recently from ea5902e to 6651cdb Compare November 6, 2025 00:39
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 3 times, most recently from a4763cf to c9ff553 Compare December 8, 2025 00:41
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 2 times, most recently from eed2ebe to 2678622 Compare December 11, 2025 00:42
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch from 8eed549 to d6bc63c Compare January 6, 2026 00:43
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 3 times, most recently from 6d78926 to f89e035 Compare January 13, 2026 00:39
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 2 times, most recently from 0032ec9 to ca13b70 Compare January 22, 2026 00:44
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 2 times, most recently from 6379b62 to 4f88a90 Compare January 29, 2026 00:49
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch from 4f88a90 to 9bbce51 Compare February 3, 2026 00:52
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 2 times, most recently from b165dcd to 21bfa07 Compare February 17, 2026 00:52
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 2 times, most recently from 9812fac to 45c8f29 Compare March 3, 2026 00:52
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 2 times, most recently from 42c928f to 2e4f022 Compare March 10, 2026 00:48
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 2 times, most recently from f848e0a to 2c429cd Compare March 24, 2026 00:49
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch 3 times, most recently from 62396c3 to 7e3b357 Compare April 1, 2026 21:36
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch from 7e3b357 to 5c37eba Compare April 7, 2026 00:58
@cu-infra-svc-git cu-infra-svc-git force-pushed the renovate/all-minor-patch branch from 5c37eba to 8c59ee6 Compare April 9, 2026 00:50
@socket-security
Copy link
Copy Markdown

socket-security bot commented Apr 9, 2026

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Block Medium
Recently published: npm @aws-sdk/client-codeartifact published 6 hours ago

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/client-codeartifact@3.1027.0

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/client-codeartifact@3.1027.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/client-cognito-identity published 6 hours ago

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/client-cognito-identity@3.1027.0

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/client-cognito-identity@3.1027.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/core published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/core@3.973.27

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/core@3.973.27. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/credential-provider-cognito-identity published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/credential-provider-cognito-identity@3.972.22

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-provider-cognito-identity@3.972.22. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/credential-provider-env published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/credential-provider-env@3.972.25

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-provider-env@3.972.25. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/credential-provider-http published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/credential-provider-http@3.972.27

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-provider-http@3.972.27. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/credential-provider-ini published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/credential-provider-ini@3.972.29

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-provider-ini@3.972.29. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/credential-provider-login published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/credential-provider-login@3.972.29

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-provider-login@3.972.29. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/credential-provider-node published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/credential-provider-node@3.972.30

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-provider-node@3.972.30. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/credential-provider-process published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/credential-provider-process@3.972.25

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-provider-process@3.972.25. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/credential-provider-sso published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/credential-provider-sso@3.972.29

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-provider-sso@3.972.29. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/credential-provider-web-identity published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/credential-provider-web-identity@3.972.29

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-provider-web-identity@3.972.29. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/credential-providers published 6 hours ago

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/credential-providers@3.1027.0

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-providers@3.1027.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/middleware-host-header published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/middleware-host-header@3.972.9

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/middleware-host-header@3.972.9. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/middleware-logger published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/middleware-logger@3.972.9

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/middleware-logger@3.972.9. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/middleware-recursion-detection published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/middleware-recursion-detection@3.972.10

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/middleware-recursion-detection@3.972.10. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/middleware-user-agent published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/middleware-user-agent@3.972.29

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/middleware-user-agent@3.972.29. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/nested-clients published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/nested-clients@3.996.19

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/nested-clients@3.996.19. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/region-config-resolver published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/region-config-resolver@3.972.11

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/region-config-resolver@3.972.11. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/token-providers published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/token-providers@3.1026.0

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/token-providers@3.1026.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/types published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/types@3.973.7

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/types@3.973.7. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/util-endpoints published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/util-endpoints@3.996.6

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/util-endpoints@3.996.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/util-user-agent-browser published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/util-user-agent-browser@3.972.9

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/util-user-agent-browser@3.972.9. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/util-user-agent-node published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/util-user-agent-node@3.973.15

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/util-user-agent-node@3.973.15. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @aws-sdk/xml-builder published yesterday

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@aws-sdk/xml-builder@3.972.17

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/xml-builder@3.972.17. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
Recently published: npm @smithy/config-resolver published 2 days ago

Location: Package overview

From: pnpm-lock.yaml → npm/jsii-release@0.2.1039 → npm/@smithy/config-resolver@4.4.14

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@smithy/config-resolver@4.4.14. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

See 32 more rows in the dashboard

View full report

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

renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@cu-infra-svc-git