Closed max2me closed 4 months ago
In general we should be tagging docs to coincide with a release. That way, customers can go back to look at docs consistent with an earlier version. Of course they can do this with the Rust docs, but they should be able to do it here, too.
Update: we're trying to do a better jobs of tracking this now on the document history page (https://docs.cedarpolicy.com/other/doc-history.html). Would still be great to have a way to get different versions of the docs though.
Actually, I see that @mwhicks1 already opened #85 for the more general solution -- I'll close this issue then since it's been resolved (for now).
What is wrong and why? Currently docs.cedarpolicy.com reports language version 2.3 yet includes features from Cedar 3.0 such as
is
operator.What do we need to do to fix this? Scrub Cedar version throughout docs.