dependabot[bot] opened a new pull request, #454: URL: https://github.com/apache/plc4x-extras/pull/454
Bumps [github.com/rivo/tview](https://github.com/rivo/tview) from 0.0.0-20241030223020-e34b54cd4c27 to 0.42.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/rivo/tview/releases";>github.com/rivo/tview's releases</a>.</em></p> <blockquote> <h2>Introducing Releases and SemVer</h2> <p>Upon popular demand (<a href="https://redirect.github.com/rivo/tview/issues/788";>#788</a>), we are starting to use semantic versioning in <code>tview</code>. A lot has happened in this repo already so it didn't seem right to start with v0.1.0. A few notes about this decision:</p> <ul> <li>Not every commit will get a new version. Only when I feel that there have not been recent reports of major bugs, I will increase the version and create a new release.</li> <li>This is thus based on the assumption that recent, untagged versions will be used by the community and issues will be reported. Please do both.</li> <li>Consequently, as with any project, a release is not a guarantee that it is bug-free.</li> <li>As the "v0" prefix indicates, we are still in the "alpha" phase. This does not mean that I plan on breaking things. Please refer to the repo's main <a href="https://github.com/rivo/tview?tab=readme-ov-file#backwards-compatibility";>README</a> for details. However, at this point, I am not completely sure that it will be necessary to introduce a breaking change so it'll remain at "v0" for the time being. (Maybe it will remain there forever. You never know.)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/rivo/tview/commits/v0.42.0";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
