⭐ Features
🧪 🚧 I'm intensively iterating on client-side binding generation, and some preview of this functionality can be already seen in this repo:
- a workflow using this approach: .github/workflows/actions-versions.main.kts - notice the import of a generated binding and that no version is specified anywhere in the workflow
- a dummy workflow for defining which actions should get their bindings generated: .github/workflows/used-actions.yaml
- a new generation entry point that makes use of the dummy workflow: .github/workflows/generate-action-bindings.main.kts
- a Renovate PR successfully upgrading one action's version: #1052
It's available in the library's API for me to experiment and for some early adopters. Please expect breaking changes if you want to try it out. Proper documentation will follow.
Stay tuned for more!
🛠️ Fixes
None.
💣 Breaking changes
None.
▶️ Actions
Full Changelog: v1.3.0...v1.4.0