Skip to content

Tags: calvinxiao/cadence

Tags

v0.21.2

Toggle v0.21.2's commit message
Rollback workflow already completed error (cadence-workflow#4209)

v0.21.0

Toggle v0.21.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Release/0.21.0 (cadence-workflow#4183)

* updating docker files to use 0.21 server and 3.25 UI

* updating changelog with release and date

* updating rest of docker compose files with versioned images

* updating changelog

v0.20.0

Toggle v0.20.0's commit message
Update docker for 0.20.0 release

v0.19.2

Toggle v0.19.2's commit message
Update docker-compose to 0.19.2

v0.19.1

Toggle v0.19.1's commit message
Update docker for 0.19.1 release

v0.18.2

Toggle v0.18.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
update docker-compose for 0.18.2 release (cadence-workflow#4060)

v0.18.1

Toggle v0.18.1's commit message
Move tcheck to go.mod, get rid of glide dependency (cadence-workflow#…

…3999)

[glide.sh is down](Masterminds/glide#1077), breaking our pipelines, and glide is abandonware anyway.
It's well past time to migrate off.

I don't believe `tcheck` is actually used for anything, nor is it mentioned in any documentation... but it _does_ work, it'll tell you if e.g. cadence-frontend is running and could be useful for scripting.  Though in that case a relevant `cadence ...` command would be as good or better anyway.

It may be worth removing this entirely?  It's not particularly large nor pulling in any new dependencies, but it may just be old cruft.

v0.19.0

Toggle v0.19.0's commit message
Retroactively tag v0.19.0, matches the go module checksum in proxy.go…

…lang.org

v0.10.0

Toggle v0.10.0's commit message
Retroactively tag v0.10.0, matches the go module checksum in proxy.go…

…lang.org

v0.18.0

Toggle v0.18.0's commit message
Update docker for 0.18.0 release