Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add badger db support & tune release #927

Merged
merged 11 commits into from
May 20, 2022
9 changes: 6 additions & 3 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,10 @@ on:
push:
# Sequence of patterns matched against refs/tags
tags:
- "v[0-9]+.[0-9]+.[0-9]+" # Push events to matching v*, i.e. v1.0, v20.15.10
- "v[0-9]+\\.[0-9]+\\.[0-9]+" # Official release version tags e.g. v2.0.5
- "v[0-9]+\\.[0-9]+\\.[0-9]+-rc[0-9]+" # Release candidate tags e.g. v1.0.3-rc4
Comment on lines +8 to +9
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- "v[0-9]+\\.[0-9]+\\.[0-9]+" # Official release version tags e.g. v2.0.5
- "v[0-9]+\\.[0-9]+\\.[0-9]+-rc[0-9]+" # Release candidate tags e.g. v1.0.3-rc4
- "v[0-9]+.[0-9]+.[0-9]+" # Official release version tags e.g. v2.0.5
- "v[0-9]+.[0-9]+.[0-9]+-rc[0-9]+" # Release candidate tags e.g. v1.0.3-rc4

Slashes needed?

Copy link
Contributor Author

@dreamcodez dreamcodez May 19, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

by putting the slashes in the regexp is more exact. \\. means an actual period. In regexp . means 'any character'. Hence before v0🙏🏻1🙏🏻2 was valid.. if that makes sense?

Two backslashes looks weird; the first slash is to escape the dot in the regexp; the second backslash escapes the backslash itself in the double-quoted string so that its not interpreted as a string escape (a single slash is seen by the regexp engine).

I've tested it :) in another repo and the rc i tested as well today.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

claps in semver

pull_request:
types: [ opened, synchronize ]

jobs:
release:
Expand All @@ -16,12 +19,12 @@ jobs:
fetch-depth: 0
- uses: actions/setup-go@v3
with:
go-version: 1.17
go-version: 1.18
- name: Set Env
run: echo "TM_VERSION=$(go list -m github.com/tendermint/tendermint | sed 's:.* ::')" >> $GITHUB_ENV
- name: Build
uses: goreleaser/goreleaser-action@v2
if: ${{ github.event_name == 'pull_request' }}
if: github.event_name == 'pull_request' && contains(github.event.pull_request.labels.*.name, 'Enable:ReleaseBuild')
with:
version: latest
args: build --rm-dist --skip-validate # skip validate skips initial sanity checks in order to be able to fully run
Expand Down
3 changes: 1 addition & 2 deletions .goreleaser.yml
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ builds:
binary: umeed
mod_timestamp: "{{ .CommitTimestamp }}"
flags:
- -tags=netgo ledger
- -tags=badgerdb ledger netgo
- -trimpath
env:
- CGO_ENABLED=0
Expand All @@ -25,7 +25,6 @@ builds:
- linux
goarch:
- amd64
- arm
- arm64

archives:
Expand Down