:rocket: <v0.27.0 released!>
# github-workflows-kt
p
j
I admire how you do frequent small releases. For #refreshversions we somehow always end up doing unfrequent huge releases. And that makes me super tired
a
+1 on what @jmfayard said. frequent small releases are so easy to follow through and develop compared to unfrequent huge releases
p
thanks! I figure it’s just easier to manage releases when they’re small, both for us the authors and you the users 🙂 my goal is to have continuous deployment, at least to some extent, so that I don’t have to do these manually and the version is calculated based on semver schema. For now we’re still in 0.x so it’s not really compliant with semver, but once we go 1.x, I’ll try to go CD as well
+ another argument for frequent releases of this DSL is deploying updated action wrappers, this is actually what gets changed more frequently than the core DSL lib
j
I don't have arguments for huge unfrequent releases. Somehow we didn't manage do better than that yet.
p
I noticed that the folks from https://github.com/renovatebot/renovate have the deployment nicely automated, I’m gonna analyze their workflows and get highly inspired 😉