Resolves #104

Pre-pre-release: michalrus/bfp-release-testing/releases/tag/0.0.1.

How to install

Windows

In the link on top, you can see there are two Windows artifacts:

• Either a setup.exe which does everything for you, including setting up system PATH, so that you can run blockfrost-platform.exe from anywhere.

• Or a more manual .zip, without any installation.

Linux

• There's a .tar.bz2, which you can unpack yourself, and run ./bin/blockfrost-platform.

• And a curl-bash-install.sh which consumes that .tar.bz2, and you use it by running:

  curl -fsSL https://github.com/michalrus/bfp-release-testing/releases/latest/download/curl-bash-install.sh | bash

  It also tries to set up PATH, and gives the user instructions if it fails.

macOS (both architectures)

• There are 2 .tar.bz2s – one for each architecture.

• You can also use the curl-bash script above — it’s working even on Catalina (10.15.x).

• Or our Homebrew tap, which the release workflow also updates:

  brew install blockfrost/tap/blockfrost-platform

How to release

Right now, the workflow is triggered either by creating a release (or a pre-release), or manually (workflow_dispatch:) – in both cases it has to be run from a Git tag.

We can think about adding other triggers, e.g. simply pushing a tag. It would then create the release on its own, but maybe that would be too automated, and it's better to have a human look at everything first.

I haven’t yet run it on our repo, but I have the same workflow in my own temporary repository.

Here's a release of blockfrost-platform published there – michalrus/bfp-release-testing/releases/tag/0.0.1.

To-dos

• Update baseUrl to this repo blockfrost/blockfrost-platform.
• Merge this PR.
• Open new issue: Change the account pushing to our Homebrew tap from michalrus-bot to blockfrost-bot – we just need to generate a Personal Access Token, and substitute it in repo’s secrets. + Test that blockfrost-bot PAT has correct access – from Michal's repo first.
  • Use blockfrost-bot for our homebrew-tap updates #142
• Open new issue: Update the docs – separate issue.
  • documentation enhancements #129
• Open new issue: Guard the releases better, e.g. require 2 approvals. It can be done with protected branches (or rather, tags), and a little creative use of GitHub’s custom Deployment Protection Rules.
  • Guard the release process better – e.g. require 2 approvals #143
• Run a real pre-release from our repository.