Since this pull request, GitHub Actions build workflow will become to publish Libplanet.Explorer project to NuGet for each push event if the build successes. You can see the published package here.
It uses version suffix including with build metadata dev.<TIMESTAMP>+git.sha.<CUT-11-LENGTH-SHA1> format (e.g. 0.1.0-dev.20210223044246+git.sha.0bb87f56b82). It uses cut 11-length Git SHA1 hash because NuGet limits version length to 64. According to https://git-scm.com/book/en/v2/Git-Tools-Revision-Selection, the commits of Linux kernel project can be presented in secure with 11-length hash.
Since this pull request, GitHub Actions
build
workflow will become to publishLibplanet.Explorer
project to NuGet for eachpush
event if the build successes. You can see the published package here.It uses version suffix including with build metadata
dev.<TIMESTAMP>+git.sha.<CUT-11-LENGTH-SHA1>
format (e.g.0.1.0-dev.20210223044246+git.sha.0bb87f56b82
). It uses cut 11-length Git SHA1 hash because NuGet limits version length to 64. According to https://git-scm.com/book/en/v2/Git-Tools-Revision-Selection, the commits of Linux kernel project can be presented in secure with 11-length hash.