-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
MNT: upgrade upload/download-artifact GitHub actions #370
MNT: upgrade upload/download-artifact GitHub actions #370
Conversation
Thank you for your contribution! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #370 +/- ##
=======================================
Coverage 96.80% 96.80%
=======================================
Files 17 17
Lines 2034 2034
=======================================
Hits 1969 1969
Misses 65 65 ☔ View full report in Codecov by Sentry. |
Hello! It looks like I did not configure the publish workflow to ever run for a PR. Maybe let me fix that and then you can rebase, so we know it works before merge? Thanks for your patience! |
sure, by all means ! |
718f030
to
c8a6ce4
Compare
@pllim thanks for updating this branch. I think the failure is unrelated, can you re-trigger the job ? |
@neutrinoceros , they didn't fail. I cancelled them because I realized I needed to enable artifact upload/download also for non-release events. I am still debating with myself whether I should disable them again after it is proven or not. |
Ah... I mixed the release env stuff into dist build job too. I need to ponder this. (#371) |
so we can test dist in PR. I verified that upload/download works in PR 371 so no need to enable here for PRs.
25becd1
to
ab8dc04
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I added a commit to clean up my own tech debt. I think this is GTG now.
Also, yes, I thought about migrating to OpenAstronomy template but resisted because I got the Trusted Publishing already set up here and that does not play well with templating (yet). |
Description
Hi, version 4 of upload-artifact and download-artifact were recently released.
Staying on old version is not viable long term because GitHub will sooner or later drop support for the old versions of node that these depend on.
Since migration to v4 is not as straightfoward as bumping the version number, I'm helping all astropy-related packages byt manually performing the necessary changes.