Pulp-ansible

Bugfixes {: 0.24.2-bugfix }

- Fixed deadlock when performing multiple syncs with similar collections.
[2131](https://github.com/pulp/pulp_ansible/issues/2131)
- Fixed a bug in the git sync caused by a bad serialization after pulpcore 3.73.0.

---

Bugfixes {: 0.24.1-bugfix }

- Fixed a migration that was failing when upgrading on a system that was on 0.23.0 at one point in time.
[2118](https://github.com/pulp/pulp_ansible/issues/2118)

---

Features {: 0.24.0-feature }

- CollectionVersion global uniqueness constraint is now its sha256 digest. Repository level uniqueness
is still (namespace, name, version).
[1052](https://github.com/pulp/pulp_ansible/issues/1052)

Bugfixes {: 0.24.0-bugfix }

- Fixed a regression with migration 0056 failing on multiple null values on a unique constraint.
[2040](https://github.com/pulp/pulp_ansible/issues/2040)

Deprecations and Removals {: 0.24.0-removal }

- Added the final migration to make the sha256 of the collection version artifact the uniqueness
constraint. This allows users to serve their own interpretation of the content in their private
repositories.
The migration will only succeed if all the content has been adjusted. To account for content that
was not migrated by the migration shipped with 0.22.0, you can run the content repair command
``datarepair-ansible-collection-sha256`` prior to upgrading.
This version removed the content repair command.
[1052](https://github.com/pulp/pulp_ansible/issues/1052)
- Rebased and squashed old migrations to prepare for pulpcore 3.70 compatibility.
[2062](https://github.com/pulp/pulp_ansible/issues/2062)

Misc {: 0.24.0-misc }

- [2081](https://github.com/pulp/pulp_ansible/issues/2081), [#2083](https://github.com/pulp/pulp_ansible/issues/2083)

---

Bugfixes {: 0.23.1-bugfix }

- Fixed a regression with migration 0056 failing on multiple null values on a unique constraint.
[2040](https://github.com/pulp/pulp_ansible/issues/2040)

---

Features {: 0.23.0-feature }

- Added sha256 to collection versions.
This is the first part of a change to make this field the uniqueness constraint in the database.
The `datarepair-ansible-collection-sha256` management command is provided to prepare for the next release bringing the second and final step.

Bugfixes {: 0.23.0-bugfix }

- Fixed some 500 errors when browsing the Galaxy API.
[galaxy500s](https://github.com/pulp/pulp_ansible/issues/galaxy500s)
- Cast the content object to a collectionversion before setting the rebuild metadata.
[1921](https://github.com/pulp/pulp_ansible/issues/1921)
- Fixed a bug hitting a db restriction with `is_highest` on import.
[1986](https://github.com/pulp/pulp_ansible/issues/1986)
- Use the highest collection version to reflect a collection's update_at timestamp.
[2000](https://github.com/pulp/pulp_ansible/issues/2000)
- Fixed the JSONField specification so it doesn't break ruby bindings.
See context [here](https://github.com/pulp/pulp_rpm/issues/3639).
- Fixed the openapi spec for the collection version search.

Deprecations and Removals {: 0.23.0-removal }

- Removed `is_highest` from collection versions.
[1986](https://github.com/pulp/pulp_ansible/issues/1986)
- Removed the `is_highest` attribute on CollectionVersion.

---

Bugfixes {: 0.22.4-bugfix }

- Fixed deadlock when performing multiple syncs with similar collections.
[2131](https://github.com/pulp/pulp_ansible/issues/2131)

---