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

Update dependency @redocly/cli to ^1.18.1 (main) #189401

Merged
merged 2 commits into from
Jul 29, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 29, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@redocly/cli ^1.18.0 -> ^1.18.1 age adoption passing confidence

Release Notes

Redocly/redocly-cli (@​redocly/cli)

v1.18.1

Compare Source

Patch Changes
  • Allowed the theme.openapi configuration option to accept settings specific to Redoc 2.x and earlier.
  • Fixed an issue in the OpenAPI spec rule where dependentSchemas was parsed as an array.
    It is now correctly parsed as a map.
  • Fixed bundling of $refs inside patternProperties.
  • Updated AsyncAPI v2 typings to abide by JSON Schema draft-07 specification.
  • Updated @​redocly/openapi-core to v1.18.1.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added backport:all-open Backport to all branches that could still receive a release release_note:skip Skip the PR/issue when compiling release notes Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc labels Jul 29, 2024
@renovate renovate bot requested a review from a team July 29, 2024 14:32
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

Copy link
Contributor

@TinaHeiligers TinaHeiligers left a comment

Choose a reason for hiding this comment

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

LGTM

@afharo
Copy link
Member

afharo commented Jul 29, 2024

/ci

1 similar comment
@TinaHeiligers
Copy link
Contributor

/ci

Copy link
Contributor Author

renovate bot commented Jul 29, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@afharo
Copy link
Member

afharo commented Jul 29, 2024

/ci

@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@TinaHeiligers TinaHeiligers merged commit b49373f into main Jul 29, 2024
36 checks passed
@TinaHeiligers TinaHeiligers deleted the renovate/main-openapi-spec branch July 29, 2024 19:04
@kibanamachine
Copy link
Contributor

💔 All backports failed

Status Branch Result
7.17 Backport failed because of merge conflicts
8.15 Backport failed because of merge conflicts

You might need to backport the following PRs to 8.15:
- Upgrade EUI to v95.3.0 (#187342)
- Update dependency @launchdarkly/node-server-sdk to ^9.4.7 (main) (#187807)
- Update dependency @redocly/cli to ^1.17.0 (main) (#187765)

Manual backport

To create the backport manually run:

node scripts/backport --pr 189401

Questions ?

Please refer to the Backport tool documentation

@TinaHeiligers
Copy link
Contributor

cc @afharo failing backports.

@afharo
Copy link
Member

afharo commented Jul 29, 2024

I don't think that we need to backport these... maybe @jloleysens can confirm.

@TinaHeiligers
Copy link
Contributor

I don't think that we need to backport these

I hope not, conflicts in both targeted branches and we have to backport manually.

@jloleysens
Copy link
Contributor

TBH I strongly doubt this needed to be backported.

@afharo
Copy link
Member

afharo commented Jul 30, 2024

TBH I strongly doubt this needed to be backported.

Cool! Here's the PR to change the backport tags in renovate: #189471

@afharo afharo added backport:skip This commit does not require backporting and removed backport:all-open Backport to all branches that could still receive a release labels Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v8.16.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants