Backend:
- Add column_definitions_compatible() in sample_sheet_util.py
- Filter incompatible collections in match_collections()
- Include column_definitions in HDCA options response
Frontend:
- Add column_definitions to DataOption type
- Check compatibility in canAcceptSrc for drag/drop
Fixes#21472🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
It should be possible for a subworkflow to declare a required input
with a default value (i.e. `None` / `null` is not a valid input),
yet the parent workflow may decide to just use the default.
This fixes that scenario.
Broken in https://github.com/galaxyproject/galaxy/pull/21473 .
Fix the following integration test issue:
```
FAILED test/integration/test_datatype_upload.py::test_upload_datatype_auto[test.sig] - AssertionError: Expected md5 sum 'fbbf5dc7ef17afae88808dc081dcc00b' for lib/galaxy/datatypes/test/test.sig, but test file md5sum is 44253008a9d105332ed107199fceb4d8. You need to add a final newline to lib/galaxy/datatypes/test/test.sig.
assert 'fbbf5dc7ef17afae88808dc081dcc00b' == '44253008a9d105332ed107199fceb4d8'
- 44253008a9d105332ed107199fceb4d8
+ fbbf5dc7ef17afae88808dc081dcc00b
```
xref discussion in https://github.com/galaxyproject/galaxy/pull/21467, we realized that the `release-drafter` isn't quite able to handle Galaxy's release flow; with a rolling release concurrent with a dev branch (problems with the drafter overwriting a release branch's notes and vice versa).
A limitation of the release-drafter (as I understand it) is that it
only updates the latest draft, whether it is the dev draft at that
point or the release draft, hence, resulting in duplicate release
drafts if a PR against a release branch is merged.
Here, we've added a step that checks and expects only 1 draft release
at a time. This is cleaner because: while the only draft is `dev`,
we only update that draft. Once, during the release process, `dev`
becomes a `release_` branch, we do not create yet another draft
for dev and instead just update the latest release branch draft,
until the release will be published and then dev will start getting
its own draft notes.
we plan to add kmindex (https://github.com/tlemane/kmindex
) to tools-iuc. As the tool uses a unique index format, a dedicated Galaxy datatype will be introduced to support it.
Dannon Baker