Releases: typesafegithub/github-workflows-kt
0.41.0
⭐ Features
- add possibility to use local actions conveniently (thanks @Vampire!)
- add possibility to use published Docker actions conveniently (thanks @Vampire!)
🛠️ Fixes
None.
💣 Breaking changes
- change Maven coordinates to io.github.typesafegithub:github-workflows-kt
- rename root Kotin package to io.github.typesafegithub.workflows
- move project to typesafegithub org - changes in the YAML preamble
- refactor usage of repository based actions to own Action subclass
▶️ Actions
Full Changelog: v0.40.0...v0.41.0
Contributors
Assets 2
0.40.0
⭐ Features
None.
🛠️ Fixes
💣 Breaking changes
None.
▶️ Actions
- add actions/stale@v8
- update actions/cache@v3
- update actions/labeler@v4
- update aws-actions/amazon-ecr-login@v1
- update docker/setup-buildx-action@v2
- update ReactiveCircus/android-emulator-runner@v2
- update ruby/setup-ruby@v1
Full Changelog: v0.39.0...v0.40.0
0.39.0
⭐ Features
- [#693] enforce named arguments for actions - this is to forbid using positional arguments which can cause issues when an action gets an input in the middle of the class signature. Thanks to this change, action's usage is explicit with regards to the inputs, like in GitHub Actions workflow YAML
- add link to API docs - the API docs aren't yet great, especially because of their coverage, but the docs are now built and hosted so that they can be used and further improved
🛠️ Fixes
None.
💣 Breaking changes
- [#693] enforce named arguments for actions - you may need to adjust how you use the actions, otherwise a compilation error will occur
▶️ Actions
- docker/metadata-action@v4 (thanks @NikkyAI!)
- add actions/setup-go@v4
- aws-actions/configure-aws-credentials@v2
Other
Thanks @Vampire for various contributions around docs, especially enable automatic unindenting of snippets!
Full Changelog: v0.38.0...v0.39.0
Contributors
Assets 2
0.38.0
⭐ Features
None.
🛠️ Fixes
None.
💣 Breaking changes
None.
▶️ Actions
Warning: the below changes may break your workflow code. Even though an action didn't get a new major version, using actions from Kotlin differs from how actions are used from YAML. If you don't use named arguments when passing inputs to actions, pay attention especially to the order of arguments. If you do use named arguments, you should be fine.
Full Changelog: v0.37.0...v0.38.0
0.37.0
⭐ Features
🛠️ Fixes
None.
💣 Breaking changes
- move base classes for actions to 'domain' + add custom outputs for all actions (thanks @Vampire!) - if you define your custom actions, you'll need to adjust their code a bit. See the updated docs
- allow inserting original preamble and trim whitespaces - breaking API adjustment for this pretty new feature
▶️ Actions
- add cachix/install-nix-action@v19
- add madhead/intellij-http-client-action@v231
- use typings provided by setup-msbuild@v1
- use typings provided by supercharge/mongodb-github-action@v1
Warning: the below changes may break your workflow code. Even though an action didn't get a new major version, using actions from Kotlin differs from how actions are used from YAML. If you don't use named arguments when passing inputs to actions, pay attention especially to the order of arguments. If you do use named arguments, you should be fine.
Full Changelog: v0.36.0...v0.37.0
Contributors
Assets 2
0.36.0
⭐ Features
- support defining workflows not in Kotlin scripts (thanks @mfwgenerics!)
- allow setting custom YAML preamble (thanks @mfwgenerics!)
- make actions wrappers data classes
🛠️ Fixes
None.
💣 Breaking changes
- go back to using JRE 11 + set name for the YAML consistency check job - it will require you to regenerate your YAMLs because the consistency job check changes again. Sorry for the back-and-forth!
▶️ Actions
- add burrunan/gradle-cache-action@v1 (thanks @Vampire!)
- add actions/cache/restore@v3
- add actions/cache/save@v3
- add Vampire/setup-wsl@v2 (thanks @Vampire!)
- add docker/build-push-action@v4
- add krzema12/github-actions-typing@v1
Warning: the below changes may break your workflow code. Even though an action didn't get a new major version, using actions from Kotlin differs from how actions are used from YAML. If you don't use named arguments when passing inputs to actions, pay attention especially to the order of arguments. If you do use named arguments, you should be fine.
- update actions/cache@v3
- update GoogleCloudPlatform/github-actions@v1
- update google-github-actions/setup-gcloud@v1
Full Changelog: v0.35.0...v0.36.0
Contributors
Assets 2
0.35.0
⭐ Features
None.
🛠️ Fixes
- correctly serialize empty and null-y strings (thanks @Vampire!)
- put jobs and steps as last attributes
💣 Breaking changes
- in some rare cases (nulls or empty strings as values), the fix for "correctly serialize empty and null-y strings" may force you to regenerate the YAML
- if you use custom arguments, "put jobs and steps as last attributes" will force you to regenerate the YAML
▶️ Actions
Warning: the below changes may break your workflow code. Even though an action didn't get a new major version, using actions from Kotlin differs from how actions are used from YAML. If you don't use named arguments when passing inputs to actions, pay attention especially to the order of arguments. If you do use named arguments, you should be fine.
Full Changelog: v0.34.2...v0.35.0
Contributors
Assets 2
0.34.2
⭐ Features
None.
🛠️ Fixes
- don't break lines for scalars (#616, thanks for reporting @benkeil!)
💣 Breaking changes
- for the fix for #616, it may be necessary to regenerate some workflows that use long strings, even if they work fine right now. The expected result now is no line breaks for strings at all
▶️ Actions
None.
Full Changelog: v0.34.1...v0.34.2
Contributors
Assets 2
0.34.1
⭐ Features
None.
🛠️ Fixes
- use JRE 17 in consistency check job - regenerating your YAMLs is required to include a new step in the consistency check job
💣 Breaking changes
None.
▶️ Actions
None.
Full Changelog: v0.34.0...v0.34.1
0.34.0
Warning: this version is faulty, please skip it!
⭐ Features
None.
🛠️ Fixes
None.
💣 Breaking changes
None.
▶️ Actions
Warning: the below changes may break your workflow code. Even though an action didn't get a new major version, using actions from Kotlin differs from how actions are used from YAML. If you don't use named arguments when passing inputs to actions, pay attention especially to the order of arguments. If you do use named arguments, you should be fine.
Other
Full Changelog: v0.33.0...v0.34.0
