Skip to content

⬆️ Updates kentaro-m/auto-assign-action action to v2 #849

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
Open
renovate wants to merge 1 commit into
base: master
Choose a base branch
from
Open

⬆️ Updates kentaro-m/auto-assign-action action to v2 #849

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link

@renovate renovate bot commented Feb 3, 2024 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
kentaro-m/auto-assign-action action major v1.1.2 → v2.0.1

Release Notes

kentaro-m/auto-assign-action (kentaro-m/auto-assign-action)

v2.0.1

Compare Source

What's Changed

Full Changelog: kentaro-m/auto-assign-action@v2.0.0...v2.0.1

v2.0.0

Compare Source

What's Changed

Full Changelog: kentaro-m/auto-assign-action@v1.2.6...v2.0.0

v1.2.6

Compare Source

Changes

v1.2.5

Compare Source

What's Changed

Full Changelog: kentaro-m/auto-assign-action@v1.2.4...v1.2.5

v1.2.4

Compare Source

What's Changed

New Contributors

Full Changelog: kentaro-m/auto-assign-action@v1.2.3...v1.2.4

v1.2.3

Compare Source

What's Changed

New Contributors

Full Changelog: kentaro-m/auto-assign-action@v1.2.2...v1.2.3

v1.2.2

Compare Source

What's Changed

New Contributors

Full Changelog: kentaro-m/auto-assign-action@v1.2.1...v1.2.2

v1.2.1

Compare Source

What's Changed

New Contributors

Full Changelog: kentaro-m/auto-assign-action@v1.2.0...v1.2.1

v1.2.0

Compare Source

Changes

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Moscow, 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@auto-assign auto-assign bot requested a review from AlexRogalskiy February 3, 2024 01:48
@github-actions
Copy link

github-actions bot commented Feb 3, 2024

Thanks for opening an issue! Make sure you've followed CONTRIBUTING.md.

@github-actions
Copy link

github-actions bot commented Feb 3, 2024

Hello from PR Helper

Is your PR ready for review and processing? Mark the PR ready by including #pr-ready in a comment.

If you still have work to do, even after marking this ready. Put the PR on hold by including #pr-onhold in a comment.

@github-actions
Copy link

github-actions bot commented Feb 3, 2024

Thanks for the PR!

This section of the codebase is owner by https://github.com/AlexRogalskiy/ - if they write a comment saying "LGTM" then it will be merged.

@renovate
⬆️ Updates kentaro-m/auto-assign-action action to v2
2e01bb5 
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/kentaro-m-auto-assign-action-2.x branch from ea17705 to 2e01bb5 Compare January 17, 2026 03:42
@socket-security
Copy link

socket-security bot commented Jan 17, 2026

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Addedlodash@​4.17.20100838783100
Addedlicense-checker@​25.0.19910010075100
Addedjsonlint@​1.6.31001009075100
Addedremark-preset-davidtheclark@​0.12.0761008078100
Addedjsonpath@​1.1.010010010080100
Addedmarkdown-link-check@​3.8.79910010082100
Addedts-node@​9.1.19710010082100
Addedremark-cli@​9.0.01001009883100
Addedremark-lint-code-block-style@​2.0.110010010084100
Addedremark-lint-ordered-list-marker-value@​2.0.110010010084100
Addedremark-validate-links@​10.0.49910010084100
Addedpretty-quick@​3.1.09910010087100
Addedtypescript@​4.2.39910010010080
Addedts-jest@​26.5.3971009490100
Addedlint-staged@​10.5.49810010090100
Addedsemantic-release@​17.3.9989910097100
Addedprettier@​2.2.1971009898100
Addedtypedoc@​0.20.32981009998100

View full report

@socket-security
Copy link

socket-security bot commented Jan 17, 2026

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn Critical
Critical CVE: npm json-schema is vulnerable to Prototype Pollution

CVE: GHSA-896r-f27r-55mw json-schema is vulnerable to Prototype Pollution (CRITICAL)

Affected versions: < 0.4.0

Patched version: 0.4.0

From: package-lock.json → npm/@semantic-release/npm@7.0.10 → npm/jest-circus@26.6.3 → npm/coveralls@3.1.0 → npm/jest@26.6.3 → npm/markdown-link-check@3.8.7 → npm/json-schema@0.2.3

ℹ Read more on: This package | This alert | What is a critical CVE?

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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/json-schema@0.2.3. 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.

Warn Critical
Critical CVE: Prototype Pollution in npm minimist

CVE: GHSA-xvch-5gv4-984h Prototype Pollution in minimist (CRITICAL)

Affected versions: >= 1.0.0 < 1.2.6; < 0.2.4

Patched version: 1.2.6

From: package-lock.json → npm/editorconfig-checker@3.3.0 → npm/folio@0.3.18 → npm/conventional-changelog-cli@2.1.1 → npm/@semantic-release/npm@7.0.10 → npm/license-checker@25.0.1 → npm/remark-cli@9.0.0 → npm/eslint-import-resolver-typescript@2.4.0 → npm/eslint-plugin-import@2.22.1 → npm/jest-circus@26.6.3 → npm/coveralls@3.1.0 → npm/jest@26.6.3 → npm/ts-jest@26.5.3 → npm/typedoc@0.20.32 → npm/@semantic-release/release-notes-generator@9.0.1 → npm/minimist@1.2.5

ℹ Read more on: This package | This alert | What is a critical CVE?

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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/minimist@1.2.5. 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.

Warn Critical
Critical CVE: Arbitrary Code Execution in npm underscore

CVE: GHSA-cf4h-3jhx-xvhq Arbitrary Code Execution in underscore (CRITICAL)

Affected versions: >= 1.3.2 < 1.12.1

Patched version: 1.12.1

From: package-lock.json → npm/jsonpath@1.1.0 → npm/jsonlint@1.6.3 → npm/underscore@1.7.0

ℹ Read more on: This package | This alert | What is a critical CVE?

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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/underscore@1.7.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.

Warn High
Obfuscated code: npm npm is 94.0% likely obfuscated

Confidence: 0.94

Location: Package overview

From: package-lock.json → npm/@semantic-release/npm@7.0.10 → npm/npm@6.14.11

ℹ Read more on: This package | This alert | What is obfuscated code?

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 not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/npm@6.14.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.

Warn High
Obfuscated code: npm safer-buffer is 94.0% likely obfuscated

Confidence: 0.94

Location: Package overview

From: package-lock.json → npm/@semantic-release/npm@7.0.10 → npm/jest-circus@26.6.3 → npm/coveralls@3.1.0 → npm/jest@26.6.3 → npm/markdown-link-check@3.8.7 → npm/safer-buffer@2.1.2

ℹ Read more on: This package | This alert | What is obfuscated code?

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 not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/safer-buffer@2.1.2. 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.

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@AlexRogalskiy AlexRogalskiy Awaiting requested review from AlexRogalskiy

Assignees

No one assigned

Labels

npm dependencies review-required

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant