publish-zinnia-module-action's Introduction

publish-zinnia-module-action

Publish a Zinnia module to the registry

Usage

DEPRECATED

Use web3-storage-upload-file-action and w3name-update-action instead:

steps:
  - run: curl -L https://api.github.com/repos/${{ github.repository }}/tarball/${{ github.sha }} > source.tar.gz
  - uses: filecoin-station/web3-storage-upload-file-action@v0
    id: upload
    with:
      path: source.tar.gz
      private-key: ${{ secrets.W3UP_PRIVATE_KEY }}
      proof: ${{ secrets.W3UP_PROOF }}
  - uses: filecoin-station/w3name-update-action@v0
    with:
      value: "/ipfs/${{ steps.upload.outputs.cid }}"
      private-key: ${{ secrets.W3NAME_PRIVATE_KEY }}
      revision: ${{ secrets.W3NAME_REVISION }}

See https://web3.storage/docs/how-to/upload/#bring-your-own-delegations for w3up-* credentials.

For w3name-*, use a script like scripts/w3name.js.

publish-zinnia-module-action's People

Contributors

Watchers

publish-zinnia-module-action's Issues

docs: add example for publishing latest release

It's simple to set up this action to publish the last release that was published: https://github.com/filecoin-station/voyager/blob/4f4410c36df95774e6f52cabf717c322e27e6693/.github/workflows/publish.yml. This has one issue however: It's possible to create releases that are neither "latest" nor "pre-releases". Those shouldn't trigger a publish, effectively overwriting the "latest" version.

Ref filecoin-station/spark#52 (comment)

Recommend Projects