Update module github.com/google/cel-go to v0.27.0

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/google/cel-go	v0.26.0 -> v0.27.0

---

Warning

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

---

Release Notes

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

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

• @​catalinadurbala made their first contribution in #​1227
• @​abenea made their first contribution in #​1258

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

v0.26.1

Compare Source

What's Changed

• Comprehension nesting limit typo, allow nesting limit validator to accept doubles as limits by @​l46kok in #​1196
• Minor compatibility fixes for google3-import. by @​jnthntatum in #​1198
• Bump the npm_and_yarn group across 1 directory with 2 updates by @​dependabot[bot] in #​1197
• Init function bindings on environment init by @​beldmian in #​1199
• Support variable descriptions in the AI prompt template by @​TristonianJones in #​1205
• Add support for nested element type by @​MisLink in #​1190
• Support unwrapping unknown implementations of proto.Message by @​srikrsna in #​1207

New Contributors

• @​beldmian made their first contribution in #​1199
• @​MisLink made their first contribution in #​1190
• @​srikrsna made their first contribution in #​1207

Full Changelog: google/cel-go@v0.25.1...v0.26.1

---

Configuration

📅 Schedule: 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 2 additional dependencies were updated

Details:

Package	Change
cel.dev/expr	v0.24.0 -> v0.25.1
github.com/antlr4-go/antlr/v4	v4.13.0 -> v4.13.1

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux[bot]
Once this PR has been reviewed and has the lgtm label, please assign nunnatsa 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:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

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

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