Tags

chasquid v1.15.0
-----BEGIN SSH SIGNATURE-----
U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgHwiuRSJ1qsO6triWeyi/zcyB10
7SEttKL+YqdEXG9M0AAAADZ2l0AAAAAAAAAAZzaGE1MTIAAABTAAAAC3NzaC1lZDI1NTE5
AAAAQOOpxUfqn6sB0pBN0trXO7Yy14XaZfNHr9vFTFEOFcOUb4LS/9egCH8nxlOrxrhbO+
BziQkHE1TPhFs0yVsrmgY=
-----END SSH SIGNATURE-----

v1.14.0
-----BEGIN SSH SIGNATURE-----
U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgHwiuRSJ1qsO6triWeyi/zcyB10
7SEttKL+YqdEXG9M0AAAADZ2l0AAAAAAAAAAZzaGE1MTIAAABTAAAAC3NzaC1lZDI1NTE5
AAAAQEnA0oSnXJrBCu5RhczUsK0ovZomNk/FkZoyNTRosPdAa7sjNHVT9d0XR40mHm21tQ
XjGoOL/qtyVCyHhnrGhAU=
-----END SSH SIGNATURE-----

v1.13.0

It seems that by tagging 1.11.1, which is the first time a
semver-compatible version appeared, a bunch of Go tooling (e.g.
pkg.go.dev) now takes it as the only chasquid version, which is not
great and prone to confusion.

This tag (which points to v1.13) is intended to help mitigate those
tooling issues.

Future releases are likely to just be tagged with a semver-compatible
version from the start (e.g. v1.14.0 instead of v1.14).

This was reported by Christoph Mewes (xrstf@github) as part of the
discussion in https://github.com/albertito/chasquid/issues/51.

v1.11.1

v1.13

v1.12

v1.9

v1.8

v1.7

v1.6

v1.5

v1.4

v1.3

v1.2

v1.1

v1.00

v0.07

v0.06