Skip to content

Update all dependencies#88

Closed
dominikholler wants to merge 1 commit into
kubevirt:mainfrom
dominikholler:renovate/all-dependencies
Closed

Update all dependencies#88
dominikholler wants to merge 1 commit into
kubevirt:mainfrom
dominikholler:renovate/all-dependencies

Conversation

@dominikholler

@dominikholler dominikholler commented May 12, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Type Update Change
cel.dev/expr indirect patch v0.25.1 → v0.25.2
github.com/Masterminds/semver/v3 indirect minor v3.4.0 → v3.5.0
github.com/coreos/go-systemd/v22 indirect minor v22.6.0 → v22.7.0
github.com/fsnotify/fsnotify indirect minor v1.9.0 → v1.10.1
github.com/fxamacker/cbor/v2 indirect patch v2.9.0 → v2.9.2
github.com/google/cel-go indirect minor v0.26.1 → v0.28.0
github.com/google/pprof indirect digest 294ebfa → 92041b7
github.com/onsi/gomega require minor v1.39.1 → v1.40.0
github.com/onsi/gomega indirect minor v1.39.1 → v1.40.0
github.com/prometheus/common indirect patch v0.67.4 → v0.67.5
go.uber.org/zap indirect minor v1.27.1 → v1.28.0
go.yaml.in/yaml/v2 indirect patch v2.4.3 → v2.4.4

Release note

Update dependency cel.dev/expr to v0.25.2

Release note

Update dependency github.com/Masterminds/semver/v3 to v3.5.0

Release note

Update dependency github.com/coreos/go-systemd/v22 to v22.7.0

Release note

Update dependency github.com/fsnotify/fsnotify to v1.10.1

Release note

Update dependency github.com/fxamacker/cbor/v2 to v2.9.2

Release note

Update dependency github.com/google/cel-go to v0.28.0

Release note

Update dependency github.com/google/pprof to v0.0.0-20260507013755-92041b743c96

Release note

Update dependency github.com/onsi/gomega to v1.40.0

Release note

Update dependency github.com/prometheus/common to v0.67.5

Release note

Update dependency go.uber.org/zap to v1.28.0

Release note

Update dependency go.yaml.in/yaml/v2 to v2.4.4

Release Notes

google/cel-spec (cel.dev/expr)

v0.25.2

Compare Source

What's Changed

New Contributors

Full Changelog: cel-expr/cel-spec@v0.25.1...v0.25.2

Masterminds/semver (github.com/Masterminds/semver/v3)

v3.5.0

Compare Source

What's Changed
New Contributors

Full Changelog: Masterminds/semver@v3.4.0...v3.5.0

coreos/go-systemd (github.com/coreos/go-systemd/v22)

v22.7.0

Compare Source

This release fixes an issue with multiple calls to (e.g.) StopUnit, simplifies and improves code and documentation, and adds a few new methods.

What's Changed

New Contributors

Full Changelog: coreos/go-systemd@v22.6.0...v22.7.0

fsnotify/fsnotify (github.com/fsnotify/fsnotify)

v1.10.1

Compare Source

Changes and fixes

  • inotify: don't remove sibling watches sharing a path prefix (#​754)

  • inotify, windows: don't rename sibling watches sharing a path prefix
    (#​755)

v1.10.0

Compare Source

This version of fsnotify needs Go 1.23.

Changes and fixes

  • inotify: improve initialization error message (#​731)

  • inotify: send Rename event if recursive watch is renamed (#​696)

  • inotify: avoid copying event buffers when reading names (#​741)

  • kqueue: skip dangling symlinks (ENOENT) in watchDirectoryFiles, so a bad entry no longer aborts Watcher.Add for the whole directory (#​748)

  • kqueue: drop watches directly in Close() to fix a file descriptor leak when recycling watchers (#​740)

  • windows: fix nil pointer dereference in remWatch (#​736)

  • windows: lock watch field updates against concurrent WatchList to fix a race introduced in v1.9.0 (#​709, #​749)

fxamacker/cbor (github.com/fxamacker/cbor/v2)

v2.9.2

Compare Source

This release refactors and hardens the streaming encoder by adding stricter checks for encoding CBOR indefinite-length data. Other changes include minor bugfixes, defensive checks, and more tests.

Projects that don't use CBOR indefinite-length data may also want to upgrade (summary of prior releases).

The stricter checks in the encoder prevent improper use of the library and bad inputs from producing malformed CBOR indefinite-length data that would be rejected by the decoder.

This release passed fuzz tests (billions of execs) and it is production quality.

What's Changed
  • Reject encoding indefinite-length map with odd item count by @​fxamacker in #​764
  • Reject encoding indefinite-length data item as a chunk inside indefinite-length byte string or text string by @​fxamacker in #​765
  • Make TagSet.Remove a no-op when contentType is nil by @​fxamacker in #​766
  • Refactor indefinite-length encoding and improve chunk validation during encoding by @​fxamacker in #​767
  • Add more tests, fix a nit in unreachable panic message, update docs & ci by @​fxamacker in #​768
CI / GitHub Actions and Docs
🔎 Details...

Full Changelog: fxamacker/cbor@v2.9.1...v2.9.2

v2.9.1

Compare Source

This release includes important bugfixes, defensive checks, improved code quality, and more tests. Although not public, the fuzzer was also improved by adding more fuzz tests.

🐞 Bug fixes related to the keyasint feature

These changes only affect Go struct fields tagged with keyasint:

  • [Decoding] Reject integer keys that exceed math.MaxInt64 when decoding CBOR map to a struct with keyasint field (PR #​757)
  • [Decoding] Prevent string representation of an integer key from matching the struct field tagged by keyasint (PR #​757)
  • [Encoding & Decoding] Deduplicate struct fields with the same normalized keyasint tag values (PR #​757)
🐞 Other bug fixes and defensive checks

Some of the bugs fixed are related to decoding extreme values that cannot be encoded with this library. For example, the decoder checks if epoch time encoded as CBOR float value representing hundreds of billions of years overflows int64(seconds).

NOTE: It is generally good practice to avoid using floating point to store epoch time (even when not using CBOR).

  • [Decoding] Reject decoding epoch time encoded as floats that overflow int64 (PR #​753)
  • [Encoding] Return a cloned slice for an empty RawMessage from RawMessage.MarshalCBOR (PR #​753)
  • [Encoding] Reject encoding nil inside indefinite-length strings (PR #​750)
  • [Diagnostic] Accept valid U+FFFD replacement character (PR #​753)
What's Changed
CI / GitHub Actions and Docs
🔎 Details...

New Contributors

Full Changelog: fxamacker/cbor@v2.9.0...v2.9.1

google/cel-go (github.com/google/cel-go)

v0.28.0

Compare Source

High-Level Changes

  • Enhanced JSON Interoperability: New support for JSON names across the checker, AST, and runtime allows for more seamless data handling when working with JSON-native structures.
  • Improved Developer Tooling: Integration is now smoother thanks to new utilities for converting Go errors into cel.Issues and more descriptive, context-aware error messages.
  • Greater Environment Flexibility: You can now redeclare variables as constants and export parse limit options, providing finer control over how CEL environments are configured and constrained.
  • Native Struct Improvements: Support for mixing CEL and native values within native structs simplifies the handling of complex, hybrid data types.

🚀 Features

  • Add helper method to check whether a function has a singleton binding in #​1266
  • Helper utility for converting a Go error into cel.Issues in #​1267
  • Policy API improvements in #​1268
  • CEL Test usability requirements in #​1269
  • Better context-related error messages in #​1271
  • Sort env.Config values where reasonable in #​1273
  • Support redeclaring variables as constants in NewEnv in #​1275
  • Add support for exporting parse limit options in #​1277
  • Support mixing CEL values and native values in native structs in #​1270
  • Add checker, AST, and type-provider support for JSON names in #​1283
  • JSON field names runtime support in #​1286
  • Optionally include reachable fieldpaths in prompt in #​1285
  • REPL -- cel-spec pb2 and json name support #​1294

🐞 Bug Fixes

  • Fix support for config-based type references in #​1265
  • Check arg kinds in optional.or and .orValue impl in #​1276
  • Bazel fixes for import in #​1278
  • Support zero-value literals in presence test inlining #​1280
  • Cache concatList.Size() to prevent O(N^2) evaluation time #​1291
  • Preserve runtime error node IDs from Resolve #​1290
  • Default enable identifier escaping with backticks #​1295
  • Cap format string precision to prevent memory exhaustion #​1292

🛠️ Maintenance & Internal

  • chore: Migrate gsutil usage to gcloud storage in #​1274
  • Lint fixes for exported function/type comments in #​1279
  • Lint fixes for import in #​1287

Full Changelog: https://github.com/google/cel-go/compare/v0.27.0...v0.28.0-alpha

v0.27.0

Compare Source

Release Summary

This release focuses on improving developer tooling and stability. Key highlights include significant enhancements to the REPL (YAML configuration support and parse-only evaluation), the addition of cost estimation for regex operations, and improved test coverage reporting.

On the stability front, this release addresses race conditions in reference types, improves namespace resolution, and ensures formatting directives align strictly with the CEL specification.

Note: This release includes a breaking change regarding how types are handled as variables. Please review the "Breaking Changes" section below.

⚠ Breaking Changes

Remove types as variables: The logic for handling types has been relaxed to support safe rollout of feature packages which introduce new types whose names may collide with existing variables. Please review your policies if you relied on types behaving strictly as variables in previous versions. PR #​1262

Features & Enhancements

REPL & Tooling

  • YAML Configuration: The REPL now supports reading and writing YAML environment configurations. PR #​1250

  • Parse-Only Mode: Added parse-only evaluation capabilities to the REPL. PR #​1254

  • Test Coverage: Introduced logic for CEL test coverage calculation and updated the reporter to handle error/unknown scenarios.PR #​1209 & PR #​1215

Core Library

  • Regex Costing: Added support for cost estimation and tracking within the regex library. PR #​1200

  • JSON Type Exposure: Exposed CEL JSON types to assist developers in converting to native values. PR #​1261

  • Policy Composition: Source information is now preserved during CEL policy composition, aiding in debugging. PR #​1253

Extensibility:

  • Updated extension option factory to resolve by ID (#​1249).

  • Refactored match output compiling to accept user-defined logic (#​1246).

  • Exposed Match source ID to callers (#​1227).

Build & Maintenance

  • Bazel: Migrated to use Bazel module only and improved configuration for dependent builds. PR #​1231 & PR #​1228

  • Cleanup: Removed strcase dependency, removed AppEngine code from REPL, and performed general linting. PR #​1230, #​1216, #​1251

Bug Fixes

  • Concurrency: Fixed a race condition in the checker regarding reference types. PR #​1224

  • Namespace Resolution: Addressed an issue with namespace resolution. PR #​1256

  • Spec Compliance: Fixed formatting directives to fully support requirements documented in the cel-spec. PR #​1232

New Contributors

Full Changelog: cel-expr/cel-go@v0.26.1...v0.27.0

onsi/gomega (github.com/onsi/gomega)

v1.40.0

Compare Source

1.40.0

We're adopting a new release strategy to minimize dependency bloat in projects that consume Gomega. It is a limitation of the go mod toolchain that test subdependencies of your project's direct dependencies get pulled in as indirect dependencies. In the case of Gomega, this ends up pulling in all of Ginkgo into your go.mod even if you are only using Gomega (Gomega uses Ginkgo for its own tests).

Going forward, releases will strip out all tests, tidy up the go.mod and then push this stripped down version to a new master-lite branch. These stripped-down versions will receive the vx.y.z git tag and will be picked up by the go toolchain.

Please open an issue if this new release process causes unexpected changes for your projects.

prometheus/common (github.com/prometheus/common)

v0.67.5

Compare Source

What's Changed

Full Changelog: prometheus/common@v0.67.4...v0.67.5

uber-go/zap (go.uber.org/zap)

v1.28.0

Compare Source

Enhancements:

  • #​1534: Add zapcore.CheckPreWriteHook and CheckedEntry.Before method for transforming entries before they are written to any Cores.
yaml/go-yaml (go.yaml.in/yaml/v2)

v2.4.4

Compare Source

Configuration

📅 Schedule: (UTC)

  • 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.

👻 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

This PR has been generated by Mend Renovate.

@kvrenovatebot
Update all dependencies
e17dc98 
Signed-off-by: Renovate Bot <renovate@hollyhome.ath.cx>
@kubevirt-bot kubevirt-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels May 12, 2026
@kubevirt-bot
kubevirt-bot requested a review from akrejcir May 12, 2026 16:08
@kubevirt-bot

kubevirt-bot commented May 12, 2026

Copy link
Copy Markdown
Contributor

[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 lyarwood 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

@kubevirt-bot
kubevirt-bot requested a review from ksimon1 May 12, 2026 16:08
@dominikholler dominikholler mentioned this pull request May 13, 2026
Closed
@kubevirt-bot kubevirt-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 15, 2026
@kubevirt-bot

kubevirt-bot commented May 15, 2026

Copy link
Copy Markdown
Contributor

PR needs rebase.

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.

@kubevirt-bot

kubevirt-bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

There has been no activity on this PR for 45 days.
To protect limited CI resources, it has been automatically labelled 'stale'.
This PR will automatically rot after an additional 14 days of inactivity, and will be closed shortly after that.

What you can do:

  • If the PR is waiting on you to respond to a question or feedback and/or update the PR, please do so.
  • You can mark the PR as fresh and remove the label with the following command: /remove-lifecycle stale
  • If this PR is safe to close now, please help the project by closing it with: /close
  • If you need attention on this PR from a reviewer, you can raise it on the agenda of the relevant SIG meeting or KubeVirt Community meeting, or ping the kubevirt-dev slack channel.

/lifecycle stale

@kubevirt-prow kubevirt-prow Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 29, 2026
@dominikholler dominikholler mentioned this pull request Jun 30, 2026
Open
@kubevirt-bot

kubevirt-bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

There has been no activity on this PR for 59 days and it has been stale for 14 days.
To protect limited CI resources, it has been automatically labelled 'rotten' and will be closed in 7 days.

What you can do:

  • If the PR is waiting on you to respond to a question or feedback and/or update the PR, please do so.
  • You can mark the PR as fresh and remove the label with the following command: /remove-lifecycle rotten
  • If this PR is safe to close now, please help the project by closing it with: /close
  • If you need attention on this PR from a reviewer, you can raise it on the agenda of the relevant SIG meeting or KubeVirt Community meeting, or ping the kubevirt-dev slack channel.

/lifecycle rotten

@kubevirt-prow kubevirt-prow Bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 13, 2026
@kubevirt-bot

kubevirt-bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

There has been no activity on this PR for 66 days and it has been rotten for 7 days.
To protect limited CI resources, it has been automatically closed.

What you can do:

/close

@kubevirt-prow kubevirt-prow Bot closed this Jul 20, 2026
@kubevirt-prow

kubevirt-prow Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

@kubevirt-bot: Closed this PR.

Details

In response to this:

There has been no activity on this PR for 66 days and it has been rotten for 7 days.
To protect limited CI resources, it has been automatically closed.

What you can do:

/close

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

@akrejcir akrejcir Awaiting requested review from akrejcir
@ksimon1 ksimon1 Awaiting requested review from ksimon1

Assignees

No one assigned

Labels

dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XXL

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@dominikholler @kubevirt-bot @kvrenovatebot