fix: Disable no-$ref-siblings rule from required ruleset#95
Merged
Conversation
While it is technically invalid OpenAPI, it is nothing breaking for the developer-portal, so we don't need to fail publishing if there are ref-siblings.
egrimstad
force-pushed
the
fix/disable-no-ref-siblings
branch
from
4a343b9 to
798db01
Compare
rikard-swahn
approved these changes
Feb 27, 2026
egrimstad
pushed a commit
that referenced
this pull request
Feb 27, 2026
🤖 I have created a release *beep* *boop* --- ## [2.2.1](v2.2.0...v2.2.1) (2026-02-27) ### Bug Fixes * Disable no-$ref-siblings rule from required ruleset ([#95](#95)) ([5f8e8b7](5f8e8b7)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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
2 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.
While it is technically invalid in OpenAPI 3.0, it is nothing breaking for the developer-portal, so we don't need to fail publishing if there are ref-siblings.