Skip to content

Conversation

@tf-security
Copy link
Contributor

snyk-top-banner

Snyk has created this PR to upgrade @actions/core from 1.2.6 to 1.11.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 16 versions ahead of your current version.

  • The recommended version was released a year ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Improper Input Validation
SNYK-JS-ACTIONSCORE-2980270
69 No Known Exploit

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade @actions/core from 1.2.6 to 1.11.1.

See this package in yarn:
@actions/core

See this project in Snyk:
https://app.snyk.io/org/typeform/project/ed4eb8b1-7458-41c7-a22b-f01a8679fec6?utm_source=github&utm_medium=referral&page=upgrade-pr
@tf-security tf-security requested a review from a team as a code owner October 29, 2025 14:19
@tf-security
Copy link
Contributor Author

tf-security commented Oct 29, 2025

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Licenses 0 0 0 0 0 issues
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@gitstream-cm
Copy link

gitstream-cm bot commented Oct 29, 2025

This PR is missing a Jira ticket reference in the title or description.
Please add a Jira ticket reference to the title or description of this PR.

@gitstream-cm
Copy link

gitstream-cm bot commented Oct 29, 2025

🥷 Code experts: No results found

No code experts were identified for the files in this pull request based on git blame analysis.

This may occur when:

  • Files are new or have limited commit history
  • Git authors aren't mapped to current team members
  • Analysis thresholds need adjustment

If you expected to see expert suggestions, consider:

  • Reviewing your config.user_mapping settings

  • Adjusting the gt/lt parameters in your action

  • Verifying files have sufficient commit history

To learn more about /:\gitStream - Visit our Docs

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants