Skip to content

fix(deps): update go modules (major) #441

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
Open
red-hat-konflux wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update go modules (major) #441

red-hat-konflux wants to merge 1 commit into from

Conversation

@red-hat-konflux
Copy link
Contributor

@red-hat-konflux red-hat-konflux bot commented Jan 7, 2026

This PR contains the following updates:

Package Change Age Confidence
github.com/gdamore/tcell/v2 v2.9.0 -> v3.0.6 age confidence
github.com/netsampler/goflow2 v1.3.7 -> v2.2.6 age confidence
go.yaml.in/yaml/v2 v2.4.2 -> v3.0.4 age confidence
gopkg.in/evanphx/json-patch.v4 v4.12.0 -> v5.9.11 age confidence

Warning

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

Release Notes

gdamore/tcell (github.com/gdamore/tcell/v2)

v3.0.6: Version 3.0.6 Bug Fix Release

Compare Source

This address some minor bug fixes, and it reduces some of the writing we do to the terminal when changing attributes and using color.

Most of the rest of the commits in this release are related to improving test coverage, and enhancing the mock terminal backend.
Note that the very useless SimScreen has been removed, as the MockBackend is far more functional.

Also some demos have moved from _demos to demos -- and they are now verified in the CI/CD. We will be doing this with the rest of the demos over time.

What's Changed

Full Changelog: gdamore/tcell@v3.0.5...v3.0.6

v3.0.5: Version 3.0.5 Bug Fix and Refactor Release

Compare Source

This release is principally a bug fix release, but we also took this opportunity to remove the views sub-package.

This is technically a breaking change, but we don't think anyone has converted to v3 and is using the views package, and we meant to to do this as part of v3 originally.

The content that was in the views package might be introduced in another repository later, if desired. (If you were using the views package and miss it, please let us know! We'd be happy to resurrect it in another sub package.)

What's Changed

Full Changelog: gdamore/tcell@v3.0.4...v3.0.5

v3.0.4: Version 3.0.4 Bug Fix Release (Includes Breaking Change)

Compare Source

This release contains one important bug fix (for Control-J reporting on legacy terminals), and some refactoring intended to
make feature detection and reporting better. There is a breaking change here in the TTY API, but we don't think anyone has adopted the v3 version of this yet, which is why we felt we could make this change.

What's Changed

Full Changelog: gdamore/tcell@v3.0.3...v3.0.4

v3.0.3: Version 3.0.3 Bug Fix Release

Compare Source

What's Changed

Full Changelog: gdamore/tcell@v3.0.2...v3.0.3

v3.0.2: Version 3.0.2 Bug Fix Release

Compare Source

What's Changed

  • fix(windows): remove incorrect +1 from console dimension calculations by @​ayn2op in #​890

New Contributors

Full Changelog: gdamore/tcell@v3.0.1...v3.0.2

v3.0.1: Version 3.0.1 Bug Fix Release

Compare Source

One very unfortunate bug with key handling (capital letters not working) was found just after we released 3.0.0.

This release also adds some accessors which should have been in 3.0.0 but weren't. Technically this probably should have been a minor release, but we don't think anyone is likely to have started using 3.0.0 for real (particularly with the nasty bug we fixed), so we decided not to make it a minor release.

With this direct Attributes use is no longer recommended. Use the accessors on Style instead.

What's Changed

New Contributors

Full Changelog: gdamore/tcell@v3.0.0...v3.0.1

v3.0.0: Version 3.0.0 Major Release

Compare Source

Version 3 is a major new release. It introduces improvements in the event handling,
richer support for more keys and modifier reports, more functionality out of the box, desktop notification support,
simpler APIs for emitting strings directly to the screen, and numerous bug fixes.

Every Tcell version 2 application will need some modifications to work with Tcell version 3.
See the CHANGESv3.md document for more information.

Full Changelog: gdamore/tcell@v2.13.0...v3.0.0

v2.13.5: Version 2.13.5 Bug Fix Release

Compare Source

This fixes a regression where Control-J was being reported as KeyEnter.

Full Changelog: gdamore/tcell@v2.13.4...v2.13.5

v2.13.4: Version 2.13.4 Bug Fix

What's Changed

(Note that v2.13.3 was accidentally tagged on the wrong branch -- it had the same content, but the git history
was wrong -- we've deleted the tag.)

Note that folks relying on KeyBacktab will find that the regression where on some terminals it became KeyTab+ModShift is now fixed.

Full Changelog: gdamore/tcell@v2.13.2...v2.13.4

v2.13.2: Version 2.13.2 Bug Fix Release

Compare Source

This fixes a problem that affected some applications on Windows (wrong terminal dimensions due to
an off-by-one error.)

Full Changelog: gdamore/tcell@v2.13.1...v2.13.2

v2.13.1: Version 2.13.1 Bug Fix Release

Compare Source

This fixes a bug decoding certain control keys ([, ], )

v2.13.0: Version 2.13 Bug Fix and Minor Feature Release

Compare Source

What's Changed

Full Changelog: gdamore/tcell@v2.12.2...v2.13.0

v2.12.2: Version 2.12.2 Bug Fix Release

Compare Source

This fixes a problem with certain emoji sequences.

Full Changelog: gdamore/tcell@v2.12.1...v2.12.2

v2.12.1: Version 2.12.1 Bug Fix Release

Compare Source

There was some fallout from all the recent design changes. This should fix the main known issues. It also fixes a long
standing issue in the views package.

What's Changed

Full Changelog: gdamore/tcell@v2.12.0...v2.12.1

v2.12.0: Version 2.12 Feature Release

Compare Source

Building on the work of v2.11, this includes the win32 input mode design, and new string accessors for cells.
This should be a big quality of life improvement for folks working with simple tcell apps.

What's Changed

Full Changelog: gdamore/tcell@v2.11.0...v2.12.0

v2.11.0: Version 2.11.0 Bug Fix Release

Compare Source

This is mostly bug fixes for the previous release. It does however involve a complete redesign of the input subsystem,
which is why we bumped the minor number.

What's Changed

Full Changelog: gdamore/tcell@v2.10.0...v2.11.0

v2.10.0: Version 2.10.0 Feature Release

Compare Source

The main change here was introduction of Kitty keyboard protocol support (CSI-u).

What's Changed

New Contributors

Full Changelog: gdamore/tcell@v2.9.0...v2.10.0

netsampler/goflow2 (github.com/netsampler/goflow2)

v2.2.6

Compare Source

v2.2.5

Compare Source

v2.2.4

Compare Source

v2.2.3

Compare Source

v2.2.2

Compare Source

v2.2.1

Compare Source

v2.2.0

Compare Source

v2.1.5

Compare Source

v2.1.4

Compare Source

v2.1.3

Compare Source

v2.1.2

Compare Source

v2.1.1

Compare Source

v2.1.0

Compare Source

v2.0.0

Compare Source

yaml/go-yaml (go.yaml.in/yaml/v2)

v3.0.4

Compare Source

v3.0.3

Compare Source

v3.0.2

Compare Source

v3.0.1

Compare Source

v3.0.0

Compare Source

v2.4.3

Compare Source

evanphx/json-patch (gopkg.in/evanphx/json-patch.v4)

v5.9.11

Compare Source

What's Changed

Full Changelog: evanphx/json-patch@v5.9.10...v5.9.11

v5.9.10

Compare Source

What's Changed

New Contributors

Full Changelog: evanphx/json-patch@v5.9.0...v5.9.10

v5.9.0

Compare Source

What's Changed

Full Changelog: evanphx/json-patch@v5.8.1...v5.9.0

v5.8.1: Fix API breakage

Compare Source

This PR fixes Operation containing a reference to internal/json and breaking the ability to manually compose one. This restores that ability using a type alias.

Full Changelog: evanphx/json-patch@v5.8.0...v5.8.1

v5.8.0: Blargh Phixs and Empathyprovements

Compare Source

This release fixes a few stray panics, addresses large number accuracy, and improves performance!

What's Changed

Full Changelog: evanphx/json-patch@v5.7.0...v5.8.0

v5.7.0: The 2023 Release

Compare Source

What's Changed

New Contributors

Full Changelog: evanphx/json-patch@v5.6.0...v5.7.0

v5.6.0: Bug fixes

Compare Source

What's Changed

New Contributors

Full Changelog: evanphx/json-patch@v5.5.0...v5.6.0

v5.5.0: Better null handling

Compare Source

This incorporates a few fixes related to how nulls are handles in array's and objects.

v5.3.0: Fix zero sized document crash

Compare Source

This fixes a crash bug where submitted an empty slice as the document would panic.

v5.2.0

Compare Source

v5.1.0

Compare Source

v5.0.0: Proper Go modules release

Compare Source

This release has a proper /v5 directory, unlike the previous releases that did not have a /v4 dir. Thanks to @​BenTheElder for getting this sorted out!

v4.13.0

Compare Source

Remove github.com/pkg/errors dependency

Configuration

📅 Schedule: Branch creation - On day 7 of the month, every 3 months ( * * 7 */3 * ) (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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

@red-hat-konflux
fix(deps): update go modules
eeeb98a 
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux bot added the dependencies Pull requests that update a dependency file label Jan 7, 2026
@red-hat-konflux
Copy link
Contributor Author

red-hat-konflux bot commented Jan 7, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum
Command failed: mod upgrade --mod-name=github.com/gdamore/tcell/v2 -t=3
could not load package: err: exit status 1: stderr: go: inconsistent vendoring in /tmp/renovate/repos/github/netobserv/network-observability-cli:
	github.com/gdamore/tcell/v2@v2.8.1: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	github.com/gdamore/tcell/v3@v3.0.6: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	github.com/lucasb-eyer/go-colorful@v1.3.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	github.com/netsampler/goflow2/v2@v2.2.6: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	github.com/prometheus/client_golang@v1.23.2: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	github.com/xdg-go/scram@v1.2.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	golang.org/x/net@v0.47.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	golang.org/x/sys@v0.39.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	golang.org/x/term@v0.38.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	golang.org/x/text@v0.32.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	golang.org/x/tools@v0.39.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	google.golang.org/protobuf@v1.36.11: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	gopkg.in/evanphx/json-patch.v5@v5.9.11: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	github.com/gdamore/tcell/v2@v2.9.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
	github.com/lucasb-eyer/go-colorful@v1.2.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
	github.com/prometheus/client_golang@v1.23.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
	github.com/xdg-go/scram@v1.1.2: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
	golang.org/x/net@v0.43.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
	golang.org/x/sys@v0.35.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
	golang.org/x/term@v0.34.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
	golang.org/x/text@v0.28.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
	golang.org/x/tools@v0.36.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
	google.golang.org/protobuf@v1.36.10: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod

	To ignore the vendor directory, use -mod=readonly or -mod=mod.
	To sync the vendor directory, run:
		go mod vendor

@openshift-ci
Copy link

openshift-ci bot commented Jan 7, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign memodi for approval. For more information see the Code Review Process.

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

Details 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
Copy link

openshift-ci bot commented Jan 7, 2026

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

I'm waiting for a netobserv 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.

Details

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

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file needs-ok-to-test

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant