Add GitHub Actions workflow for ABI release - #14
Conversation
|
Please review @pyropy |
pyropy
left a comment
There was a problem hiding this comment.
Great job @DarkLord017! Thank you for your contribution 🎉
The new workflow looks great. Did you have a chance to test it on your fork?
I'm proposing to replace the GitHub action for publishing the release artifacts with the official one. Let me know if that's okay?
Yes i tested it on my fork , it creates a release if tag is pushed and adds the ability to as an artifact successfully |
Co-authored-by: Srdjan <stankovic.srdjo@gmail.com>
hey @pyropy but by changin this the abi will be added as a workflow artifact not a release artifact , should i search for different libraries if u want it as a release artifact
|
I see you have created tags, but not release on your repository. Try creating a release to see what happens then. |
see this 1.0.18 release is from another branch which uses my initial commit but the 1.0.14 uses the workflow on ma |
@pyropy also created a release using https://github.com/softprops/action-gh-release 1.0.19 using this
|
That looks great. Let's switch to |
|
Made the changes
Made the changes |
pyropy
left a comment
There was a problem hiding this comment.
Amazing job @DarkLord017 ! 🎉
Adds the canonical FilOzone workflow that auto-adds newly opened issues and PRs to the FOC board (FilOzone org project #14), matching how the FOC repos and filbeam/worker do it. Uses the FILOZZY_CI_ADD_TO_PROJECT org secret. Part of filbeam/worker#695 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>





Fixes #12
This workflow creates a new release when a new tag is pushed and adds abi of the contract as an artifact to the release