Skip to content

Add linter to check if tool versions are bumped#1502

Merged
mvdbeek merged 9 commits intogalaxyproject:masterfrom
bernt-matthias:topic/lint_shed_version
Mar 21, 2025
Merged

Add linter to check if tool versions are bumped#1502
mvdbeek merged 9 commits intogalaxyproject:masterfrom
bernt-matthias:topic/lint_shed_version

Conversation

@bernt-matthias
Copy link
Collaborator

so far against hardcoded toolshed.

@bernt-matthias bernt-matthias force-pushed the topic/lint_shed_version branch from 7c4d9cd to ee39ad9 Compare March 18, 2025 11:29
@mvdbeek mvdbeek merged commit 49bb08a into galaxyproject:master Mar 21, 2025
13 of 14 checks passed
@bernt-matthias bernt-matthias deleted the topic/lint_shed_version branch March 23, 2025 14:55
@nsoranzo
Copy link
Member

nsoranzo commented Mar 27, 2025

@bernt-matthias I suppose we need to disable the new ShedVersion check when running the weekly linting and tests in IUC's .github/workflows/ci.yaml ?
I have this now failing my weekly testing: https://github.com/TGAC/earlham-galaxytools/actions/runs/14025507773/job/39521819447

@bernt-matthias
Copy link
Collaborator Author

@peterjc
Copy link
Contributor

peterjc commented Apr 21, 2025

Why is an equal version treated as an error? It should be equal if the latest code has just been pushed to the Tool Shed.

peterjc added a commit to peterjc/galaxy_blast that referenced this pull request Apr 21, 2025
See galaxyproject/planemo#1502 - in our
current setup the the default branch should match the latest
upload to the Tool Shed so the version number should be equal.
@bernt-matthias
Copy link
Collaborator Author

Why is an equal version treated as an error? It should be equal if the latest code has just been pushed to the Tool Shed.

CI is executed before the push to the TS. The linter check is intended to check if the tool version has been increased in a pull request.

CI does not do this nicely in some cases, eg if only one tool of a suite is updated. Therfore we allow to push anyway at IUC (after a careful double check).

@peterjc
Copy link
Contributor

peterjc commented Apr 21, 2025

I guess the usefulness of the version equality check depends on the workflow and when planemo lint is run. I don’t think this should be the default, but can and have disabled this check entirely instead (not ideal as it won’t catch real errors out of sync). Thanks for clarifying

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants