ci: add publish

[juliangruber]

This automatically publishes the module source ip IPFS/IPNI, when a release has been created. Then, Station Core's auto updater will be able fetch it.

All secrets have been configured on the repo, and stored in 1password with additional context.

Caveat: If we create a new stable release, which is however not the "latest" version, the action will publish it and overwrite the current IPNI pointer anyways. I see this as low risk atm. Do you have any ideas how we could circumvent that?

[bajtos]

Caveat: If we create a new stable release, which is however not the "latest" version, the action will publish it and overwrite the current IPNI pointer anyways. I see this as low risk atm. Do you have any ideas how we could circumvent that?

Can we skip the "publish to IPFS/IPNS" step for pre-release releases?

That way:

• Creating a "proper" GitHub release updates the IPNS link
• Creating a "pre-release" GitHub release does not update it

A quick search found this GHA discussion, I don't know if the information is still relevant though.
https://github.com/orgs/community/discussions/26281

if: "!github.event.release.prerelease"

[juliangruber]

It's already skipped for prerelease versions. It is however unfortunately possible to create a release that is not a pre-release and not marked as latest:

[bajtos]

I see. I think the current version is good enough.

In the ideal world, we would want to decouple "publish to IPFS" from "update IPNS".

• We can publish the source code to IPFS for all releases, including pre-releases. This step should record the CID somewhere in the release metadata. E.g., by adding a new txt file containing the CID to the release artefacts.
• When the repository's Latest Release is updated by any means, we update the IPNS link to point to the CID of that release.

It seems like GitHub does not provide an event/trigger to detect when the repository's Latest Release was updated. Maybe that's an oversight worth reporting to GitHub?

Maybe it's worth capturing this as a new GH issue in filecoin-station/publish-zinnia-module-action.

[bajtos]

LGTM 👍🏻

[juliangruber]

I see. I think the current version is good enough.

In the ideal world, we would want to decouple "publish to IPFS" from "update IPNS".

• We can publish the source code to IPFS for all releases, including pre-releases. This step should record the CID somewhere in the release metadata. E.g., by adding a new txt file containing the CID to the release artefacts.
• When the repository's Latest Release is updated by any means, we update the IPNS link to point to the CID of that release.

Uploading non-latest IPFS assets isn't yet a requirement, so I don't see a need to split these apart, making the stack more complicated.

It seems like GitHub does not provide an event/trigger to detect when the repository's Latest Release was updated. Maybe that's an oversight worth reporting to GitHub?

Maybe it's worth capturing this as a new GH issue in filecoin-station/publish-zinnia-module-action.

Captured in filecoin-station/publish-zinnia-module-action#3 👍