Git-Mirrors/xmr-btc-swap
1
0
Fork 0
mirror of https://github.com/comit-network/xmr-btc-swap.git synced 2024-10-01 01:45:40 -04:00
Code Issues Packages Projects Releases Wiki Activity
2c2fb7f350
xmr-btc-swap/.github/workflows
History
Byron Hambly 6e7e39eea4
build(deps): upgrade bdk, ecdsa_fun, sigma_fun, sha2, bitcoin-harness, serde 
- bdk to 0.22.0 #1126
- ecdsa_fun to 7c3d592 #1127
- sigma_fun to 7c3d592 #1128
- sha2 to 0.10.2 #948
- serde to 1.0.144 #1115
- bitcoin-harness to bff9a64

Revert "ci: specify previous dprint version until fixed"
This reverts commit 11eb1737ce.
2022-09-12 12:03:24 +02:00
..
build-release-binaries.yml Bump Swatinem/rust-cache from 1.4.0 to 2.0.0 2022-07-18 11:16:26 +00:00
ci.yml build(deps): upgrade bdk, ecdsa_fun, sigma_fun, sha2, bitcoin-harness, serde 2022-09-12 12:03:24 +02:00
create-release.yml Bump actions/checkout from 3.0.1 to 3.0.2 2022-04-22 11:11:09 +00:00
draft-new-release.yml Merge branch 'master' into libp2p_upgrade 2022-04-22 16:01:31 +02:00
preview-release.yml Upgrade libp2p and stabilized the version 2022-04-22 15:53:55 +02:00
README.md Add workflow documentation 2021-03-25 11:12:02 +11:00

README.md

Workflow documentation

ci.yml

Defines the Continuous Integration workflow for merging into the master branch.

Releases

The workflows in this repository automate various things around releases. The functionality is composed in such a way that a human can easily start the workflow at various points, i.e. instead of being an all-or-nothing automation, we can step in where necessary.

Preview release

We have a rolling tag preview that always points to HEAD of master. The preview-release.yml workflow moves this tag to latest HEAD every time a PR gets merged. It also creates a corresponding GitHub "pre-release".

Building release binaries and attaching changelog

Whenever a new release is created, the build-release-binaries.yml workflow will build the swap and asb binaries in release mode and attach them to the release as artifacts.

Because this workflow is triggered on every release, it works for:

  • automatically created preview releases
  • releases created through the GitHub web interface
  • releases created by merging release branches into master

Making a new release

To create a new release, one has to:

  • Create a new branch
  • Update the version in the swap/Cargo.toml manifest file
  • Update the Changelog (convert Unreleased section to a release)
  • Make a commit
  • Open and merge a PR
  • Create a release from the resulting merge commit

To avoid errors in this process, we can automate it. The draft-new-release.yml workflow allows the user specify the desired version and the workflow will then open a PR that automates the above.

The created branch will follow the naming of release/X.Y.Z for the given version.

Any time a PR with such a branch name is merged, the create-release.yml workflow kicks in and creates a new release based on the resulting merge commit.

Because these two workflows are de-coupled, a user is free to create a release branch themselves if they wish to do so. They may also side-step both of these workflows by creating a release manually using the Github web interface.