Skip to content

build(deps): bump github.com/google/cel-go from 0.26.0 to 0.29.0 - #24

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/github.com/google/cel-go-0.29.0
Open

build(deps): bump github.com/google/cel-go from 0.26.0 to 0.29.0#24
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/github.com/google/cel-go-0.29.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 28, 2026

Copy link
Copy Markdown

Bumps github.com/google/cel-go from 0.26.0 to 0.29.0.

Release notes

Sourced from github.com/google/cel-go's releases.

Release v0.29.0

What's Changed

New Features

Bug Fixes

Cost Tracking

Testing & Tooling

Documentation

Release v0.28.1

What's Changed

New Contributors

... (truncated)

Commits
  • fa16799 avoid repeated construction of cost tracker (#1357)
  • ea3d5c0 feat(ext): add json encoder (#1340)
  • a4d0d64 startsWith / endsWith runtime cost agreement with checked cost (#1351)
  • d4efa77 Ensure receiver and global matches cost estimates agree (#1350)
  • 13cff33 ext/lists: add max size check to genRange() to prevent OOM (#1310)
  • f0ffa7e Execution frame integration with updated IntepretableV2 (#1344)
  • f1ec2f6 guard int32/uint32 map key narrowing in qualifyInternal (#1337)
  • 258e7c8 Managed execution frame with async call foundations (#1316)
  • 14f6746 validate offset on empty-string path in indexOf and lastIndexOf (#1335)
  • 783267d reject out-of-range minutes in timezone offset parsing (#1336)
  • Additional commits viewable in compare view

Dependabot compatibility score

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 commands and options

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 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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [github.com/google/cel-go](https://github.com/google/cel-go) from 0.26.0 to 0.29.0.
- [Release notes](https://github.com/google/cel-go/releases)
- [Commits](cel-expr/cel-go@v0.26.0...v0.29.0)

---
updated-dependencies:
- dependency-name: github.com/google/cel-go
  dependency-version: 0.29.0
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code minor labels Jul 28, 2026
@dependabot
dependabot Bot requested a review from a team as a code owner July 28, 2026 11:26
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code minor labels Jul 28, 2026
@github-actions

Copy link
Copy Markdown

Dependency Bump Evaluation

Version change: github.com/google/cel-go 0.26.0 -> 0.29.0 (3 minor bumps)
Semver bump type: minor (x3: v0.27.0, v0.28.0, v0.29.0)

Changes (across all 3 releases):

  • v0.29.0: JSON encoder extension, network IP/CIDR support, execution frame with async foundations, OOM prevention in genRange(), cost tracking improvements, multiple bug fixes (optional unwrapping, has() unknown propagation, timezone parsing, indexOf/lastIndexOf validation)
  • v0.28.0: JSON name support in checker/AST/runtime, mixed CEL/native values in native structs, variable redeclaration as constants, Go error to cel.Issues conversion, memory exhaustion cap in format strings, default backtick identifier escaping
  • v0.28.1: Deleted IntToDuration overload fix, context eval error preservation, strings extension cost estimation
  • v0.27.0: YAML config for REPL, regex cost estimation, JSON type exposure, extension option factory by ID

Breaking changes:

  • v0.27.0: Types relaxed as variables for safe feature-package rollout (PR #1262) -- only affects code that relied on types behaving as variables in CEL expressions. Not applicable here (see impact below).
  • v0.28.0: Default-enabling backtick identifier escaping (#1295) -- only affects expressions using backtick identifiers. Not applicable here.
  • v0.29.0: None documented.

Security concerns: None -- the bump includes positive security hardening:

  • genRange() max size check to prevent OOM (v0.29.0 #1310)
  • Format string precision cap to prevent memory exhaustion (v0.28.0 #1292)

Impact on codebase:

  • cel-go is an indirect dependency -- no .go file in this project imports it directly.
  • It is pulled in transitively by k8s.io/apiextensions-apiserver and k8s.io/apiserver (Kubernetes CRD validation machinery).
  • The project's only CEL usage is a single kubebuilder validation marker: self == oldSelf (taint immutability rule in api/v1alpha1/noderemediationpolicy_types.go:67). None of the breaking or behavioral changes in v0.27.0-v0.29.0 affect this pattern.

CI status:

  • build / build: FAILURE -- Docker push permission error (denied: installation not allowed to Write organization package), a known dependabot limitation unrelated to the dependency bump. The Go compilation itself succeeded.
  • generate: SUCCESS
  • lint, test, test-e2e: IN_PROGRESS at time of evaluation

Recommendation: REVIEW REQUIRED

Notes: The dependency change itself is safe -- cel-go is indirect, the project's CEL usage is minimal and unaffected by any breaking changes, and the bump includes security hardening. The REVIEW REQUIRED status is solely because CI checks (lint, test, test-e2e) are still running. Once CI is fully green (the build / build failure is an infrastructure permission issue, not a code problem), this is safe to merge.

— Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code minor

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants