chore: 🔖 release new versions

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@redocly/cli@1.1.0

Minor Changes

• Added ignoreCase option for tags-alphabetical rule.
• Added join support for OAS 3.1 definitions.
• Added support for Redoc v2.1.2, and aligned the dependencies for both projects.

Patch Changes

• Fixed an issue where the --remove-unused-components option removed used components that were referenced as child objects.
• Updated Redocly config validation.
• Fixed the location pointer when reporting on the no-path-trailing-slash rule.
• Updated minimum required version of Node.js to v14 and removed deprecated packages.
• Updated @redocly/openapi-core to v1.1.0.

@redocly/openapi-core@1.1.0

Minor Changes

• Added ignoreCase option for tags-alphabetical rule.

Patch Changes

• Fixed an issue where the --remove-unused-components option removed used components that were referenced as child objects.
• Updated Redocly config validation.
• Fixed the location pointer when reporting on the no-path-trailing-slash rule.

[adamaltman]

Isn't this a feature?

[tatomyr]

Yes, it is. So it goes as a minor change according to semver: https://semver.org/#summary

[adamaltman]

We're following https://keepachangelog.com/en/1.1.0/ format though. You are changing the format.

[RomanHotsiy]

We're following https://keepachangelog.com/en/1.1.0/ format though.

We are not following it from what I can see. Prior 1.0.0 we were using Features and Fixes.

It was changed on 1.0.0 when we moved to to autogenerated changelog. I think we can adjust our script to keep Features and Fixes instead of Minor Changes and Patch Changes.

@adamaltman @tatomyr what do you think?

[tatomyr]

I believe the current format is widely used by comunity, so it's better to adhere to it as it is.
I think I can add an admonition to the changelog that we've adopted the Changesets approach since v1.0 for the time being. And later we can discuss what to do with the changelog format.

[RomanHotsiy]

I believe the current format is widely used by comunity

Other formats are also used widely by community, see examples:

https://github.com/stoplightio/spectral/blob/develop/CHANGELOG.md
https://github.com/swagger-api/swagger-ui/releases
https://github.com/Redocly/redoc/blob/main/CHANGELOG.md
https://github.com/NativeScript/nx/blob/main/CHANGELOG.md

I prefer Features and Fixes because not everyone is familiar with sevmer terminology.

[tatomyr]

Yes, but I mean it's the default format for Changesets and a lot of projects use it, so I don't expect too much troubles with understanding it. Anyways, we already have entries like this, so the changelog needs to be adjusted (and we can do this after the release). I'm going to set up a call to discuss the format we want to use.

[RomanHotsiy]

This format is nice for libraries but a lot of "products" out there don't use semver language because the audience for products may be a bit different. Do you have any reasons against using Features and Fixes (other than there is a little work required on our end)?

[tatomyr]

Not at all, except it's a default which is always a good idea to stick with.

[github-actions]

Command	Mean [s]	Min [s]	Max [s]	Relative
redocly lint packages/core/src/benchmark/benches/rebilly.yaml	1.277 ± 0.015	1.253	1.306	1.00
redocly-next lint packages/core/src/benchmark/benches/rebilly.yaml	1.302 ± 0.024	1.268	1.338	1.02 ± 0.02

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	75.44%	3793/5028
🟡	Branches	66.3%	2103/3172
🟡	Functions	68.6%	638/930
🟡	Lines	75.59%	3543/4687

Test suite run success

625 tests passing in 91 suites.

Report generated by 🧪jest coverage report action from 173dd41