chore: add a release automation workflows

[cdunster]

This uses the new Node.js common workflows from the Holochain actions repo, added in holochain/actions#10. These can't really be tested until they are merged to main.

Closes #62.

[cocogitto-bot]

✔️ cf6a91f...147c26f - Conventional commits check succeeded.

[coderabbitai]

Walkthrough

This PR adds release automation to the hc-spin repository by introducing two new GitHub Actions workflows that implement a two-stage release process. The release-prepare workflow is manually triggered and delegates to an external reusable workflow for release preparation with yarn and version management. The release-publish workflow automatically triggers on main branch pushes and delegates to a reusable workflow for npm publishing. Both workflows are configured to use yarn as the package manager and pass appropriate secrets for GitHub and npm authentication.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Linked Issues check	❓ Inconclusive	The PR partially addresses the requirements. It adds two workflow files (release-prepare.yml and release-publish.yml), but the implementation relies on external reusable workflows rather than implementing the full requirements inline.	Verify that the delegated reusable workflows (holochain/actions v1.9.0) fully implement the AC: workflow_dispatch trigger with git-cliff/version input, and publish workflow that checks release label, creates tags, and publishes to npm.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: adding release automation workflows. It is specific and directly related to the changeset.
Description check	✅ Passed	The description is related to the changeset, explaining that the PR introduces release automation using new Node.js common workflows from holochain/actions and closes issue #62.
Out of Scope Changes check	✅ Passed	Both workflow files are directly related to the stated objective of adding release automation. No out-of-scope changes are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 62-add-a-release-on-tag-workflow

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/release-publish.yml:
- Line 9: Replace the mutable tag reference to the reusable workflow with an
immutable commit SHA: locate the line containing "uses:
holochain/actions/.github/workflows/nodejs-publish-release.yml@v1.9.0" and swap
the `@v1.9.0` suffix for the full 40-character commit SHA for that target commit
(e.g., @<commit-sha>), ensuring you pick the exact commit corresponding to the
intended release and update the workflow file accordingly so the job "publish"
uses the pinned commit.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 30ee29a4-d24a-4328-9fef-ec44e1e0cf54

📥 Commits

Reviewing files that changed from the base of the PR and between 5b11212 and 147c26f.

📒 Files selected for processing (2)

• .github/workflows/release-prepare.yml
• .github/workflows/release-publish.yml