chore: release

[github-actions]

🤖 New release

• cel-parser: 0.8.0 -> 0.8.1 (✓ API compatible changes)
• cel-interpreter: 0.9.0 -> 0.9.1 (✓ API compatible changes)

Changelog

cel-parser

0.8.1 - 2025-04-29

Added

• Implement Short-Circuit Evaluation for AND Expressions to Fix Issue Implement short-circuit evaluation for AND expression #117 (#118)

cel-interpreter

0.9.1 - 2025-04-29

Added

• Implement Short-Circuit Evaluation for AND Expressions to Fix Issue Implement short-circuit evaluation for AND expression #117 (#118)

Fixed

• improve Context::add_variable Err type (#127)

Other

• Add min function (#130)
• Fix typos. (#125)
• Add custom Duration and Timestamp types for conversion with serde (#89)
• Export timestamp and duration fn as they were (#112)
• ValueType copy & debug (#113)
• Expose Serialization and ToJson errors (#114)
• Fix compilation without chrono (#111)
• Fix default features, cleanup dependencies & other minor code improvements (#109)
• Added missing timestamp macros (#106)

---

This PR was generated with release-plz.

[alexsnaps]

@clarkmcc Were you thinking or releasing v0.10 ?
Unsure about this message I see... I could move these 2 out of the ::time module again. I indeed broke that when refactoring things 🤦

[clarkmcc]

@alexsnaps No plans to release v0.10 within the next few days. Unless there's a rush, I'll probably wait until a few more changes build up and we've gotten some feedback about any breaking changes in the last release.

I'm not strictly opposed to breaking changes pre-1.0 if the change is positive. If you feel like a reversion of that change is necessary, I'm happy to review a PR for that. I'm also not overly concerned by the change at least at this stage.

[alexsnaps]

Opened a PR if that helps wrt the change.
wrt a release, it's mostly about visibility for ourselves as a dependent, as we'd need some unreleased changes, but can still point to a sha, which I just wanted to avoid if a release was about to happen :)