Closed 2bndy5 closed 1 year ago
Noticed this while working on the new composite actions. As far as resolving the depreciation issue, I can fix it there and I'm hoping to roll out the new CI here and to the libraries shortly,
Yes I was also thinking this would wait until after the transition to the new workflow style
Looks like we have until June 2023, so I'll try not to go TOO slow! :snail:
I already solved this in my own workflows.
There's also a warning about csexton/release-asset-action still using node.js v12. I have found a more frequently maintained action that can do the same thing, so I don't get the deprecation warnings anymore.
I have found a more frequently maintained action that can do the same thing
What did you find?
https://github.com/shogo82148/actions-upload-release-asset
It requires the upload URL, but that can be fetched via the context of the github event. Multiple files are supported using a glob pattern as well. See my release CI for the nRF24L01 lib. I have tested it with my CircuitPython_Homie lib releases.
Nice, I can look into this as well, and I'll add it as another item for the new workflow actions.
FYI, the comment in the current cookiecutter workflow is outdated and can be entirely removed because actions/upload-release-asset is now archived (not supported anymore).
I'm getting this warning for every build/release workflow run:
Looks like changes will need to be made in the cookiecutter's CI worlflows, specifically about normalizing the repo name for
circuitpython-build-tools
arguments.