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.

Sign up for GitHub

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

Jump to bottom

Update dependency @redocly/cli to ^1.16.0 (main) #187033

Merged
merged 3 commits into from
Jun 27, 2024
Merged

Update dependency @redocly/cli to ^1.16.0 (main) #187033

merged 3 commits into from
Jun 27, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 27, 2024 •
edited by afharo
Loading

Mend Renovate

This PR contains the following updates:

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

Release Notes

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

v1.16.0

Compare Source

Minor Changes
  • Users can run the CLI tool behind a proxy by using HTTP_PROXY or HTTPS_PROXY environment variables to configure the proxy settings.
Patch Changes

v1.15.0

Compare Source

Minor Changes
  • Made redocly.yaml validation consistent with the general Redocly config.
Patch Changes
  • Updated Redoc to v2.1.5.
  • Fixed no-invalid-media-type-examples, no-invalid-parameter-examples, and no-invalid-schema-examples rules which allowed falsy example values to pass for any schema.
  • Updated @​redocly/openapi-core to v1.15.0.

v1.14.0

Compare Source

Minor Changes
  • Added the ability to exclude some operations or entire paths from the security-defined rule.
Patch Changes

v1.13.0

Compare Source

Minor Changes
  • Added support for the linting command to output markdown format.
Patch Changes

v1.12.2

Compare Source

Patch Changes

v1.12.1

Compare Source

Patch Changes

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 has been generated by Mend Renovate. View repository job log here.

@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 Jun 27, 2024
@renovate renovate bot requested a review from a team June 27, 2024 00:19
@elasticmachine
Copy link
Contributor

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

@pgayvallet
Copy link
Contributor

/ci

@pgayvallet pgayvallet enabled auto-merge (squash) June 27, 2024 05:51
@pgayvallet
Copy link
Contributor

/ci

@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jun 27, 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.

@pgayvallet
Copy link
Contributor

/ci

@kibana-ci
Copy link
Collaborator

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
enterpriseSearch 2.7MB 2.7MB +129.0B

History

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

@pgayvallet pgayvallet merged commit bacc276 into main Jun 27, 2024
37 of 38 checks passed
@pgayvallet pgayvallet deleted the renovate/main-openapi-spec branch June 27, 2024 09:12
@kibanamachine
Copy link
Contributor

💔 All backports failed

Status Branch Result
❌ 7.17 Backport failed because of merge conflicts
❌ 8.14 Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 187033

Questions ?

Please refer to the Backport tool documentation

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 187033 locally

@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Jun 29, 2024
@pgayvallet pgayvallet added the backport:skip This commit does not require backporting label Jul 2, 2024
@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Jul 2, 2024
@pgayvallet pgayvallet removed the backport:all-open Backport to all branches that could still receive a release label Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@pgayvallet pgayvallet pgayvallet approved these changes

Assignees
No one assigned
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.15.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@elasticmachine @pgayvallet @kibana-ci @kibanamachine