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.30 to 1.18.32 #106

Closed

Conversation

erpranavjoshi
Copy link

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


Snyk has created this PR to upgrade org.projectlombok:lombok from 1.18.30 to 1.18.32.

ℹ️ 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 a month ago, on 2024-03-20.

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:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@erpranavjoshi erpranavjoshi requested a review from a team as a code owner April 15, 2024 23:44
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.

@harshithad0703
Copy link
Contributor

upgraded in #115

@harshithad0703 harshithad0703 deleted the snyk-upgrade-88ffd9d4f291fbbc6b75af7514566318 branch May 2, 2024 05:29
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.

None yet

3 participants