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.

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

[Snyk] Upgrade com.slack.api:slack-app-backend from 1.38.0 to 1.39.1 #83

Closed

Conversation

cs-sagarmalve
Copy link

This PR was automatically created by Snyk using the credentials of a real user.


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade com.slack.api:slack-app-backend from 1.38.0 to 1.39.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 5 versions ahead of your current version.

  • The recommended version was released on a month ago.


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.

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 com.slack.api:slack-app-backend from 1.38.0 to 1.39.1.

See this package in maven:
com.slack.api:slack-app-backend

See this project in Snyk:
https://app.snyk.io/org/contentstack-devex/project/d4e249e0-1e7c-480b-9181-5e419e6d80c3?utm_source=github&utm_medium=referral&page=upgrade-pr
@cs-sagarmalve cs-sagarmalve requested a review from a team as a code owner June 5, 2024 01:37
Copy link

github-actions bot commented Jun 5, 2024

We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch.

@reeshika-h reeshika-h force-pushed the snyk-upgrade-a0aa39804358b11c43a05514535ec4de branch 2 times, most recently from b79dcd0 to aa16482 Compare October 17, 2024 07:44
@reeshika-h reeshika-h force-pushed the snyk-upgrade-a0aa39804358b11c43a05514535ec4de branch from aa16482 to 1c5d175 Compare October 17, 2024 08:08
@aravindbuilt aravindbuilt deleted the snyk-upgrade-a0aa39804358b11c43a05514535ec4de branch October 17, 2024 08:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants