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 org.projectlombok:lombok from 1.18.32 to 1.18.34 #126

Closed

Conversation

erpranavjoshi
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 org.projectlombok:lombok from 1.18.32 to 1.18.34.

ℹ️ 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 1 version ahead of your current version.

  • The recommended version was released on 22 days 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 org.projectlombok:lombok from 1.18.32 to 1.18.34.

See this package in maven:
org.projectlombok:lombok

See this project in Snyk:
https://app.snyk.io/org/contentstack-devex/project/91aa54d8-824d-4e38-9e2d-c4e5f96c011d?utm_source=github&utm_medium=referral&page=upgrade-pr
@erpranavjoshi erpranavjoshi requested a review from a team as a code owner July 20, 2024 03:51
Copy link

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-7fd2f4ba7a4ea77216e61a49b6846b58 branch from 0c59e1f to 5dee761 Compare October 23, 2024 11:57
Copy link

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.

1 similar comment
Copy link

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-7fd2f4ba7a4ea77216e61a49b6846b58 branch from 5dee761 to ec23aa4 Compare October 23, 2024 11:59
Copy link

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.

1 similar comment
Copy link

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-7fd2f4ba7a4ea77216e61a49b6846b58 branch from ec23aa4 to a165776 Compare October 24, 2024 10:04
Copy link

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.

1 similar comment
Copy link

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
Copy link
Contributor

Upgrade the package version in this PR : #149.

@reeshika-h reeshika-h closed this Nov 29, 2024
@reeshika-h reeshika-h deleted the snyk-upgrade-7fd2f4ba7a4ea77216e61a49b6846b58 branch November 29, 2024 19:58
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