Now that there are releases of dolfin-adjoint and support in the main branch of other packages for ufl_legacy, it seems appropriate to publish a release of ufl_legacy.
This presumably involves:
tagging the latest commit on the ufl_legacy branch (e.g. ufl_legacy-2022.3.0 to match the version in the metadata)
The wheels workflow may work, depending on the credentials given to the workflow. If it's a scoped token that only has permission to publish ufl releases, then it will fail to upload and someone can manually upload and register with twine. GitHub environment secrets can be used to separate credentials for ufl_legacy, or setting it up as a trusted publisher so no credentials need to be managed.
Now that there are releases of dolfin-adjoint and support in the main branch of other packages for ufl_legacy, it seems appropriate to publish a release of ufl_legacy.
This presumably involves:
ufl_legacy-2022.3.0
to match the version in the metadata)The wheels workflow may work, depending on the credentials given to the workflow. If it's a scoped token that only has permission to publish ufl releases, then it will fail to upload and someone can manually upload and register with twine. GitHub environment secrets can be used to separate credentials for ufl_legacy, or setting it up as a trusted publisher so no credentials need to be managed.