This gives us a release-please setup similar to what we have for the web3.storage API.
A few notes:
This changes the Cloudflare Worker name to w3name, but I haven't yet set up that worker.
This requires our Cloudflare API token adding to GitHub secrets as CF_API_TOKEN, which (unless secrets are shared between repos in the same organisation?) hasn't yet been done.
We need to define/decide on the domain names that staging and production are going to live on and set those as the route value for each environment.
I've created this as a draft just because of the last point.
This gives us a release-please setup similar to what we have for the web3.storage API.
A few notes:
w3name
, but I haven't yet set up that worker.CF_API_TOKEN
, which (unless secrets are shared between repos in the same organisation?) hasn't yet been done.route
value for each environment.I've created this as a draft just because of the last point.