-
Notifications
You must be signed in to change notification settings - Fork 44
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #369 from uabjabborov/release/0.11.0
Release v0.11.0 preparation
- Loading branch information
Showing
2 changed files
with
22 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,16 +1,27 @@ | ||
# Release | ||
|
||
The steps: | ||
|
||
1. [draft](https://github.com/zigbee-alliance/distributed-compliance-ledger/releases/new) and publish a new GitHub release: | ||
1. Set a new upgrade handler for the version being released in [here](https://github.com/zigbee-alliance/distributed-compliance-ledger/blob/2ea0715e47bc911c21e0f74431a87ce68bbd5043/app/app.go#L589) before releasing the binary | ||
|
||
example: | ||
```golang | ||
app.UpgradeKeeper.SetUpgradeHandler( | ||
"v0.11.0", | ||
func(ctx sdk.Context, plan upgradetypes.Plan, fromVM module.VersionMap) (module.VersionMap, error) { | ||
return make(module.VersionMap), nil | ||
}, | ||
) | ||
``` | ||
> **_Note:_** Dummy handler is added in this example. But you may want to run some migrations inside the handler. | ||
2. [draft](https://github.com/zigbee-alliance/distributed-compliance-ledger/releases/new) and publish a new GitHub release: | ||
* specify a new release tag based on a new planned version of DCLedger in the format `v<version>` (e.g. `v1.2.3` for the version `1.2.3`) | ||
* verify the branch/commit target for the release: usually it should be `master` but other targets are possible as well | ||
* put release notes | ||
2. once published [release pipeline](https://github.com/zigbee-alliance/distributed-compliance-ledger/actions/workflows/release.yml) is triggered: | ||
3. once published [release pipeline](https://github.com/zigbee-alliance/distributed-compliance-ledger/actions/workflows/release.yml) is triggered: | ||
* it builds `dcld` binary on `ubuntu-20.04` and `macos-11` and attaches the artifacts to the GitHub release: | ||
* binary and archived binary for `ubuntu-20.04` | ||
* archived binary for `macos-11` | ||
* systemd service file | ||
3. additional way to trigger the pipeline is to do that manually, it can be used for the following cases: | ||
4. additional way to trigger the pipeline is to do that manually, it can be used for the following cases: | ||
* some intermittent issue happened during the normal build so some artifact hasn't been attached | ||
* testing / debugging |