Jochen Schalanda

The `-in` flag is supported since [go-junit-report 2.0.0](https://github.com/jstemmer/go-junit-report/releases/tag/v2.0.0). It looks like you're running [go-junit-report 1.0.0](https://github.com/jstemmer/go-junit-report/releases/tag/v1.0.0).

Unfortunately not in this repository, but my fork includes binaries for Darwin and Linux on ARM64: https://github.com/joschi/go-junit-report/releases/tag/v2.2.0

@michael-schnell Thanks for reporting this! I think adding a default for a property is a compatible change and removing it is a breaking change. What do you think?

I think this was originally introduced in https://github.com/OpenAPITools/openapi-diff/issues/136 / https://github.com/OpenAPITools/openapi-diff/issues/137. Happy to discuss whether it still makes sense.

@pmhofman Thanks for reporting this! It looks like an issue with the reference resolution in the upstream project https://github.com/swagger-api/swagger-parser/. Would you mind creating a bug report there and link it...

@michael-schnell Thanks for reporting this! Would you expect removing of the deprecation to be a breaking change or a mere informational message/compatible change?

Sorry, wrong issue.

@jdnvn Thanks for this suggestion! I like the idea, but one issue I see is that `info.version` is a string with no inherent semantics: > version | string | REQUIRED....

@RPS044 None of this looks like it's related to this project. Could you please elaborate on your issue with openapi-diff?

@Hazel-John Thanks for reporting this! We probably have to consider whether the [`minLength` and `maxLength` properties](https://swagger.io/docs/specification/data-models/data-types/#string) are changed in requests or response specifications. What do you think? Property Location Change...