Gemd

What’s New
* GEMD objects now support a much more robust version of equality checks. `==` will now check if references within an object (e.g., `material_run.spec`) refer to the same things by making LinkByUIDs equal to objects that share their IDs. This check will also recursively crawl through ingredients and measurements, making it much easier to determine if a stored version of a material history contains the same information as a newer one. (150)
Improvements
* There were some minor performance improvements as well stemming from some updates that were missed in 142.

Improvements
* The `from_entity` method from `LinkByUID` now uses the keyword argument `scope`, with the positional keyword `name` now deprecated. This matches library behaviors elsewhere. Documentation of the method was improved while we were in there. (149)

This release involves minor changes only.

Improvements
* Added inch-pounds as a unit for torque to the units file. (148)

Fixes
* Proofreading edits to the documentation. (146)

Version 1.0.0 signifies that GEMD is stable and mature. From here on out, all breaking changes to the codebase _must_ incur a major version bump. This means that code now written on top of gemd-python is **guaranteed to remain valid until _at least_ version 2.0.0**. We will continue to make improvements as needed.

Improvements
* The documentation was updated to be more legible and comprehensive (145)

This release includes substantial performance improvements as well as smaller, quality-of-life improvements and bug fixes.

What's New
* Profiling showed that recursive_foreach and recursive_flatmap were very slow in some applications. We've modified those two methods to reduce the number of function calls and to cache type checking across the util methods. The end result is that many cases are now running twice as fast. 142
* We've migrated from using `master` branch as the default branch to `main` branch. If you've been pinning to particular branches (which you shouldn't, really) then you'll need to update your `requirements.txt` or `setup.py`. 144

Improvements
* When calling flatten, `scope` is now an optional argument. This means that if your object set already has `uids` on all objects, there's no need to provide a `scope` string just to satisfy a signature. However, if you try to flatten objects that have no `uids`, a `ValueError` will be raised. 143

Fixes
* Because of a few intersecting corner cases, `mass %` was being parsed by [Pint](https://pint.readthedocs.io/en/stable/) as `milliarcseconds`. To prevent user confusion, we've removed `mas` as a synonym for `milliarcseconds`. #141
* Users can now import `make_index` directly from `gemd.util`, as was possible for its sister methods. 131
* Changes were made to how documents were deployed and repository permissions were controlled. 138 132

Coming soon
* We expect to move to version 1.0.0 in the near future. Stay tuned!

The update features small quality-of-life improvements
What's New

* A convenience method was was added for indexing objects by their UIDs (135). make_index will crawl whatever object is handed to it, indexing all the scope:id tuples it finds the later dereferencing, particularly for use in substitute_links.

Fixes

* The version of Pint was pinned to be compatible with Python 3.5, but with dropping 3.5 support we can advance it to take advantage of some more recent features. (136)
* Changes were made to our GitHub configuration to help with user management (132) and administrative token management (137).