feat: auto build without run build locally

[bluelovers]

What kind of PR is this?

Select only one to speed up review/approval; i.e., don't lump an addition and a removal into a single PR.

• Adding something new to awesome-ipfs
• Editing something already listed on awesome-ipfs
• Removing something from awesome-ipfs
• Something else (if so, please explain in the "Additional details" section below)

Pre-submit checklist

Please confirm ALL of the following before submitting your PR.

• This PR includes only one addition, removal, or edit.
• I edited the /data directory instead of the README.md.
• I ran the make build command following my edits to the /data directory.
• I reviewed the content policy and the and the IPFS Community Code of Conduct to ensure my submission meets the requirements.
• I have followed the CONTRIBUTING.md guidelines.

Additional details

Is there anything else we should know about this PR?

For new additions: What is your project's current size/reach?

For new additions: What is your project's potential size/reach?

For new additions: How critical is IPFS to your project?

• Essential
• Somewhat critical
• Useful, but not critical

For new additions: What core goal(s) does your project address?

• Big-data solutions
• Freedom from corporate/government interference
• Data integrity
• Dev tools or other ways to enable developers
• Disaster resilience/recovery
• File storage/retrieval
• File streaming
• Permanent archiving
• Self-sovereign idenity
• Platforms that utilize consensus, reputation, or incentivization
• Other (please list)

Is anything about IPFS blocking your project?

[jessicaschilling]

@andrew @lidel - can you please review? Thanks!

[andrew]

This looks good to me, I wonder if we should lock the referenced actions to a tag or commit rather master so we don't pull in any breaking changes later?

[lidel]

Thank you @bluelovers, just to be safe, let's switch to release versions

[andrew]

Thanks @bluelovers (and @lidel for the tweaks), I've merged this and its working well!