Citrine

This release of Citrine Python, we're excited to open up a new method of selecting materials for use in model training and visualization to our SDK users.

In our web application, the Citrine Platform has changed how the materials for training tables are selected by leveraging GemdQueries. With this release, we have deployed GemdQueries in Citrine Python as well. Now you may choose materials based on properties, material names, or other detailed properties of the material history, and we will return rows corresponding to the dependent subgraphs for all matching materials. This also supports nesting AND and OR queries, allowing for fine-grained control.

As usual, we've also included some minor fixes and improvements to keep our python SDK lean, clean, and to keep you running smoothly!

What's New
* Implementing `GemdQuery` objects for building tables. 926

Improvements
* Cleaning up disconnected code. 923

Fixes
* Description and summary field requirements are now optional for Datasets. 924

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v3.0.0...v3.1.0

We are proud to announce the 3rd major release of Citrine Python! The Citrine platform has made a lot of improvements over the past year, and our python SDK evolved along with it. This version of Citrine Python removes older methods that have been deprecated and keeps all our dependencies up to date to keep you running smoothly through 2024 and beyond.

It is recommended to migrate to version 3.0 as soon as possible. If all your code still runs without deprecation warnings with our previous release ([version 2.42.2](https://github.com/CitrineInformatics/citrine-python/releases/tag/v2.42.2)) then you have nothing to fear! Otherwise, things that were previously deprecation warnings may become errors.

Migrating to v3.0.0 immediately is not completely necessary, though continuing to use a 2.X version of Citrine Python may introduce instabilities in the near future. For any additional information on how to migrate your code, review the following deprecations below or consult our [V3 Migration Guide](https://citrineinformatics.github.io/citrine-python/FAQ/v3_migration.html).

Improvements
* Dependency updates 904 921 922
* Documentation improvements 910 917 920 919
* More efficient logging 913
* Internal testing improvements 916

Deprecated
The following deprecated features are no longer supported
* Python 3.7 is no longer supported 903
* Citrine.builders are no longer supported 909
* Require a team ID for `find_or_create_project` 912


**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v2.42.2...v3.0.0

This release of Citrine Python includes only a minor bug fix to correct our deployment to PyPI.

Fix
* Fix to our automatic deployment to PyPI. 911

Coming Soon

* We are very excited to announce that Citrine python v3.0 is expected to release in early February 2024. Note this means that currently deprecated methods will result in errors after this move, so be sure to check your code for any deprecation warnings. Contact Citrine support for any assistance in migration.

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v2.42.1...v2.42.2

In this version of Citrine python, we have some internal updates as well as improvements to our methods for accessing branches to improve consistency.

We are also pleased to announce that **Citrine python v3.0** will be coming in early February 2024. So as you update to the latest version of Citrine python, be sure to check your code (especially automated scripts) for any deprecation warnings! Those deprecated methods will result in errors after moving to v3.0.

Improvements
* Improvements to internal test automation. 906

Deprecated
* Deprecate branch access by version ID. To remain consistent with our other methods, one instead `get`s a branch with the branch root ID and version number. 902

Coming Soon
* We are very excited to announce that **Citrine python v3.0** is expected to release in early February 2024. Note this means that currently deprecated methods will result in errors after this move, so be sure to check your code for any deprecation warnings. Contact Citrine support for any assistance in migration.

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v2.41.0...v2.42.1

Shipping fixes and internal improvements with this release of Citrine Python. Making sure you can run smoothly as we pave the way for the next big step in functionality.

Improvements
* Internal changes for feature development. 891, 892, 893, 894, 898

Fixes
* Add admin checks for users and teams. 901

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v2.37.1...v2.41.0

Some minor updates to Citrine Python in this release to help catch ingestion errors and keep up with changing dependencies.

Improvements
* Add timeout setting to `files.ingest` ingestion endpoint to catch errors. 889
* Maintenance to keep us secure and up to date with dependencies. 890

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v2.36.0...v2.37.1