The galaxy-tool-shed-schema package is basically pydantic models for the whole tool shed API. It is used by both the backend code for the new tool shed and the testing code that runs on both the old and new tool shed.
The creation of galaxy-tool-util-models package is something I've wanted to do for a while - it should solve some TODOs I've left in the base. I think beyond enabling galaxy-tool-shed-schema package - the other nice thing is that galaxy-schema code can now rely on various tool stuff without requiring dependency on any of the parser or runtime code.
This should also fix things for the new record types in #19377. I've introduced a type that can be used tools and is included schema for collection creation. The galaxy-tool-util-models packages can now be dependended on by galaxy-schema and galaxy-tool-util and these two packages do not need to depend on each other - either direction of that dependency would make me uncomfortable. xref
https://github.com/galaxyproject/galaxy/actions/runs/13704893929/job/38327692654?pr=19377
If you want to run or collect workflow tests now you've got to indicate
the full path currently (i.e. `pytest --collect-only
lib/galaxy_test/workflow/tests.py`). With this change `pytest
--collect-only lib/galaxy_test/workflow/` or just `pytest --collect-only
lib/galaxy_test/` will also discover the workflow tests.
- Allow class: File and class: Collection on file and collection test descriptions.
- Allow collection_type: <type> in collection test descriptions. Implement this.
- Update test workflows to reflect these two things as best practices.
mvdbeek