-
Couldn't load subscription status.
- Fork 0
Update dependency io.swagger:swagger-annotations to v1.6.16 #90
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
Open
renovate
wants to merge
1
commit into
develop
Choose a base branch
from
renovate/swagger-annotations-version
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3d28ff5 to
e0605b6
Compare
e0605b6 to
83f0e0c
Compare
83f0e0c to
451dddf
Compare
451dddf to
0c701a7
Compare
0c701a7 to
a7f1ccf
Compare
a7f1ccf to
afd1cbc
Compare
afd1cbc to
0e06794
Compare
0e06794 to
d857c66
Compare
d857c66 to
02c22f3
Compare
02c22f3 to
5f05614
Compare
5f05614 to
f44f831
Compare
f44f831 to
5baa75b
Compare
5baa75b to
a8c7f96
Compare
a8c7f96 to
3247f52
Compare
3247f52 to
60aa08b
Compare
60aa08b to
1695f55
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.5.4->1.6.16Release Notes
swagger-api/swagger-core (io.swagger:swagger-annotations)
v1.6.16: Swagger-core 1.6.16 released!Compare Source
What's Changed
Full Changelog: swagger-api/swagger-core@v1.6.15...v1.6.16
v1.6.15: Swagger-core 1.6.15 released!Compare Source
What's Changed
Full Changelog: swagger-api/swagger-core@v1.6.14...v1.6.15
v1.6.14: Swagger-core 1.6.14 released!Compare Source
What's Changed
Full Changelog: swagger-api/swagger-core@v1.6.13...v1.6.14
v1.6.13: Swagger-core 1.6.13 released!Compare Source
What's Changed
kotlin.Deprecatedas a deprecated operation by @sokomishalov in #4463New Contributors
Full Changelog: swagger-api/swagger-core@v1.6.12...v1.6.13
v1.6.12: Swagger-core 1.6.12 released!Compare Source
What's Changed
Full Changelog: swagger-api/swagger-core@v1.6.11...v1.6.12
v1.6.11: Swagger-core 1.6.11 released!Compare Source
What's Changed
Full Changelog: swagger-api/swagger-core@v1.6.10...v1.6.11
v1.6.10: Swagger-core 1.6.10 released!Compare Source
What's Changed
New Contributors
Full Changelog: swagger-api/swagger-core@v1.6.9...v1.6.10
v1.6.9: Swagger-core 1.6.9 released!Compare Source
What's Changed
Full Changelog: swagger-api/swagger-core@v1.6.8...v1.6.9
v1.6.8: Swagger-core 1.6.8 released!Compare Source
What's Changed
Full Changelog: swagger-api/swagger-core@v1.6.7...v1.6.8
v1.6.7: Swagger-core 1.6.7 released!Compare Source
What's Changed
Full Changelog: swagger-api/swagger-core@v1.6.6...v1.6.7
v1.6.6: Swagger-core 1.6.6 released!Compare Source
What's Changed
Full Changelog: swagger-api/swagger-core@v1.6.5...v1.6.6
v1.6.5: Swagger-core 1.6.5 released!Compare Source
What's Changed
Full Changelog: swagger-api/swagger-core@v1.6.4...v1.6.5
v1.6.4: Swagger-core 1.6.4 released!Compare Source
What's Changed
Full Changelog: swagger-api/swagger-core@v1.6.3...v1.6.4
v1.6.3: Swagger-core 1.6.3 released!Compare Source
v1.6.2: Swagger-core 1.6.2 released!Compare Source
v1.6.1: Swagger-core 1.6.1 released!Compare Source
v1.6.0: Swagger-core 1.6.0 released!Compare Source
NOTE: since version
1.6.0java 7 is not supported.v1.5.24: Swagger-core 1.5.24 released!Compare Source
ApiModel.value(#3292)v1.5.23: Swagger-core 1.5.23 released!Compare Source
minor release bumping jackson to 2.9.9 (#3246) and fixing a bug related to
@JsonSerializeprocessing (#3264)v1.5.22: Swagger-core 1.5.22 released!Compare Source
v1.5.21: Swagger-core 1.5.21 released!Compare Source
Minor bug fix release implementing/fixing the following:
v1.5.20: Swagger-core 1.5.20 released!Compare Source
Updates master branch to Swagger 2.0 / OpenAPI 3.0 code; 1.5.X code has been moved from master to 1.5 branch where 1.5.X code development/maintenance will continue (#2787)
Add missing properties to Model (#2768)
Fix security scheme name/key resolving (#2767)
Fix missing enum in converted response schema (#2790)
Allows setting operation deprecated to false (#2782)
Fix name resolution in enums (#2707)
Allows custom typename resolving (#2121)
Fixed override issue on property
collectionFormatpart of annotation@ApiImplicitParam(#2800)Response example support (#2319)
v1.5.19: Swagger-core 1.5.19 released!Compare Source
Notable features
ApiModelPropertyfieldaccessModewhich replacesreadOnly(deprecated) to allow setting readOnly both astrueandfalseinApiModelPropertyannotation. (#2379)Current behaviour (without usage of
accessMode) is left unaltered to maintain backward compatibility.See this test for a usage example.
Bug fixes
operationId(#2433)v1.5.18: Swagger-core 1.5.18 released!Compare Source
Mainly bug fix release implementing/fixing the following:
v1.5.17: Swagger-core 1.5.17 released!Compare Source
Minor release fixing a couple of issues and adding extensions to model property:
v1.5.16: Swagger-core 1.5.16 released!Compare Source
Minor release that upgrades a couple of dependency to deal with their respective security vulnerabilities. See #2275 for more details.
v1.5.15: Swagger-core 1.5.15 released!Compare Source
Tiny but important fix required for swagger-parser-1.0.30 (#2254)
Don't be shy to pick it up though! Tiny fixes can be important too...
v1.5.14: Swagger Core 1.5.14 ReleasedCompare Source
Looking for OpenAPI 3.0 spec support? Jump in here:
https://github.com/swagger-api/swagger-core/tree/feature/3.0.0-rc1
v1.5.14 adds a few features and fixes a few boo-boos.
New features:
@JsonSerializeAsannotation #2147.equalsand.hashcode#2168Fixes:
setRequired(...)method inModelImpl#2167v1.5.13Compare Source
v1.5.12: Swagger-core 1.5.12 ReleasedCompare Source
Happy Holidays!!! Here's a gift from the Swagger Team.
We've updated Jackson to
2.8.4in 1.5.12! This brings better performance, security, and bigger numbers to swagger-core.This release replaces
swagger-core-1.5.11, which was released with an issue affecting swagger parser.As with always, there are many good things in this version
Enhancements:
multipleOf#1907@ApiImplicitParamsat class level #1926typeandformatin annotations #1973, #2034, #2035vendorExtensions #2020readOnly,allowEmptyValue,collectionFormatfields in annotations #2054, #2055minimum,maximumbooleanenum support (as iftrue|falsewasn't enough) #2058Fixes:
nullvs.falsefor default boolean value #1827operationIdvalues with inheritance #1959v1.5.11Compare Source
v1.5.10: Swagger-Core 1.5.10 Released!Compare Source
Notable changes
(see also specific sample java-jersey-jaxrs-multi-use-basepath)
(see example for decorator and annotated resource)
Notable bug fixes
v1.5.9: Swagger-Core 1.5.9 Released!Compare Source
Upgrade notes
1.5.8 introduced a change of behavior to the resource scanning which ended up reading unintended resources. This change was reverted to the way it was before, only with a cleaner scanning of sub resources. The table below describes what will be scanned and what will be skipped:
@Api@Path@Api(hidden=true)@Api(hidden=true)@Path@Api(hidden=true) scanAllResources@ApiscanAllResources@Api@Path@PathscanAllResources@ApisubresourceThe wiki has been updated with the details.
Notable changes
Notable bug fixes
v1.5.8: Swagger-Core 1.5.8 Released!Compare Source
Upgrade notes:
@ApiOperation,@Api,@Producesand@Consumesannotations; previously these values would be treated as single consume/produce e.g.in previous version would result in:
With current behavior it will generate:
/swaggerand/swagger.{type:json|yaml}JAX-RS endpoints provided by two separate resources, andio.swagger.jaxrs.listing.ApiListingResourceprovides only/swagger.{type:json|yaml}endpoint and no longer both/swagger(with Accept headerapplication/jsonorapplication/yaml) and/swagger.{type:json|yaml}/swaggerendpoint is provided byio.swagger.jaxrs.listing.AcceptHeaderApiListingResourceIf package scanning for providers is used, behavior remains the same (
AcceptHeaderApiListingResourceis in the same package and gets scanned), otherwiseAcceptHeaderApiListingResourcemust be added to scanned classes.see also wiki
io.swagger.jersey.listing.ApiListingResourceJSONno longer provides/swagger.{type:json|yaml}endpointRelated to JAX-RS endpoints change above,
usage of Jersey2
io.swagger.jersey.listing.ApiListingResourceJSONshould be replaced byio.swagger.jaxrs.listing.ApiListingResource(or package scanningio.swagger.jaxrs.listing);ApiListingResourceJSONno longer provides/swaggerand/swagger.{type:json|yaml}; it provides only/endpoint.Notable features
@PATCH,@GET...etc annotations (#1643)@ProducesAnnotation are ignored in Accept header (#1609)@ApiResponseat class level (#1382)Notable bug fixes
v1.5.7: Swagger-Core 1.5.7 Released!Compare Source
This release provides new functionality for lower-level integration with Swagger and resolves compatibility issues in some deployments where
@Providerscanning is not configurable.Upgrade notes:
swagger-jaxrsmodule. This made configuration of the JSON mapper easy and consistent with what is provided for rendering the swagger json/yaml definitions. Because some deployments need a different mapper configuration, this was causing problems and was removed. If you were relying on theJacksonJsonProviderin theio.swagger.jaxrs.jsonpackage, please either copy the logic of this file from the 1.5.6 tag or create your own provider!@Apiand@Pathparameters. The commit8921f2ffixes this, but may create issues for those taking advantage of those "bugs". If you are using subresources, please verify that it's behaving how you like after upgrading to 1.5.7.Notable features
Notable bug fixes
v1.5.6: Swagger-Core 1.5.6 Released!Compare Source
This release includes a minor fix to address a bug with defaultValues (#1568)
v1.5.5: Swagger-Core 1.5.5 Released!Compare Source
This release includes minor fixes to models and example value support.
Notable features
byte,binaryproperties (#1578)Notable bug fixes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.