Skip to content

Add GitHub Actions workflow for ABI release - #14

Merged
pyropy merged 4 commits into
filbeam:mainfrom
DarkLord017:main
Jan 27, 2026
Merged

Add GitHub Actions workflow for ABI release#14
pyropy merged 4 commits into
filbeam:mainfrom
DarkLord017:main

Conversation

@DarkLord017

Copy link
Copy Markdown
Contributor

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

@DarkLord017

Copy link
Copy Markdown
Contributor Author

Please review @pyropy

@pyropy pyropy left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Comment thread .github/workflows/abi-release.yml Outdated
@DarkLord017

DarkLord017 commented Jan 26, 2026

Copy link
Copy Markdown
Contributor Author

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

@pyropy
pyropy requested review from bajtos and juliangruber January 26, 2026 11:47
DarkLord017 and others added 2 commits January 26, 2026 19:01
@DarkLord017

Copy link
Copy Markdown
Contributor Author
Screenshot 2026-01-26 at 7 45 17 PM 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

@DarkLord017
DarkLord017 requested a review from pyropy January 26, 2026 14:16
@pyropy

pyropy commented Jan 26, 2026

Copy link
Copy Markdown
Contributor

Screenshot 2026-01-26 at 7 45 17 PM 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.

@DarkLord017

DarkLord017 commented Jan 26, 2026

Copy link
Copy Markdown
Contributor Author
Screenshot 2026-01-26 at 11 16 13 PM

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
in branch and like it is created manually as the newer artifacts just adds to the workflow artifacts maybe i can these two things
maybe i can use this action https://github.com/softprops/action-gh-release ?

@DarkLord017

DarkLord017 commented Jan 26, 2026

Copy link
Copy Markdown
Contributor Author

Screenshot 2026-01-26 at 7 45 17 PM 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 se
e what happens then.

@pyropy also created a release using https://github.com/softprops/action-gh-release 1.0.19 using this
let me know which sounds good

Screenshot 2026-01-26 at 11 46 07 PM

@pyropy

pyropy commented Jan 27, 2026

Copy link
Copy Markdown
Contributor

Screenshot 2026-01-26 at 7 45 17 PM 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 se
e what happens then.

@pyropy also created a release using https://github.com/softprops/action-gh-release 1.0.19 using this let me know which sounds good

Screenshot 2026-01-26 at 11 46 07 PM

That looks great. Let's switch to softprops/action-gh-release 👍🏻

@DarkLord017

Copy link
Copy Markdown
Contributor Author

Made the changes

Screenshot 2026-01-26 at 7 45 17 PM 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 se
e what happens then.

@pyropy also created a release using https://github.com/softprops/action-gh-release 1.0.19 using this let me know which sounds good
Screenshot 2026-01-26 at 11 46 07 PM

That looks great. Let's switch to softprops/action-gh-release 👍🏻

Made the changes

@pyropy pyropy left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazing job @DarkLord017 ! 🎉

@pyropy
pyropy merged commit 385efa5 into filbeam:main Jan 27, 2026
3 checks passed
BigLep added a commit that referenced this pull request Jul 7, 2026
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Publish contract ABI on release

3 participants