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(cel-interpreter): release v0.10.0 #107

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

Conversation

github-actions[bot]
Copy link
Contributor

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

🤖 New release

  • cel-interpreter: 0.9.0 -> 0.10.0 (⚠️ API breaking changes)

⚠️ cel-interpreter breaking changes

--- failure function_missing: pub fn removed or renamed ---

Description:
A publicly-visible function cannot be imported by its prior path. A `pub use` may have been removed, or the function itself may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.36.0/src/lints/function_missing.ron

Failed in:
  function cel_interpreter::functions::timestamp, previously in file /tmp/.tmpCUkhST/cel-interpreter/src/functions.rs:529
  function cel_interpreter::functions::duration, previously in file /tmp/.tmpCUkhST/cel-interpreter/src/functions.rs:522
Changelog

cel-interpreter

0.10.0 - 2024-11-06

Other

  • 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 from 2c7f88f to ceda1e9 Compare November 6, 2024 00:44
@github-actions github-actions bot force-pushed the release-plz-2024-11-04T17-01-04Z branch 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 :)

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