[harshitethic]

What

Closes #86.

When release (or the deprecated version input) receives GitHub's ${{ github.ref }}, the action already strips refs/tags/ but leaves refs/heads/ intact. A release-candidate branch passed as refs/heads/release-candidate-1 then fails release-name validation.

Changes

• Strip the refs/heads/ prefix in addition to refs/tags/ for explicit release inputs.
• Preserve existing plain release values and leave unrelated ref namespaces unchanged.
• Add parameterized regression tests for both release and version input variants.

Verification

• yarn test --runInBand: 58 tests passed.
• yarn lint: passed.
• git diff --check: passed.

This intentionally does not rename slash-containing branch paths; it only removes the GitHub ref namespace as requested. AI-assisted patch, locally validated.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 0e74f57. Configure here.}

[andreiborza]

Hi @harshitethic, thanks for the contribution.

You need to run the pre-commit hooks that will automatically build a new dist file and update the action's docker tag so it can be tested.

[harshitethic]

Thanks for the review — I’ve addressed the generated-artifact requirements on this branch.

• dist/index.js now includes the refs/heads/ prefix handling; rebuilding locally with yarn build produces no diff in the committed bundle.
• action.yml uses the branch-specific Docker tag fix-strip-head-ref-86-20261023. Running yarn set-docker-tag-from-branch produces no diff.
• Local verification: yarn format-check passed, yarn lint passed, yarn build passed, and yarn test --runInBand passed (58 tests).

The GitHub Actions workflows for this fork currently report action_required; maintainer approval may be needed before they can run. Happy to address anything those checks find.