Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: release #107

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Nov 4, 2024

πŸ€– 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 - 2024-12-30

Added

cel-interpreter

0.9.1 - 2024-12-30

Added

Other

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

@github-actions github-actions bot force-pushed the release-plz-2024-11-04T17-01-04Z branch 2 times, most recently from ceda1e9 to e48154c Compare November 6, 2024 15:30
@alexsnaps
Copy link
Contributor

@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
Copy link
Owner

clarkmcc commented Nov 7, 2024

@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
Copy link
Contributor

alexsnaps commented Nov 7, 2024

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 :)

@github-actions github-actions bot force-pushed the release-plz-2024-11-04T17-01-04Z branch 2 times, most recently from 519381e to f663ace Compare November 13, 2024 22:28
@github-actions github-actions bot changed the title chore(cel-interpreter): release v0.10.0 chore(cel-interpreter): release v0.9.1 Nov 19, 2024
@github-actions github-actions bot force-pushed the release-plz-2024-11-04T17-01-04Z branch 2 times, most recently from f2e85e0 to 11f7482 Compare November 19, 2024 17:43
@github-actions github-actions bot force-pushed the release-plz-2024-11-04T17-01-04Z branch from 11f7482 to 87f9ea2 Compare December 30, 2024 13:52
@github-actions github-actions bot changed the title chore(cel-interpreter): release v0.9.1 chore: release Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants