-
Notifications
You must be signed in to change notification settings - Fork 39
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
Upgrade Servlet API 4.0.4 -> 6.0.0 #119
Upgrade Servlet API 4.0.4 -> 6.0.0 #119
Conversation
Suggested commit message:
|
54dfe1b
to
9f45bec
Compare
0b7f434
to
12b946b
Compare
6f580c5
to
452d44d
Compare
5086862
to
b3a754a
Compare
dc67941
to
c78c97f
Compare
f66b173
to
eaa4046
Compare
dde2d26
to
668f271
Compare
3551d61
to
6f4b997
Compare
a984de2
to
da01651
Compare
da01651
to
0db889d
Compare
Looks good. No mutations were possible for these changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Following the changes in #543 the only thing that prevented this build from passing was an update to the test code. I added a commit; I think there's no harm in merging this PR, even though internally we haven't yet upgraded (but we likely will this quarter still).
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
2af8f3c
to
3918fd7
Compare
Looks good. No mutations were possible for these changes. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
This PR contains the following updates:
4.0.4
->6.0.0
Release Notes
eclipse-ee4j/servlet-api
v6.0.0
Compare Source
v5.0.0
Compare Source