forked fromhypermodeinc/badger
- Notifications
You must be signed in to change notification settings - Fork0
Tags: zjiek327/badger
Tags
v4.0.1
chore(go.mod): add retraction (hypermodeinc#1891)Since the v4.0.0 tag cannot be removed from the goproxy service, weadded a retraction directive so users do not accidentally use v4.0.0tag.
v4.0.1-RC1
chore(go.mod): add retraction (hypermodeinc#1891)Since the v4.0.0 tag cannot be removed from the goproxy service, weadded a retraction directive so users do not accidentally use v4.0.0tag.
v4.0.0
chore(ci): update changelog + import paths for v4 (hypermodeinc#1886)Changelog should reflect that we are switching to SemVer. This requiresmoving to a new major version. We also update all import paths inBadger.
v3.2103.5
chore(ci): bring workflows from main to release branch (hypermodeinc#……1840)## ProblemWe want workflows on main and release branch to be in harmony. This isespecially required for CD.## SolutionPull in recent changes from main.
v3.2103.4
chore(cd): cd steps for badger (hypermodeinc#1830)This PR adds CD steps for Badger releases. Artifacts (badger binary andchecksum) will be uploaded automatically to Github. Final step will beto add artifacts to release. This reflects the process we already havein place for Dgraph.Badger build flags were taken from the [Dgraph releasescript](https://github.com/dgraph-io/dgraph/blob/main/contrib/release.sh).We add a Makefile to streamline the build process.
PreviousNext