Repository navigation
chore(release): bump tooling to v0.11.1 - #525
Merged
Merged
Conversation
rartych
approved these changes
Nov 9, 2026
Kevsy
approved these changes
Nov 9, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What type of PR is this?
repository management
What this PR does / why we need it:
Cuts the
0.11.1(patch) release: bumpsVERSION.yaml, adds thev0.11.1CHANGELOG.mdsection, and updates the README tag example. Consolidates the 5 PRs merged tomainsincev0.11.0(the security scheme rules S-041 to S-043 from #523, the Release Automation canary paths from #477, and three/validationdependency bumps); see the CHANGELOG section for the list.Which issue(s) this PR fixes:
Part of #524
Special notes for reviewers:
The base (
3efbcf4) has the Validation Regression canary green (12/12 ReleaseTest, 6/6 CommonalitiesTest), and the new fixture branchregression/r4.3-broken-spec-security-schemepasses the runner. The Release Automation Regression canary is green atb321503(#477), and no release automation file changed onmainsince.redocly bundleoutput was compared across the release's@redocly/clirange (2.64.1 to 2.72.1) over the API definitions of 67 API repositories: 99 of 104 files are byte-identical, the other 5 fail identically under both versions on spec-side bundler errors.Changelog input
Additional documentation
This section can be blank.