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

docs(changelog): release 5.9 #1543

Merged
merged 2 commits into from
Mar 8, 2021
Merged

docs(changelog): release 5.9 #1543

merged 2 commits into from
Mar 8, 2021

Conversation

P0lip
Copy link
Contributor

@P0lip P0lip commented Mar 5, 2021

Closes #1507

The changes are already on master, just need to be published.

Checklist

  • Tests added / updated
  • Docs added / updated

Does this PR introduce a breaking change?

  • Yes
  • No

@P0lip P0lip self-assigned this Mar 5, 2021
@P0lip P0lip force-pushed the docs/changelog branch 2 times, most recently from d18a787 to a628291 Compare March 8, 2021 12:27
@@ -26,7 +47,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Falsy OpenAPI `example` fields are validated correctly [#1418](https://github.com/stoplightio/spectral/pull/1418)
- OpenAPI examples in examples is asked to be OpenAPI compliant [#1406](https://github.com/stoplightio/spectral/issues/1406)
- Allow single trailing slash for OpenAPI 3 server url [#1427](https://github.com/stoplightio/spectral/pull/1427)
- Missing non-existing enums in the OpenAPI default [#1429](https://github.com/stoplightio/spectral/pull/1429)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, this is on purpose.
Back in Jan 2021, while I cherry-picking changes, I realized that this particular commit cannot be easily integrated within the existing codebase, hence I had to pull it out.
I updated the changelog file on master branch respectively, but develop was kept untouched.
Now, I'm syncing the changelogs.

@P0lip P0lip requested a review from philsturgeon March 8, 2021 12:30
@P0lip P0lip marked this pull request as ready for review March 8, 2021 12:30
@philsturgeon
Copy link
Contributor

Thanks for doing this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Releasing merged features?
2 participants