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

NO-JIRA: chore(deps): update dependency mkdocs-mermaid2-plugin to v1 #5684

Open
wants to merge 1 commit into
base: release-4.15
Choose a base branch
from

Conversation

red-hat-konflux[bot]
Copy link
Contributor

This PR contains the following updates:

Package Update Change
mkdocs-mermaid2-plugin major ==0.6.0 -> ==1.2.1

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


Release Notes

fralau/mkdocs-mermaid2-plugin (mkdocs-mermaid2-plugin)

v1.2.1

Compare Source

  • Added: a test framework with MkDocs-Test and pytest
  • Changed: migrated from setup.py to pyproject.toml

v1.1.1

Compare Source

  • Fixed: Bug with local javascript library

v1.1.0

Compare Source

  • Added: Parameter javascript in config file for optionally specifying the
    URL or path of the Mermaid javascript library.

  • Changed: Parameter extra_javascript in config file is DEPRECATED,
    for optionally specifying the URL or path of the Mermaid javascript library

  • Changed: Updated documentation.

v1.0.8

Compare Source

  • Fixed: Arguments of config file not taken into consideration,
    for mermaid.js version > 10 (#​82)

v1.0.7

Compare Source

v1.0.6

Compare Source

v1.0.5

Compare Source

v1.0.1

Compare Source


Configuration

📅 Schedule: Branch creation - "after 5am on saturday" (UTC), 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

To execute skipped test pipelines write comment /ok-to-test.

This PR has been generated by MintMaker (powered by Renovate Bot).

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@openshift-ci openshift-ci bot requested review from enxebre and sjenning February 22, 2025 16:29
@openshift-ci openshift-ci bot added area/documentation Indicates the PR includes changes for documentation needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. and removed do-not-merge/needs-area labels Feb 22, 2025
Copy link
Contributor

openshift-ci bot commented Feb 22, 2025

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@bryan-cox
Copy link
Member

/ok-to-test
/area ci-tooling
/retitle NO-JIRA: chore(deps): update dependency mkdocs-mermaid2-plugin to v1
/approve
/lgtm

@openshift-ci openshift-ci bot changed the title chore(deps): update dependency mkdocs-mermaid2-plugin to v1 NO-JIRA: chore(deps): update dependency mkdocs-mermaid2-plugin to v1 Feb 24, 2025
@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. area/ci-tooling Indicates the PR includes changes for CI or tooling labels Feb 24, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 24, 2025
@openshift-ci-robot
Copy link

@red-hat-konflux[bot]: This pull request explicitly references no jira issue.

In response to this:

This PR contains the following updates:

Package Update Change
mkdocs-mermaid2-plugin major ==0.6.0 -> ==1.2.1

[!WARNING]
Some dependencies could not be looked up. Check the warning logs for more information.


Release Notes

fralau/mkdocs-mermaid2-plugin (mkdocs-mermaid2-plugin)

v1.2.1

Compare Source

  • Added: a test framework with MkDocs-Test and pytest
  • Changed: migrated from setup.py to pyproject.toml

v1.1.1

Compare Source

  • Fixed: Bug with local javascript library

v1.1.0

Compare Source

  • Added: Parameter javascript in config file for optionally specifying the
    URL or path of the Mermaid javascript library.

  • Changed: Parameter extra_javascript in config file is DEPRECATED,
    for optionally specifying the URL or path of the Mermaid javascript library

  • Changed: Updated documentation.

v1.0.8

Compare Source

  • Fixed: Arguments of config file not taken into consideration,
    for mermaid.js version > 10 (#​82)

v1.0.7

Compare Source

v1.0.6

Compare Source

v1.0.5

Compare Source

v1.0.1

Compare Source


Configuration

📅 Schedule: Branch creation - "after 5am on saturday" (UTC), 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

To execute skipped test pipelines write comment /ok-to-test.

This PR has been generated by MintMaker (powered by Renovate Bot).

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Feb 24, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 24, 2025
Copy link
Contributor

openshift-ci bot commented Feb 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bryan-cox, red-hat-konflux[bot]

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 24, 2025
Copy link
Contributor

openshift-ci bot commented Feb 24, 2025

@red-hat-konflux: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/images 4144611 link unknown /test images

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 1693d53 and 2 for PR HEAD 4144611 in total

1 similar comment
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 1693d53 and 2 for PR HEAD 4144611 in total

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 24, 2025
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/ci-tooling Indicates the PR includes changes for CI or tooling area/documentation Indicates the PR includes changes for documentation jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants