ci: bump release actions

[mattyg]

The prepare-release job was failing when running an outdated version of cargo-semver-checks that didn't support the cargo docs json generated since we've bumped the rust-toolchain version in this repo.

Summary by CodeRabbit

• Chores
  • Updated GitHub Action workflow versions to the latest versions to improve CI/CD pipeline stability and ensure access to workflow enhancements.

[cocogitto-bot]

✔️ e1195dc - Conventional commits check succeeded.

[coderabbitai]

Walkthrough

Both GitHub workflow files are updated to reference newer versions of their respective reusable workflows, upgrading from v1.1.0 to v1.3.0. No logic, inputs, secrets, or control flow changes are made.

Changes

Cohort / File(s)	Summary
GitHub Workflow Version Updates .github/workflows/prepare-release.yml, .github/workflows/publish-release.yml	Updates referenced GitHub Actions/reusable workflow versions from v1.1.0 to v1.3.0; no logic or configuration changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'ci: bump release actions' accurately describes the main change—updating GitHub Actions workflow versions in CI configuration files from v1.1.0 to v1.3.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ci/bump-release-actions

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d9402ff and e1195dc.

📒 Files selected for processing (2)

• .github/workflows/prepare-release.yml (1 hunks)
• .github/workflows/publish-release.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)

• GitHub Check: test (x86_64, 29, 26.0.10792818, go-pion)
• GitHub Check: test (x86_64, 33, 26.0.10792818, go-pion)
• GitHub Check: test (x86_64, 33, 26.0.10792818, datachannel)
• GitHub Check: test (x86_64, 29, 26.0.10792818, datachannel)
• GitHub Check: Test (macos-latest)
• GitHub Check: Test (windows-latest)
• GitHub Check: Test (ubuntu-latest)

🔇 Additional comments (2)

.github/workflows/prepare-release.yml (1)

14-14: Verify the version bump to v1.3.0 is compatible with workflow inputs.

The workflow reference is upgraded from v1.1.0 to v1.3.0. Ensure that:

1. The v1.3.0 tag exists in the holochain/actions repository
2. The input parameters (cliff_config, force_version) remain compatible
3. The secret HRA2_GITHUB_TOKEN is still accepted by the new version

.github/workflows/publish-release.yml (1)

13-13: Verify the version bump to v1.3.0—manual check required.

The version upgrade from v1.1.0 to v1.3.0 requires manual verification since automated tools are currently unavailable. Before merging, ensure:

1. The v1.3.0 tag exists in the holochain/actions repository
2. Review the changelog/release notes between v1.1.0 and v1.3.0 for any breaking changes
3. Confirm that the secrets passed (HRA2_GITHUB_TOKEN, HRA2_CRATES_IO_TOKEN) remain compatible with the new version
4. Test the workflow in a non-production environment if possible

---

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.}