Adding Github Actions for Release/Version Validation

broadinstitute / warp

WDL Analysis Research Pipelines

https://broadinstitute.github.io/warp

BSD 3-Clause "New" or "Revised" License

201 stars 93 forks source link

Adding Github Actions for Release/Version Validation #1281

Closed kevinpalis closed 3 months ago

kevinpalis commented 4 months ago

Description

This is very similar to the GH actions for changelog validation. This will validate all pipeline version numbers as part of our effort to move out of Jenkins and to GH actions.

Checklist

If you can answer "yes" to the following items, please add a checkmark next to the appropriate checklist item(s) and notify our WARP documentation team by tagging either @ekiernan or @kayleemathews in a comment on this PR.

[ ] Did you add inputs, outputs, or tasks to a workflow?
[ ] Did you modify, delete or move: file paths, file names, input names, output names, or task names?
[ ] If you made a changelog update, did you update the pipeline version number?

github-actions[bot] commented 4 months ago

Remember to squash merge!

github-actions[bot] commented 4 months ago

Validation Results:

Comparing versions and changelogs for pipelines that differ from the versions on 'origin/staging':
All WDLs and changelog files appear to be valid for this release.

github-actions[bot] commented 4 months ago

Validation Results:

basename: missing operand
Try 'basename --help' for more information.
Comparing changelogs for pipelines that differ from the versions on 'origin/develop':
All changelog files are valid for this release.

github-actions[bot] commented 4 months ago

Remember to squash merge!

github-actions[bot] commented 4 months ago

🔍Version Validation Results:

Comparing versions and changelogs for pipelines that differ from the versions on 'origin/staging':
All WDLs and changelog files appear to be valid for this release.

github-actions[bot] commented 4 months ago