thidev/hermes-compagnon
Watch
2
0
Fork
You've already forked hermes-compagnon
 0
Code Issues Pull requests Projects Releases 3 Packages Wiki Activity Actions

ci(server): publish a Forgejo release on server-v* tags #3

Merged
speedi57 merged 1 commit from ci/server-release into main 2026-10-18 13:12:43 +00:00
Conversation 0 Commits 1 Files changed 3 +26 -3
hermes commented 2026-10-18 13:01:31 +00:00
Owner
Copy link

Summary

 release job (tag server-v*)
   build --release --locked
   package  dist/{binary,sha256,config.example.toml}
   upload-artifact            # only visible on the run page
+  POST /api/v1/repos/…/releases          # creates the Release for the tag
+  POST …/releases/{id}/assets (x3)       # binary, sha256, example config
  • Crate bumped to 0.1.1 (the server-v0.1.0 tag already ran without creating a release).

Evidence

  • Before: tag server-v0.1.0 → run #53 green, but Releases page empty (artifact only).
    After: not run yet — needs a server-v0.1.1 tag after merge. YAML parses; cargo build --locked ok with the bumped lockfile.

Merge Danger

Door: two-way

Blast Radius: CI

Only runs on server-v* tags. Uses secrets.RELEASE_TOKEN if set, else the job token; if that token cannot write releases the step fails with a 403 and the fix is adding RELEASE_TOKEN (write:repository).

## Summary ```diff release job (tag server-v*) build --release --locked package dist/{binary,sha256,config.example.toml} upload-artifact # only visible on the run page + POST /api/v1/repos/…/releases # creates the Release for the tag + POST …/releases/{id}/assets (x3) # binary, sha256, example config ``` - Crate bumped to `0.1.1` (the `server-v0.1.0` tag already ran without creating a release). ## Evidence - **Before:** tag `server-v0.1.0` → run #53 green, but Releases page empty (artifact only). **After:** not run yet — needs a `server-v0.1.1` tag after merge. YAML parses; `cargo build --locked` ok with the bumped lockfile. ## Merge Danger **Door:** two-way **Blast Radius:** CI Only runs on `server-v*` tags. Uses `secrets.RELEASE_TOKEN` if set, else the job token; if that token cannot write releases the step fails with a 403 and the fix is adding `RELEASE_TOKEN` (write:repository).
ci(server): publish a Forgejo release with the binary on server-v* tags
All checks were successful
server / Check (fmt, clippy, tests) (pull_request) Successful in 1m42s
Details
server / Build release binary (tags server-v* only) (pull_request) Has been skipped
Details
38d866272e 
The workflow only uploaded a run artifact, so no release appeared. Create
the release through the API and attach binary, sha256 and example config.
Bump the crate to 0.1.1 so a fresh server-v0.1.1 tag can be cut.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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
thidev/hermes-compagnon!3
No description provided.