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

chore(deps): update dependency solidiquis/erdtree to v2 #11802

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 26, 2023

Mend Renovate

This PR contains the following updates:

Package Update Change
solidiquis/erdtree major v1.7.1 -> v2.0.0

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.


Release Notes

solidiquis/erdtree

v2.0.0: Release build (v2.0.0)

Compare Source

What's Changed

erdtree v2.0.0 introduces numerous breaking changes as well as a plethora of new features. Most breaking changes are predicated on the fact that
arguments were either renamed, removed, or fundamentally modified. The following is a list of all the PRs that document these changes and feature additions:

Perhaps the most important change to note is that the compiled binary has been renamed from et to erd in order to address the following issue
regarding name collisions with other programs: https://github.com/solidiquis/erdtree/issues/23

For a more comprehensive overview of erdtree v2.0.0, please refer to the README.md.

Full Changelog: solidiquis/erdtree@v1.8.1...v2.0.0

v1.8.1: Release build (v1.8.1)

Compare Source

What's Changed

New Contributors

Author notes

Pair programming with Croissant:

Full Changelog: solidiquis/erdtree@v1.7.1...v1.8.1


Configuration

📅 Schedule: Branch creation - "after 12pm" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 enabled auto-merge (rebase) April 26, 2023 16:02
@renovate renovate bot temporarily deployed to renovate April 26, 2023 16:02 Inactive
@renovate renovate bot force-pushed the renovate/solidiquis-erdtree-2.x branch from f19a090 to d6c0b08 Compare April 26, 2023 16:05
@renovate renovate bot temporarily deployed to renovate April 26, 2023 16:05 Inactive
@renovate renovate bot force-pushed the renovate/solidiquis-erdtree-2.x branch from d6c0b08 to ae517e2 Compare April 26, 2023 16:07
@renovate renovate bot temporarily deployed to renovate April 26, 2023 16:07 Inactive
@renovate renovate bot force-pushed the renovate/solidiquis-erdtree-2.x branch from ae517e2 to f7c904b Compare April 26, 2023 16:10
@renovate renovate bot temporarily deployed to renovate April 26, 2023 16:10 Inactive
@renovate renovate bot force-pushed the renovate/solidiquis-erdtree-2.x branch from f7c904b to 18b8c0d Compare April 26, 2023 20:01
@renovate renovate bot temporarily deployed to renovate April 26, 2023 20:01 Inactive
@renovate renovate bot force-pushed the renovate/solidiquis-erdtree-2.x branch from 18b8c0d to 036c592 Compare April 26, 2023 20:03
@renovate renovate bot temporarily deployed to renovate April 26, 2023 20:03 Inactive
@suzuki-shunsuke
Copy link
Member

auto-merge was automatically disabled April 26, 2023 20:54

Pull request was closed

@suzuki-shunsuke suzuki-shunsuke deleted the renovate/solidiquis-erdtree-2.x branch April 26, 2023 20:54
@renovate
Copy link
Contributor Author

renovate bot commented Apr 26, 2023

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 2.x releases. However, if you upgrade to 2.x manually then Renovate will reenable minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant