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

Upgrade swagger-annotations 2.2.2 -> 2.2.3 #263

Merged
merged 1 commit into from
Sep 28, 2022

Conversation

Picnic-Bot
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
io.swagger.core.v3:swagger-annotations compile patch 2.2.2 -> 2.2.3

Release Notes

swagger-api/swagger-core

v2.2.3

Compare Source


  • If you want to rebase/retry this PR, click this checkbox.

@Picnic-Bot
Copy link
Contributor Author

Picnic-Bot commented Sep 28, 2022

Suggested commit message:

Upgrade swagger-annotations 2.2.2 -> 2.2.3 (#263)

See:
- https://github.com/swagger-api/swagger-core/releases/tag/v2.2.3
- https://github.com/swagger-api/swagger-core/compare/v2.2.2...v2.2.3

@Stephan202 Stephan202 added this to the 0.4.0 milestone Sep 28, 2022
@rickie
Copy link
Member

rickie commented Sep 28, 2022

Now the commit would look almost exactly the same as #264. Should we add something like core or v3 in the commit message here?

@Stephan202
Copy link
Member

Now the commit would look almost exactly the same as #264. Should we add something like core or v3 in the commit message here?

Not sure that's worth the hassle; we have the "from" and "to" versions to distinguish the two version lines. (The groupId change was likely done for technical reasons, namely to make sure that the artifacts can co-exist.)

@rickie rickie changed the title Upgrade io.swagger.core.v3:swagger-annotations 2.2.2 -> 2.2.3 Upgrade swagger-annotations 2.2.2 -> 2.2.3 Sep 28, 2022
@rickie rickie merged commit d97a202 into master Sep 28, 2022
@rickie rickie deleted the renovate/io.swagger.core.v3-swagger-annotations-2.x branch September 28, 2022 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants