-
Notifications
You must be signed in to change notification settings - Fork 26
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
1.0 release #57
Comments
I'm starting the work in the 1.0 branch: https://github.com/CleverCloud/biscuit/tree/1.0 |
The first example of handling multiple versions is done with #23:
This is a small change for now, renaming fields does not modify the structure significantly (the generated tokens are the same byte for byte) |
Next, changing the protobuf format to use this changes the token's format, but not internal structures in the library, so there's no change to the feature set |
Adding support for boolean type (#61): |
Adding support for the set type (#51): |
Any chance of getting |
@meh possible, but I'll have to check if it will be compatible with expressions. I'm planning more operations like |
Yeah that's why I didn't just go for it, I know it's a valuable symbol for extending the language. For me it doesn't have to be a dot either, I just want an additional separator to _ so I can namespace things a bit, : would also work. |
Expressions(#38 using the design outlined in #47 (comment)): |
#62: Renaming "caveat" to "check", introduce "allow" and "deny" policies spec: fea8c33 |
With those changes, most of the work for 1.0 is done. now it needs a bit of polishing, like taking care of those issues: and making sure the specification is clear enough on the 1.0 changes |
adding #63 to the list, since I'm changing the syntax for those operations |
#63: renaming In to Contains, removing NotIn |
now would be a good time to think of other operations that could be supported. Right now I'm thinking of adding |
I added revocation identifiers for #1: |
more operations added to expressions: |
the 1.0 release is done 🥳 |
Biscuit has been in development for 2 years now and is now used in production. Most of the initial roadmap is done (we still need to commission an audit).
So it will soon be time for a stable release and more public communication. Before that, I'd prefer that we clean things up a bit, there are design decisions that were left alone because fixing them would be breaking changes, but a 1.0 release would be the right time to take care of them (here I consider a breaking change anything that would invalidate how currently existing tokens would be validated).
This will be a meta issue for the work needed towards the major release:
I'll make a branch of this repo with updated test samples once I've started that work on the Rust library.
see anything else we would need?
cc @divarvel @daeMOn63 @titanous @Keruspe @KannarFr @BlackYoup @meh
The text was updated successfully, but these errors were encountered: