⭐ Features
- #71: Generate action wrappers code
From now on, you won't find hand-crafted action wrappers in the library - they are now generated based on action metadata file (action.yml). It makes adding new wrappers much simpler and boilerplate-free. From users' perspective, it provides KDoc documentation for all inputs, as provided by actions' authors. It also unlocks great possibilities, as e.g. changes to actions API will be easy to apply in batch to all wrappers (e. g. action outputs handling). Kudos to @jmfayard for supporting this effort, especially for preparing a PoC and showing me how to use kotlinpoet (Kotlin generation library) :) - Add wrapper for actions/setup-node@v2
🛠️ Fixes
- #70: Incorrect YAML when value starts with
*,[or!
💣 Breaking changes
- #71: Because the code is now generated, several breaking changes occurred. From what I remember when working on code generation:
CreateBranchV2is nowActionCreateBranchV2- the name is inferred straight from the action name (4a2f2ea)- in
CheckoutV2,FetchDepth's concrete value is now passed withValueclass instead ofQuantity(a8bcdf1) - minor inconvenience: the order of arguments rendered to YAML for various actions may be different (e.g. for actions/setup-java@v2: 9e4b554)