Summary
The public action exposes a commit-message input, but the core action currently ignores it and always commits with a hardcoded message.
Evidence
- Public action documents/exposes
commit-message in action.yml
- README also documents
commit-message as configurable
- Core implementation hardcodes the commit message in
.github/actions/core/src/index.ts:
await git.commit(`chore: bump version to ${newVersion}`);Why this matters
This creates a contract mismatch between the documented API and the actual behavior. Users may assume they can customize the commit message, but the input currently has no effect.
Expected behavior
If commit-message is provided, the action should use it when creating the version bump commit (potentially with a placeholder for the computed version if desired).
Possible implementation ideas
- Respect the
commit-message input directly
- Optionally support a placeholder like
@NEW_VERSION@ in the custom message
- Add/adjust tests to cover custom commit messages
Summary
The public action exposes a
commit-messageinput, but the core action currently ignores it and always commits with a hardcoded message.Evidence
commit-messageinaction.ymlcommit-messageas configurable.github/actions/core/src/index.ts:Why this matters
This creates a contract mismatch between the documented API and the actual behavior. Users may assume they can customize the commit message, but the input currently has no effect.
Expected behavior
If
commit-messageis provided, the action should use it when creating the version bump commit (potentially with a placeholder for the computed version if desired).Possible implementation ideas
commit-messageinput directly@NEW_VERSION@in the custom message