Update release workflow commit identity

[yedhink]

Fixes #35

[neeto-bugwatch]

🤖 NeetoBugWatch Review

I've analyzed your pull request and found some potential improvements that might be worth considering. Please review the specific line comments below for helpful suggestions.

💡 To trigger a re-review of this PR, add a comment with the keyword neeto-bugwatch-run anywhere in the comment body.

Tip

Verdict: Good to merge — 1 minor suggestion, no significant issues found

Click to copy prompt for AI agent

Verdict: minor_issues

The following are code review comments from an AI reviewer that only has access
to the PR diff, not the full codebase. Treat every comment as a hypothesis,
not a fact. For each comment:

1. Investigate the verification questions against the full codebase first.
2. Go beyond the provided questions. Use your full codebase access to ask your
   own questions, check related code paths, and consider edge cases that the
   reviewer could not have seen from the diff alone.
3. Only implement the suggested fix if your investigation confirms the issue is real.
4. If the issue is not real, skip it entirely. Do not implement speculative fixes.

Prioritize by severity (critical > major > minor > trivial) and confidence score.
Only attend to comments with confidence below 0.5 if your investigation proves them valid.

[
  {
    "file_path": ".github/workflows/publish.yml",
    "line_number": 29,
    "comment": "Hardcoding a specific individual's name and email associates all automated workflow commits with their personal account. It is generally recommended to use the standard GitHub Actions bot account to clearly distinguish automated actions from human commits and to avoid issues if the individual changes roles or leaves.",
    "confidence": 0.9,
    "severity": "trivial",
    "suggested_fix": "Consider using the standard GitHub Actions bot credentials, such as setting the name to 'github-actions[bot]' and the email to '41898282+github-actions[bot]@users.noreply.github.com'.",
    "verification_questions": [
      "Is there a strict organizational requirement for these automated commits to be attributed to a specific individual rather than a generic bot?"
    ]
  }
]

[neeto-bugwatch]

Hardcoding a specific individual's name and email associates all automated workflow commits with their personal account. It is generally recommended to use the standard GitHub Actions bot account to clearly distinguish automated actions from human commits and to avoid issues if the individual changes roles or leaves.

Click to see review metadata

{
  "confidence": 0.9,
  "severity": "trivial",
  "suggested_fix": "Consider using the standard GitHub Actions bot credentials, such as setting the name to 'github-actions[bot]' and the email to '41898282+github-actions[bot]@users.noreply.github.com'.",
  "verification_questions": [
    "Is there a strict organizational requirement for these automated commits to be attributed to a specific individual rather than a generic bot?"
  ]
}