[wjohnald]

Citrine Python PR

Description

Bump the version to 5.2.0 for the next PyPI release. The release rolls up every change merged since v5.0.0.

The bump is minor because the roll-up adds a feature. The table helpers in #1066 shipped with a patch bump, and #1068 moved the gemd floor to 3.

Publishing the GitHub release triggers the PyPI upload and the docs deploy. The notes below are the draft for the release body. Use the title "Citrine v5.2.0 is released!" for the GitHub release.

Release notes

This release removes the GEM Table ingredient helpers' dependency on ProcessTemplate.allowed_names. add_all_ingredients and add_all_ingredients_in_output read ingredient names from the process specs in your Table Config's datasets. It also moves the SDK onto gemd 3 and updates pyjwt and urllib3 for their security fixes.

What's New

• TableConfig.add_all_ingredients and TableConfig.add_all_ingredients_in_output build ingredient columns from the names in your process specs. The helpers find names in the datasets your Table Config references. When the specs contain no ingredient names, the helpers return a copy of your Table Config with the same variables and columns. See Defining tables for examples. PNE-9647: Read ingredient names from process specs #1066

Improvements

• Citrine Python requires gemd 3, with the range gemd>=3,<4. Upgrade gemd before you install this release in an environment pinned to gemd 2. Both gemd 3 and Citrine Python require Python 3.10. Require gemd>=3,<4 #1068
• Attribute template and bounds pairs on object templates are tuples, as in gemd. Code that assigns into a pair in place, such as template.properties[0][0] = ..., raises TypeError. Replace the whole pair instead. Bump gemd to 2.3.2 #1065
• Updated pyjwt to 2.15.0 and urllib3 to 2.8.0, which include upstream security fixes. Bump pyjwt from 2.13.0 to 2.15.0 #1063, Bump urllib3 from 2.7.0 to 2.8.0 #1064

Full Changelog: v5.0.0...v5.2.0

PR Type

• Breaking change
• Bug fix
• New feature
• Maintenance

Adherence to team decisions

• I have added tests for 100% coverage.
• I have written NumPy-style docstrings for every method and class.
• I have communicated the downstream consequences of the PR to others.
• I have bumped the version in __version__.py.