Fix: Download MUSE2 release artifacts for new name format#64
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #64 +/- ##
=======================================
Coverage 47.61% 47.61%
=======================================
Files 3 3
Lines 42 42
Branches 4 4
=======================================
Hits 20 20
Misses 22 22 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull request overview
Updates the composite GitHub Action that installs MUSE2 from the latest release so CI keeps working after MUSE2 release artifacts are renamed to include version numbers.
Changes:
- Adjusts
gh release download --patternto use wildcards for Windows/macOS/Linux release asset names, matching both old and new artifact naming formats.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Pattern change looks good, but you may need to do more to get this to work. The extract/set muse2 path names require an exact path provided by |
I don't think that's a problem, though...? |
Oh yea think you're right sorry, for some reason I thought you were changing the exe names to include version numbers too. I think it's fine in that case |
|
I've confirmed this works with the renamed release artifacts, so I think it's good to go |
Description
After I've merged this PR on the MUSE2 repo, I'm going to rename the release artifacts for previous releases to include the version number in them, which means CI workflows on this repo will stop working. Fix by changing the name of the release artifacts downloaded to include a wildcard (which should match the old and new names).
Type of change
Key checklist
python -m pytest)pre-commit run --all-files)Further checks
(Indicate issue here: # (issue))