Skip to content

Upgrade to latest CEL specification #64

Open

Description

@slott56

CEL specification update:

  • Compare CEL specification 0.5.0 (when this was released) with "current" CEL specification (0.24.0 as of this edit) to get the list of changes.
  • Update all documentation, README, and all .feature files with very visible details on specific CEL specification used.
  • Rewrite and expand test cases to cover "current" CEL specification (0.24.0).
  • Prioritize resulting rework to bring this project into compliance. Create individual issues and a parent tracking issue for CEL compliance.

Activity

  1. self-assigned this
    on May 19, 2025
  2. added this to the 0.5 release milestone on Jul 25, 2025
  3. slott56 commented on Oct 1, 2025

    @slott56
    CollaboratorAuthor

    With PR #131, we now have tooling (and test cases) for the last CEL specification. (Thanks @hudlow and @stefanvanburen for doing so much work on this.)

    This means we "simply" have a long list of @wip test cases.

    The fourth of the sub-issues starts with triage of nearly 1200 new test cases into at least three categories: won't fix, hard-to-fix, and easy-to-fix. I'm going to open a discussion on @wip tests, to avoid cluttering this issue with a lot of digressions unrelated to the core four sub-issues.

  4. slott56 commented on Jul 6, 2026

    @slott56
    CollaboratorAuthor

    With PR #191, we now have tooling to help analyze the @wip test cases that provide specific scenarios that are in the CEL specification, but excluded from the acceptance test case. We can now easily put the 1200 test cases into a Notebook and start slicing and dicing them to work out why they don't pass and what changes are required.

  5. slott56 commented on Jul 6, 2026

    @slott56
    CollaboratorAuthor

    With PR #174, we have a git.log in the features directory showing the last 5 changes to the CEL-spec that was fetched. This provides some visibility into the release of the CEL-spec being tested against. Incorporating this into the README (and perhaps the help output from the CLI) must be done manually, as the @wip tags are removed.

  6. added
    trackingUsed to track progress across multiple sub-issues.
    on Jul 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requesttrackingUsed to track progress across multiple sub-issues.

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions