Publish tags to FlakeHub

[lucperkins]

Summary by CodeRabbit

• Chores
  • Enhanced automated release publishing infrastructure to streamline distribution of new versions.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new GitHub Actions workflow that automatically publishes semantic version tags to FlakeHub. The workflow triggers on tag creation or manual dispatch, checks out the repository, initializes Nix, and pushes the package to FlakeHub with public visibility settings.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow .github/workflows/flakehub-publish-tagged.yaml	New workflow file for publishing tagged releases to FlakeHub. Triggers on semantic version tags or manual dispatch, runs Determinate's nix action, and publishes using flakehub-push with public visibility targeting the designated repository.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

• gustavderdrache

Poem

🐰 A tag is born, so fresh and new,
FlakeHub awaits a release from you,
Nix builds up, with deterministic care,
Published to the world, a gift we share! 🎁✨

🚥 Pre-merge checks | ✅ 3

✅ 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 directly and clearly describes the main change: introducing a workflow to publish tags to FlakeHub.
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
• Post copyable unit tests in a comment
• Commit unit tests in branch flakehub-publish-tagged

---

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: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/flakehub-publish-tagged.yaml:
- Around line 21-26: The workflow uses movable refs for third-party actions
(actions/checkout@v6, DeterminateSystems/determinate-nix-action@v3,
DeterminateSystems/flakehub-push@main); replace each tag/branch ref with the
corresponding full commit SHA for the specific release you reviewed (pin
actions/checkout, determinate-nix-action, and flakehub-push to their full-length
commit hashes), update the workflow inputs to use those SHAs, and commit the
change so the publish job runs only known immutable versions.
- Line 6: Replace the loose regex v?[0-9]+.[0-9]+.[0-9]+* used for the tag
trigger with a stricter SemVer pattern that requires the leading "v" and proper
escaping/anchors (for example ^v[0-9]+\.[0-9]+\.[0-9]+$) so the workflow's tag
filter matches the flakehub-push "tag" input contract; update the regex string
shown in the diff accordingly and verify it is used where the workflow defines
the tag trigger.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6a650234-2c10-4f2f-957b-c6308957e06f

📥 Commits

Reviewing files that changed from the base of the PR and between 98a3561 and 2d0605f.

📒 Files selected for processing (1)

• .github/workflows/flakehub-publish-tagged.yaml