Closed smockle closed 11 months ago
The way I would go about it is to release a feature version that
Then once we release a new breaking version we can always look into the deprecations test file and remove them. It's a pattern that worked well for me in the past in several projects
Opened https://github.com/actions/create-github-app-token/pull/59 to support this.
:tada: This issue has been resolved in version 1.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
From @gr2m in https://github.com/actions/create-github-app-token/pull/54#discussion_r1344571256:
Notably, changing the input names affects the translated environment variable names[^1]:
my_var
is translated toINPUTS_MY_VAR
.my-var
is translated toINPUTS_MY-VAR
.So, we may want a plan for backwards-compatibility, or we may want to ship this in a major version bump.
[^1]: cf. “Metadata syntax for GitHub Actions > Example: Specifying inputs”