Skip to content

Citrine v1.33.0 is released!

Choose a tag to compare

View all tags
@jspeerless jspeerless released this 08 Jun 16:52
v1.33.0
5dff9cf
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

In this release of Citrine Python, we are all about improvements. We've made improvements to our default behavior around units in GEM Table column definitions to avoid the case of miss-matched units within a column. We also have improved backwards compatibility of project endpoints to reduce the amount of code changes required in the upcoming migration to Teams. Finally, as always, we continue to update our documentation and make minor improvements to better support our users.

Improvements

  • Smarter behavior of the target_units parameter in GEM Table Column definition is now on platform. If you don't specify which units you want to work in, the table builder check if there's also an OriginalUnitsColumnDefinition to figure out if you wanted the numbers as reported; if not, you'll get the default_units from your Attribute Template. So if you don't specify units, the platform's got you covered. #758
  • Increased backwards compatibility of project endpoints for our upcoming migration to Teams for access control. #759, #761
  • Updated our documentation to be more descriptive about the relationship between branches, design workflows, and archival. #760
  • Other minor improvements. #762

Full Changelog: v1.31.1...v1.33.0

Assets 2
Loading