Add explicit release dispatch fallback #13

Merged
erik merged 1 commit from fix/task-a519f294-release-dispatch into main 2026-07-22 15:25:35 -05:00
Owner

Summary

Add an explicit publish fallback for Forgejo instances that do not start a workflow from a pushed tag.

Task

Task: #task-a519f294

Changes

  • accept an existing release tag and publish flag through workflow dispatch
  • apply the same version validation and direct Forgejo API upload path as tag-triggered runs
  • document the fj fallback command

Testing

  • Release workflow YAML validation
  • Release version tooling tests
  • Previous package validation run #41 built both platform artifacts

Checklist

  • Documentation updated
  • No unrelated changes included
## Summary Add an explicit publish fallback for Forgejo instances that do not start a workflow from a pushed tag. ## Task Task: #task-a519f294 ## Changes - accept an existing release tag and publish flag through workflow dispatch - apply the same version validation and direct Forgejo API upload path as tag-triggered runs - document the `fj` fallback command ## Testing - [x] Release workflow YAML validation - [x] Release version tooling tests - [x] Previous package validation run #41 built both platform artifacts ## Checklist - [x] Documentation updated - [x] No unrelated changes included
fix: add explicit release dispatch fallback
All checks were successful
CI / Rust build, lint, and test (pull_request) Successful in 12s
CI / Swift build, lint, and test (pull_request) Successful in 14s
bdfaba36e2
Task: #task-a519f294
Author
Owner

Review update

  • Summary: PR #13 adds a constrained manual-publish fallback for an existing semantic version tag while preserving the same version checks, package builds, automatic Forgejo token, private-CA verification, and direct release upload path.
  • Acceptance criteria: Release/version/package/checksum behavior remains covered; target-machine lifecycle checks remain deferred until the release is published.
  • Evidence: PR CI run #46 passed and manually dispatched package validation run #47 built both platform artifacts successfully.
  • Blocking issues: None.
  • Warnings: The manual fallback is needed because this Forgejo instance did not emit a release workflow run for the pushed v0.1.1 tag.
  • Result: warnings
  • Follow-up: Merge, dispatch publication for existing tag v0.1.1, and verify installed artifacts.
### Review update - **Summary:** PR #13 adds a constrained manual-publish fallback for an existing semantic version tag while preserving the same version checks, package builds, automatic Forgejo token, private-CA verification, and direct release upload path. - **Acceptance criteria:** Release/version/package/checksum behavior remains covered; target-machine lifecycle checks remain deferred until the release is published. - **Evidence:** PR CI run #46 passed and manually dispatched package validation run #47 built both platform artifacts successfully. - **Blocking issues:** None. - **Warnings:** The manual fallback is needed because this Forgejo instance did not emit a release workflow run for the pushed `v0.1.1` tag. - **Result:** warnings - **Follow-up:** Merge, dispatch publication for existing tag `v0.1.1`, and verify installed artifacts.
erik merged commit ef0e77109c into main 2026-07-22 15:25:35 -05:00
erik deleted branch fix/task-a519f294-release-dispatch 2026-07-22 15:25:35 -05:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
erik/kvshare!13
No description provided.