-
Notifications
You must be signed in to change notification settings - Fork 93
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
bump crate version number to 4.3.0 #1359
Conversation
Signed-off-by: Craig Disselkoen <[email protected]>
cedar-policy-cli/Cargo.toml
Outdated
cedar-policy-validator = { package= "cedar-policy-validator", git = "https://github.com/cedar-policy/cedar.git", branch = "main", version = "=4.1.0"} | ||
cedar-policy = { version = "=4.3.0", path = "../cedar-policy" } | ||
cedar-policy-formatter = { version = "=4.3.0", path = "../cedar-policy-formatter" } | ||
cedar-policy-core = { package= "cedar-policy-core", git = "https://github.com/cedar-policy/cedar.git", branch = "main", version = "4.*"} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does this change to 4.*
? (Also, why does the cli need to depend on core at all)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It can't say 4.3.0 because current git main
is not 4.3.0. An alternate plan would be to move this from a git to a path dependency, like the dependency on cedar-policy
.
CLI dependency on core was added in #1326 and is only necessary for the protobufs-related features. Now that we have #1345, I suspect this is no longer needed, and I'm working on removing it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps related that Cargo.lock has two entries for cedar-policy-core
at different commits.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oof. Looking closer, #1326 also added some JSON-related commands that are not guarded by the protobufs experimental flag, and rely on the undocumented JSON serialization of internal structures (which is what Lean expects as of this writing). Be nice to remove those when Lean switches to accepting protobuf instead, but technically that's a breaking change to functionality not marked as experimental
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same goes for cedar-policy-validator
(one line below). Can we use path dependencies for both?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Be nice to remove those when Lean switches to accepting protobuf instead, but technically that's a breaking change to functionality not marked as experimental
All unrelased code, so please break
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Signed-off-by: Craig Disselkoen <[email protected]>
Description of changes
Bumps the version number to 4.3.0 (here on
main
). Themain
branch already contains features that are targeted for 4.3.0, such as theprotobufs
experimental feature.