Björn Kautler
Björn Kautler
The current version is not compatible with the new Gradle configuration cache as it for example modifies the version property at task execution time.
I'm currently working on a release workflow for a TypeScript project. There I don't have the version in a properties file, but I read it from `package.json` for compatibility with...
Currently, first the unsnapshotting is done, then the release build and after that the unsnapshotting commit and tag are done. That means that you never do a release build from...
If you want to automatically create a GitHub release (in non-draft state), the tag needs to be created and pushed already, or GitHub will tag the current state of the...
When releasing from local machine and not CI and you configured to sign tags and have your GPG key passphrase protected, you cannot enter your passphrase, but the tagging just...
In a project with a git-flowy workflow, we want to create the release with your plugin on the development branch, including version increase to the next snapshot version and then...
You solely use `mustRunAfter` between your lifecycle tasks like `checkCommitNeeded` and so on. The only reason to use `mustRunAfter` instead of `dependsOn` is, if the "depending" task is actually independently...
Exception subclasses are generated as typealiases (for the wrong class) instead of proper subclasses
If you generate for `@actions/cache`, the generated `cache.module_@actions_cache.kt` contains ```kt typealias ValidationError = Error typealias ReserveCacheError = Error ``` This has three problems. 1. JS `Error` is mapped to `Throwable`...
If you generate for `@types/semver`, you get in `semver.module_semver.kt` the following definition: ```kt @JsModule("semver") external open class SemVer { ``` This is wrong tough, it needs to be ```kt @JsModule("semver/classes/semver")...
The JavaDoc of `SaveImagesCmd.TaggedImage` describes that it could be just a name, or name and tag separated by a colon. (the former would save all tags for the name to...