Add aggregate semantics to Policy Compiler by copybara-service[bot] · Pull Request #1052 · cel-expr/cel-java

copybara-service · 2026-05-12T19:44:27Z

Add aggregate semantics to Policy Compiler

Aggregate walks through all matching rules (including nested ones) and appends them into a list:

rule:
aggregate:
- condition: "true"emit: "'FOO'"
- condition: "true"emit: "'BAR'"# Output: ['FOO', 'BAR']

Few noteworthy design decisions below. All examples assume all conditions matched:

For usability reasons, subrules under an aggregate ancestor will always have their lists flattened:

name: aggregate_flat_flattening_examplerule:
aggregate:
- rule:
match:
- condition: "resource.is_admin == true"output: "['GDPR_STANDARD', 'EU_B2C_NOTICE']"
- condition: "true"emit: "'FALLBACK'"# Output: ['GDPR_STANDARD', 'EU_B2C_NOTICE', 'FALLBACK']

Base case of an aggregate rule is an empty list. Nested conditional rules within an aggregate rule which outputs optional.none() are pruned (except in cases where policy output explicitly emits an optional.none()):

name: optional_pruning_examplerule:
aggregate:
- rule:
match:
- condition: "1 == 2"output: "'EU_NOTICE'"
- condition: "true"emit: "'ALWAYS'"# Output: ['ALWAYS']

name: explicit_optional_none_examplerule:
aggregate:
- rule:
match:
- condition: "resource.is_b2c == true"output: "optional.none()"# Explicitly authored by user
- condition: "true"emit: "optional.of('ALWAYS')"# Output: [optional.none(), optional.of('ALWAYS')]

Note: nesting aggregate clauses is currently not allowed, and will result in a compilation error.

Aggregate walks through all matching rules (including nested ones) and appends them into a list: ```yaml rule: aggregate: - condition: "true" emit: "'FOO'" - condition: "true" emit: "'BAR'" # Output: ['FOO', 'BAR'] ``` Few noteworthy design decisions below. All examples assume all conditions matched: 1. For usability reasons, subrules under an aggregate ancestor will always have their **lists flattened**: ```YAML name: aggregate_flat_flattening_example rule: aggregate: - rule: match: - condition: "resource.is_admin == true" output: "['GDPR_STANDARD', 'EU_B2C_NOTICE']" - condition: "true" emit: "'FALLBACK'" # Output: ['GDPR_STANDARD', 'EU_B2C_NOTICE', 'FALLBACK'] ``` 2. Base case of an aggregate rule is an empty list. Nested conditional rules within an aggregate rule which outputs `optional.none()` are pruned (except in cases where policy output explicitly emits an `optional.none()`): ```YAML name: optional_pruning_example rule: aggregate: - rule: match: - condition: "1 == 2" output: "'EU_NOTICE'" - condition: "true" emit: "'ALWAYS'" # Output: ['ALWAYS'] ``` ```YAML name: explicit_optional_none_example rule: aggregate: - rule: match: - condition: "resource.is_b2c == true" output: "optional.none()" # Explicitly authored by user - condition: "true" emit: "optional.of('ALWAYS')" # Output: [optional.none(), optional.of('ALWAYS')] ``` Note: nesting `aggregate` clauses is currently not allowed, and will result in a compilation error. PiperOrigin-RevId: 957321565

copybara-service · 2026-05-12T19:44:27Z

Add aggregate semantics to Policy Compiler

Aggregate walks through all matching rules (including nested ones) and appends them into a list:

rule:
aggregate:
- condition: "true"emit: "'FOO'"
- condition: "true"emit: "'BAR'"# Output: ['FOO', 'BAR']

Few noteworthy design decisions below. All examples assume all conditions matched:

For usability reasons, subrules under an aggregate ancestor will always have their lists flattened:

name: aggregate_flat_flattening_examplerule:
aggregate:
- rule:
match:
- condition: "resource.is_admin == true"output: "['GDPR_STANDARD', 'EU_B2C_NOTICE']"
- condition: "true"emit: "'FALLBACK'"# Output: ['GDPR_STANDARD', 'EU_B2C_NOTICE', 'FALLBACK']

Base case of an aggregate rule is an empty list. Nested conditional rules within an aggregate rule which outputs optional.none() are pruned (except in cases where policy output explicitly emits an optional.none()):

name: optional_pruning_examplerule:
aggregate:
- rule:
match:
- condition: "1 == 2"output: "'EU_NOTICE'"
- condition: "true"emit: "'ALWAYS'"# Output: ['ALWAYS']

name: explicit_optional_none_examplerule:
aggregate:
- rule:
match:
- condition: "resource.is_b2c == true"output: "optional.none()"# Explicitly authored by user
- condition: "true"emit: "optional.of('ALWAYS')"# Output: [optional.none(), optional.of('ALWAYS')]

Note: nesting aggregate clauses is currently not allowed, and will result in a compilation error.

Aggregate walks through all matching rules (including nested ones) and appends them into a list: ```yaml rule: aggregate: - condition: "true" emit: "'FOO'" - condition: "true" emit: "'BAR'" # Output: ['FOO', 'BAR'] ``` Few noteworthy design decisions below. All examples assume all conditions matched: 1. For usability reasons, subrules under an aggregate ancestor will always have their **lists flattened**: ```YAML name: aggregate_flat_flattening_example rule: aggregate: - rule: match: - condition: "resource.is_admin == true" output: "['GDPR_STANDARD', 'EU_B2C_NOTICE']" - condition: "true" emit: "'FALLBACK'" # Output: ['GDPR_STANDARD', 'EU_B2C_NOTICE', 'FALLBACK'] ``` 2. Base case of an aggregate rule is an empty list. Nested conditional rules within an aggregate rule which outputs `optional.none()` are pruned (except in cases where policy output explicitly emits an `optional.none()`): ```YAML name: optional_pruning_example rule: aggregate: - rule: match: - condition: "1 == 2" output: "'EU_NOTICE'" - condition: "true" emit: "'ALWAYS'" # Output: ['ALWAYS'] ``` ```YAML name: explicit_optional_none_example rule: aggregate: - rule: match: - condition: "resource.is_b2c == true" output: "optional.none()" # Explicitly authored by user - condition: "true" emit: "optional.of('ALWAYS')" # Output: [optional.none(), optional.of('ALWAYS')] ``` Note: nesting `aggregate` clauses is currently not allowed, and will result in a compilation error. PiperOrigin-RevId: 957321565

copybara-service · 2026-05-12T19:44:27Z

Add aggregate semantics to Policy Compiler

Aggregate walks through all matching rules (including nested ones) and appends them into a list:

rule:
aggregate:
- condition: "true"emit: "'FOO'"
- condition: "true"emit: "'BAR'"# Output: ['FOO', 'BAR']

Few noteworthy design decisions below. All examples assume all conditions matched:

For usability reasons, subrules under an aggregate ancestor will always have their lists flattened:

name: aggregate_flat_flattening_examplerule:
aggregate:
- rule:
match:
- condition: "resource.is_admin == true"output: "['GDPR_STANDARD', 'EU_B2C_NOTICE']"
- condition: "true"emit: "'FALLBACK'"# Output: ['GDPR_STANDARD', 'EU_B2C_NOTICE', 'FALLBACK']

Base case of an aggregate rule is an empty list. Nested conditional rules within an aggregate rule which outputs optional.none() are pruned (except in cases where policy output explicitly emits an optional.none()):

name: optional_pruning_examplerule:
aggregate:
- rule:
match:
- condition: "1 == 2"output: "'EU_NOTICE'"
- condition: "true"emit: "'ALWAYS'"# Output: ['ALWAYS']

name: explicit_optional_none_examplerule:
aggregate:
- rule:
match:
- condition: "resource.is_b2c == true"output: "optional.none()"# Explicitly authored by user
- condition: "true"emit: "optional.of('ALWAYS')"# Output: [optional.none(), optional.of('ALWAYS')]

Note: nesting aggregate clauses is currently not allowed, and will result in a compilation error.

Aggregate walks through all matching rules (including nested ones) and appends them into a list: ```yaml rule: aggregate: - condition: "true" emit: "'FOO'" - condition: "true" emit: "'BAR'" # Output: ['FOO', 'BAR'] ``` Few noteworthy design decisions below. All examples assume all conditions matched: 1. For usability reasons, subrules under an aggregate ancestor will always have their **lists flattened**: ```YAML name: aggregate_flat_flattening_example rule: aggregate: - rule: match: - condition: "resource.is_admin == true" output: "['GDPR_STANDARD', 'EU_B2C_NOTICE']" - condition: "true" emit: "'FALLBACK'" # Output: ['GDPR_STANDARD', 'EU_B2C_NOTICE', 'FALLBACK'] ``` 2. Base case of an aggregate rule is an empty list. Nested conditional rules within an aggregate rule which outputs `optional.none()` are pruned (except in cases where policy output explicitly emits an `optional.none()`): ```YAML name: optional_pruning_example rule: aggregate: - rule: match: - condition: "1 == 2" output: "'EU_NOTICE'" - condition: "true" emit: "'ALWAYS'" # Output: ['ALWAYS'] ``` ```YAML name: explicit_optional_none_example rule: aggregate: - rule: match: - condition: "resource.is_b2c == true" output: "optional.none()" # Explicitly authored by user - condition: "true" emit: "optional.of('ALWAYS')" # Output: [optional.none(), optional.of('ALWAYS')] ``` Note: nesting `aggregate` clauses is currently not allowed, and will result in a compilation error. PiperOrigin-RevId: 957321565

copybara-service · 2026-05-12T19:44:27Z

Add aggregate semantics to Policy Compiler

Aggregate walks through all matching rules (including nested ones) and appends them into a list:

rule:
aggregate:
- condition: "true"emit: "'FOO'"
- condition: "true"emit: "'BAR'"# Output: ['FOO', 'BAR']

Few noteworthy design decisions below. All examples assume all conditions matched:

For usability reasons, subrules under an aggregate ancestor will always have their lists flattened:

name: aggregate_flat_flattening_examplerule:
aggregate:
- rule:
match:
- condition: "resource.is_admin == true"output: "['GDPR_STANDARD', 'EU_B2C_NOTICE']"
- condition: "true"emit: "'FALLBACK'"# Output: ['GDPR_STANDARD', 'EU_B2C_NOTICE', 'FALLBACK']

Base case of an aggregate rule is an empty list. Nested conditional rules within an aggregate rule which outputs optional.none() are pruned (except in cases where policy output explicitly emits an optional.none()):

name: optional_pruning_examplerule:
aggregate:
- rule:
match:
- condition: "1 == 2"output: "'EU_NOTICE'"
- condition: "true"emit: "'ALWAYS'"# Output: ['ALWAYS']

name: explicit_optional_none_examplerule:
aggregate:
- rule:
match:
- condition: "resource.is_b2c == true"output: "optional.none()"# Explicitly authored by user
- condition: "true"emit: "optional.of('ALWAYS')"# Output: [optional.none(), optional.of('ALWAYS')]

Note: nesting aggregate clauses is currently not allowed, and will result in a compilation error.

Aggregate walks through all matching rules (including nested ones) and appends them into a list: ```yaml rule: aggregate: - condition: "true" emit: "'FOO'" - condition: "true" emit: "'BAR'" # Output: ['FOO', 'BAR'] ``` Few noteworthy design decisions below. All examples assume all conditions matched: 1. For usability reasons, subrules under an aggregate ancestor will always have their **lists flattened**: ```YAML name: aggregate_flat_flattening_example rule: aggregate: - rule: match: - condition: "resource.is_admin == true" output: "['GDPR_STANDARD', 'EU_B2C_NOTICE']" - condition: "true" emit: "'FALLBACK'" # Output: ['GDPR_STANDARD', 'EU_B2C_NOTICE', 'FALLBACK'] ``` 2. Base case of an aggregate rule is an empty list. Nested conditional rules within an aggregate rule which outputs `optional.none()` are pruned (except in cases where policy output explicitly emits an `optional.none()`): ```YAML name: optional_pruning_example rule: aggregate: - rule: match: - condition: "1 == 2" output: "'EU_NOTICE'" - condition: "true" emit: "'ALWAYS'" # Output: ['ALWAYS'] ``` ```YAML name: explicit_optional_none_example rule: aggregate: - rule: match: - condition: "resource.is_b2c == true" output: "optional.none()" # Explicitly authored by user - condition: "true" emit: "optional.of('ALWAYS')" # Output: [optional.none(), optional.of('ALWAYS')] ``` Note: nesting `aggregate` clauses is currently not allowed, and will result in a compilation error. PiperOrigin-RevId: 957321565

copybara-service · 2026-05-12T19:44:27Z

Add aggregate semantics to Policy Compiler

Aggregate walks through all matching rules (including nested ones) and appends them into a list:

rule:
aggregate:
- condition: "true"emit: "'FOO'"
- condition: "true"emit: "'BAR'"# Output: ['FOO', 'BAR']

Few noteworthy design decisions below. All examples assume all conditions matched:

For usability reasons, subrules under an aggregate ancestor will always have their lists flattened:

name: aggregate_flat_flattening_examplerule:
aggregate:
- rule:
match:
- condition: "resource.is_admin == true"output: "['GDPR_STANDARD', 'EU_B2C_NOTICE']"
- condition: "true"emit: "'FALLBACK'"# Output: ['GDPR_STANDARD', 'EU_B2C_NOTICE', 'FALLBACK']

Base case of an aggregate rule is an empty list. Nested conditional rules within an aggregate rule which outputs optional.none() are pruned (except in cases where policy output explicitly emits an optional.none()):

name: optional_pruning_examplerule:
aggregate:
- rule:
match:
- condition: "1 == 2"output: "'EU_NOTICE'"
- condition: "true"emit: "'ALWAYS'"# Output: ['ALWAYS']

name: explicit_optional_none_examplerule:
aggregate:
- rule:
match:
- condition: "resource.is_b2c == true"output: "optional.none()"# Explicitly authored by user
- condition: "true"emit: "optional.of('ALWAYS')"# Output: [optional.none(), optional.of('ALWAYS')]

Note: nesting aggregate clauses is currently not allowed, and will result in a compilation error.

Aggregate walks through all matching rules (including nested ones) and appends them into a list: ```yaml rule: aggregate: - condition: "true" emit: "'FOO'" - condition: "true" emit: "'BAR'" # Output: ['FOO', 'BAR'] ``` Few noteworthy design decisions below. All examples assume all conditions matched: 1. For usability reasons, subrules under an aggregate ancestor will always have their **lists flattened**: ```YAML name: aggregate_flat_flattening_example rule: aggregate: - rule: match: - condition: "resource.is_admin == true" output: "['GDPR_STANDARD', 'EU_B2C_NOTICE']" - condition: "true" emit: "'FALLBACK'" # Output: ['GDPR_STANDARD', 'EU_B2C_NOTICE', 'FALLBACK'] ``` 2. Base case of an aggregate rule is an empty list. Nested conditional rules within an aggregate rule which outputs `optional.none()` are pruned (except in cases where policy output explicitly emits an `optional.none()`): ```YAML name: optional_pruning_example rule: aggregate: - rule: match: - condition: "1 == 2" output: "'EU_NOTICE'" - condition: "true" emit: "'ALWAYS'" # Output: ['ALWAYS'] ``` ```YAML name: explicit_optional_none_example rule: aggregate: - rule: match: - condition: "resource.is_b2c == true" output: "optional.none()" # Explicitly authored by user - condition: "true" emit: "optional.of('ALWAYS')" # Output: [optional.none(), optional.of('ALWAYS')] ``` Note: nesting `aggregate` clauses is currently not allowed, and will result in a compilation error. PiperOrigin-RevId: 957321565

copybara-service · 2026-05-12T19:44:27Z

Add aggregate semantics to Policy Compiler

Aggregate walks through all matching rules (including nested ones) and appends them into a list:

rule:
aggregate:
- condition: "true"emit: "'FOO'"
- condition: "true"emit: "'BAR'"# Output: ['FOO', 'BAR']

Few noteworthy design decisions below. All examples assume all conditions matched:

For usability reasons, subrules under an aggregate ancestor will always have their lists flattened:

name: aggregate_flat_flattening_examplerule:
aggregate:
- rule:
match:
- condition: "resource.is_admin == true"output: "['GDPR_STANDARD', 'EU_B2C_NOTICE']"
- condition: "true"emit: "'FALLBACK'"# Output: ['GDPR_STANDARD', 'EU_B2C_NOTICE', 'FALLBACK']

Base case of an aggregate rule is an empty list. Nested conditional rules within an aggregate rule which outputs optional.none() are pruned (except in cases where policy output explicitly emits an optional.none()):

name: optional_pruning_examplerule:
aggregate:
- rule:
match:
- condition: "1 == 2"output: "'EU_NOTICE'"
- condition: "true"emit: "'ALWAYS'"# Output: ['ALWAYS']

name: explicit_optional_none_examplerule:
aggregate:
- rule:
match:
- condition: "resource.is_b2c == true"output: "optional.none()"# Explicitly authored by user
- condition: "true"emit: "optional.of('ALWAYS')"# Output: [optional.none(), optional.of('ALWAYS')]

Note: nesting aggregate clauses is currently not allowed, and will result in a compilation error.

Aggregate walks through all matching rules (including nested ones) and appends them into a list: ```yaml rule: aggregate: - condition: "true" emit: "'FOO'" - condition: "true" emit: "'BAR'" # Output: ['FOO', 'BAR'] ``` Few noteworthy design decisions below. All examples assume all conditions matched: 1. For usability reasons, subrules under an aggregate ancestor will always have their **lists flattened**: ```YAML name: aggregate_flat_flattening_example rule: aggregate: - rule: match: - condition: "resource.is_admin == true" output: "['GDPR_STANDARD', 'EU_B2C_NOTICE']" - condition: "true" emit: "'FALLBACK'" # Output: ['GDPR_STANDARD', 'EU_B2C_NOTICE', 'FALLBACK'] ``` 2. Base case of an aggregate rule is an empty list. Nested conditional rules within an aggregate rule which outputs `optional.none()` are pruned (except in cases where policy output explicitly emits an `optional.none()`): ```YAML name: optional_pruning_example rule: aggregate: - rule: match: - condition: "1 == 2" output: "'EU_NOTICE'" - condition: "true" emit: "'ALWAYS'" # Output: ['ALWAYS'] ``` ```YAML name: explicit_optional_none_example rule: aggregate: - rule: match: - condition: "resource.is_b2c == true" output: "optional.none()" # Explicitly authored by user - condition: "true" emit: "optional.of('ALWAYS')" # Output: [optional.none(), optional.of('ALWAYS')] ``` Note: nesting `aggregate` clauses is currently not allowed, and will result in a compilation error. PiperOrigin-RevId: 957321565

copybara-service · 2026-05-12T19:44:27Z

Add aggregate semantics to Policy Compiler

Aggregate walks through all matching rules (including nested ones) and appends them into a list:

rule:
aggregate:
- condition: "true"emit: "'FOO'"
- condition: "true"emit: "'BAR'"# Output: ['FOO', 'BAR']

Few noteworthy design decisions below. All examples assume all conditions matched:

For usability reasons, subrules under an aggregate ancestor will always have their lists flattened:

name: aggregate_flat_flattening_examplerule:
aggregate:
- rule:
match:
- condition: "resource.is_admin == true"output: "['GDPR_STANDARD', 'EU_B2C_NOTICE']"
- condition: "true"emit: "'FALLBACK'"# Output: ['GDPR_STANDARD', 'EU_B2C_NOTICE', 'FALLBACK']

Base case of an aggregate rule is an empty list. Nested conditional rules within an aggregate rule which outputs optional.none() are pruned (except in cases where policy output explicitly emits an optional.none()):

name: optional_pruning_examplerule:
aggregate:
- rule:
match:
- condition: "1 == 2"output: "'EU_NOTICE'"
- condition: "true"emit: "'ALWAYS'"# Output: ['ALWAYS']

name: explicit_optional_none_examplerule:
aggregate:
- rule:
match:
- condition: "resource.is_b2c == true"output: "optional.none()"# Explicitly authored by user
- condition: "true"emit: "optional.of('ALWAYS')"# Output: [optional.none(), optional.of('ALWAYS')]

Note: nesting aggregate clauses is currently not allowed, and will result in a compilation error.

Aggregate walks through all matching rules (including nested ones) and appends them into a list: ```yaml rule: aggregate: - condition: "true" emit: "'FOO'" - condition: "true" emit: "'BAR'" # Output: ['FOO', 'BAR'] ``` Few noteworthy design decisions below. All examples assume all conditions matched: 1. For usability reasons, subrules under an aggregate ancestor will always have their **lists flattened**: ```YAML name: aggregate_flat_flattening_example rule: aggregate: - rule: match: - condition: "resource.is_admin == true" output: "['GDPR_STANDARD', 'EU_B2C_NOTICE']" - condition: "true" emit: "'FALLBACK'" # Output: ['GDPR_STANDARD', 'EU_B2C_NOTICE', 'FALLBACK'] ``` 2. Base case of an aggregate rule is an empty list. Nested conditional rules within an aggregate rule which outputs `optional.none()` are pruned (except in cases where policy output explicitly emits an `optional.none()`): ```YAML name: optional_pruning_example rule: aggregate: - rule: match: - condition: "1 == 2" output: "'EU_NOTICE'" - condition: "true" emit: "'ALWAYS'" # Output: ['ALWAYS'] ``` ```YAML name: explicit_optional_none_example rule: aggregate: - rule: match: - condition: "resource.is_b2c == true" output: "optional.none()" # Explicitly authored by user - condition: "true" emit: "optional.of('ALWAYS')" # Output: [optional.none(), optional.of('ALWAYS')] ``` Note: nesting `aggregate` clauses is currently not allowed, and will result in a compilation error. PiperOrigin-RevId: 957321565

copybara-service · 2026-05-12T19:44:27Z

Add aggregate semantics to Policy Compiler

Aggregate walks through all matching rules (including nested ones) and appends them into a list:

rule:
aggregate:
- condition: "true"emit: "'FOO'"
- condition: "true"emit: "'BAR'"# Output: ['FOO', 'BAR']

Few noteworthy design decisions below. All examples assume all conditions matched:

For usability reasons, subrules under an aggregate ancestor will always have their lists flattened:

name: aggregate_flat_flattening_examplerule:
aggregate:
- rule:
match:
- condition: "resource.is_admin == true"output: "['GDPR_STANDARD', 'EU_B2C_NOTICE']"
- condition: "true"emit: "'FALLBACK'"# Output: ['GDPR_STANDARD', 'EU_B2C_NOTICE', 'FALLBACK']

Base case of an aggregate rule is an empty list. Nested conditional rules within an aggregate rule which outputs optional.none() are pruned (except in cases where policy output explicitly emits an optional.none()):

name: optional_pruning_examplerule:
aggregate:
- rule:
match:
- condition: "1 == 2"output: "'EU_NOTICE'"
- condition: "true"emit: "'ALWAYS'"# Output: ['ALWAYS']

name: explicit_optional_none_examplerule:
aggregate:
- rule:
match:
- condition: "resource.is_b2c == true"output: "optional.none()"# Explicitly authored by user
- condition: "true"emit: "optional.of('ALWAYS')"# Output: [optional.none(), optional.of('ALWAYS')]

Note: nesting aggregate clauses is currently not allowed, and will result in a compilation error.

Aggregate walks through all matching rules (including nested ones) and appends them into a list: ```yaml rule: aggregate: - condition: "true" emit: "'FOO'" - condition: "true" emit: "'BAR'" # Output: ['FOO', 'BAR'] ``` Few noteworthy design decisions below. All examples assume all conditions matched: 1. For usability reasons, subrules under an aggregate ancestor will always have their **lists flattened**: ```YAML name: aggregate_flat_flattening_example rule: aggregate: - rule: match: - condition: "resource.is_admin == true" output: "['GDPR_STANDARD', 'EU_B2C_NOTICE']" - condition: "true" emit: "'FALLBACK'" # Output: ['GDPR_STANDARD', 'EU_B2C_NOTICE', 'FALLBACK'] ``` 2. Base case of an aggregate rule is an empty list. Nested conditional rules within an aggregate rule which outputs `optional.none()` are pruned (except in cases where policy output explicitly emits an `optional.none()`): ```YAML name: optional_pruning_example rule: aggregate: - rule: match: - condition: "1 == 2" output: "'EU_NOTICE'" - condition: "true" emit: "'ALWAYS'" # Output: ['ALWAYS'] ``` ```YAML name: explicit_optional_none_example rule: aggregate: - rule: match: - condition: "resource.is_b2c == true" output: "optional.none()" # Explicitly authored by user - condition: "true" emit: "optional.of('ALWAYS')" # Output: [optional.none(), optional.of('ALWAYS')] ``` Note: nesting `aggregate` clauses is currently not allowed, and will result in a compilation error. PiperOrigin-RevId: 957321565

copybara-serviceBotforce-pushed the test_913930387 branch 4 times, most recently from a194d42 to 634780bCompare May 12, 2026 21:10

copybara-serviceBot changed the title ~~Add aggregate semantic to Policy Compiler~~Add aggregate semantics to Policy CompilerMay 12, 2026

copybara-serviceBotforce-pushed the test_913930387 branch 11 times, most recently from 6714afc to 380bcf3Compare May 13, 2026 23:37

copybara-serviceBotforce-pushed the test_913930387 branch 2 times, most recently from 7d705ad to f319900Compare May 20, 2026 21:38

copybara-serviceBotforce-pushed the test_913930387 branch 10 times, most recently from d97200e to 913d2b1Compare July 31, 2026 20:38

copybara-serviceBotforce-pushed the test_913930387 branch from 913d2b1 to 8d150b2Compare July 31, 2026 21:01

copybara-serviceBot merged commit 8d150b2 into mainJul 31, 2026

copybara-serviceBot deleted the test_913930387 branch July 31, 2026 21:01

TristonianJones mentioned this pull request Aug 7, 2026
Aggregate semantics in Policy Compiler cel-expr/cel-go#1408
Merged