Skip to content

ci(release): create the GitHub release on tag pushes (hex.pm-only was only half the story) - #3

Merged
jgnagy merged 1 commit into
mainfrom
fix/release-workflow-github-release
Oct 27, 2026
Merged

jgnagy merged 1 commit into
mainfrom
fix/release-workflow-github-release

Conversation

@jgnagy

@jgnagy jgnagy commented Oct 27, 2026

Copy link
Copy Markdown
Member

The release workflow published to hex.pm but never created a GitHub release — the step didn't exist (nothing broken; the authify/authify repo carries a second create-release job this library never got). This ports that job, adapted for a Hex library: triggers after the publish job succeeds, contents: write permission, notes assembled from CHANGELOG.md's version section (Keep-a-Changelog) plus the commit list and the hex install line. The v0.1.1 release object itself is being created retroactively alongside this fix; future tags get it automatically.

…attern)

The release workflow only published to hex.pm — nothing created the
GitHub release, so tags produced no release objects (hex.pm got 0.1.1
but GitHub shows no v0.1.1 release). This ports the authify/authify
create-release job, adapted: needs the publish job, contents:write
permission, full-history checkout, notes from CHANGELOG.md's
Keep-a-Changelog section for the version plus the commit list and a hex
install line (instead of the Docker section).
@jgnagy
jgnagy merged commit 59371fb into main Oct 27, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant