Update go dependencies - #226
Conversation
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: red-hat-konflux-kflux-prd-rh02[bot] The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @red-hat-konflux-kflux-prd-rh02[bot]. Thanks for your PR. I'm waiting for a openshift-online member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
6fb2bdd to
7f2f6fc
Compare
|
/ok-to-test |
|
/rebase |
7f2f6fc to
4305f9b
Compare
|
|
/retest |
4305f9b to
4fafe15
Compare
Signed-off-by: red-hat-konflux-kflux-prd-rh02 <190377777+red-hat-konflux-kflux-prd-rh02[bot]@users.noreply.github.com>
4fafe15 to
ff7ecf6
Compare
|
/retest |
|
@red-hat-konflux-kflux-prd-rh02[bot]: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
This PR contains the following updates:
v4.0.0-20230305170008-8188dc5388df→v4.0.0-20260216212909-7d5770395bb7v4.1.3→v4.3.0v2.9.0→v2.9.2v2.9.3v1.4.3→v1.4.4v0.17.8→v0.31.0v0.7.0→v0.7.1545e8a4→ef3492dv1.0.0→v1.0.1v1.0.1→v1.0.4v1.0.18→v1.0.27v2.32.0→v2.32.18006f30→d252783v1.12.1→v1.24.1v0.2.0→v0.6.2v0.32.1→v0.70.1v0.7.3→v0.21.1v1.2.0→v1.3.1v2.4.3→v2.4.4f3d0a9c→c1d0aacv0.56.0→v0.58.0v0.34.0→v0.36.0v0.44.0→v0.45.0v0.40.0→v0.41.0v0.14.0→v0.15.0v0.47.0→v0.49.0v1.36.12-0.20260120151049-f2248ac996af→v1.36.1243fb72c→d427ff9b8788ab→cf1189dv6.3.3→v6.4.2Release Notes
cenkalti/backoff (github.com/cenkalti/backoff/v4)
v4.3.0Compare Source
v4.2.1Compare Source
v4.2.0Compare Source
fxamacker/cbor (github.com/fxamacker/cbor/v2)
v2.9.2Compare 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
CI / GitHub Actions and Docs
🔎 Details...
Full Changelog: fxamacker/cbor@v2.9.1...v2.9.2
v2.9.1Compare 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
keyasintfeatureThese changes only affect Go struct fields tagged with
keyasint:math.MaxInt64when decoding CBOR map to a struct withkeyasintfield (PR #757)keyasinttag 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).
RawMessagefromRawMessage.MarshalCBOR(PR #753)U+FFFDreplacement character (PR #753)What's Changed
TimeRFC3339NanoUTCby @fxamacker in #688CI / GitHub Actions and Docs
🔎 Details...
New Contributors
Full Changelog: fxamacker/cbor@v2.9.0...v2.9.1
go-logr/logr (github.com/go-logr/logr)
v1.4.4Compare Source
What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.4.3...v1.4.4
google/cel-go (github.com/google/cel-go)
v0.31.0Compare Source
This release introduces critical performance breakthroughs, simplifies integration with native Go structures, and hardens the safety limits of evaluated expressions.
Features
Fixes
Breaking Changes
There are no breaking changes, but all
ext.NativeTypesfeatures are now available viacel.NativeTypesNotes on Performance
This release targets two primary computational bottlenecks in high-throughput CEL environments: environment construction and reflection-based type coercion.
Expected Impact
Go-lang Benchmark Citation (benchstat)
The performance improvements can be verified running the repository's native benchmark harness with benchstat:
name old time/op new time/op deltaBenchmarkEnvExtension/10_vars 3.56µs ± 1% 0.15µs ± 0% -95.79% (p=0.000 n=10+10)BenchmarkNativeToValue/struct 120ns ± 2% 42ns ± 1% -65.00% (p=0.000 n=10+10)BenchmarkOptionalMapEvaluation 245ns ± 1% 195ns ± 1% -20.41% (p=0.000 n=10+10)name old allocs/op new allocs/op deltaBenchmarkEnvExtension/10_vars 32.0 ± 0% 1.0 ± 0% -96.88% (p=0.000 n=10+10)BenchmarkNativeToValue/struct 3.00 ± 0% 1.00 ± 0% -66.67% (p=0.000 n=10+10)New Contributors
Full Changelog: cel-expr/cel-go@v0.30.0...v0.31.0
v0.30.0Compare Source
What's Changed
x in [x]for NaN values by @pranit0808 in cel-expr#1374New Contributors
Full Changelog: cel-expr/cel-go@v0.29.2...v0.29.3
v0.29.2Compare Source
What's Changed
Full Changelog: cel-expr/cel-go@v0.29.1...v0.29.2
v0.29.1Compare Source
What's Changed
Full Changelog: cel-expr/cel-go@v0.29.0...v0.29.1
v0.29.0Compare Source
What's Changed
New Features
extlibrary for JSON encoding by @rohan-patnaik in cel-expr#1340network.IP/CIDRsupport from Kubernetes by @tdesrosi in cel-expr#1238InterpretableV2by @TristonianJones in cel-expr#1344Bug Fixes
has()unknown propagation during partial evaluation by @0xASTRA in cel-expr#1324indexOfandlastIndexOfby @alhudz in cel-expr#1335int32/uint32map key narrowing inqualifyInternalby @alhudz in cel-expr#1337genRange()inext/liststo prevent OOM by @marwan9696 in cel-expr#1310Cost Tracking
startsWith/endsWithruntime cost agreement with checked cost by @TristonianJones in cel-expr#1351Testing & Tooling
Documentation
v0.28.1Compare Source
What's Changed
IntToDurationoverload by @alexsnaps in #1300New Contributors
Full Changelog: cel-expr/cel-go@v0.28.0...v0.28.1
v0.28.0Compare Source
High-Level Changes
cel.Issuesand more descriptive, context-aware error messages.🚀 Features
cel.Issuesin #1267env.Configvalues where reasonable in #1273NewEnvin #1275🐞 Bug Fixes
optional.orand.orValueimpl in #1276🛠️ Maintenance & Internal
Full Changelog: https://github.com/google/cel-go/compare/v0.27.0...v0.28.0-alpha
v0.27.0Compare 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
v0.26.1Compare Source
What's Changed
proto.Messageby @srikrsna in #1207New Contributors
Full Changelog: cel-expr/cel-go@v0.25.1...v0.26.1
v0.26.0Configuration
📅 Schedule: (UTC)
🚦 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.
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.