Repository navigation
fix: keep the landing page version current and credit the author - #232
Merged
Merged
Conversation
The landing page header badge and footer still said v0.1.6 and its structured data said 0.1.3, long after v0.4.1 shipped; all three now say v0.4.1. The footer credits the author with a link to their site, and the structured-data author gains the @id that site uses for its Person so both describe one person.
voyvodka
enabled auto-merge (squash)
October 14, 2026 11:53
voyvodka
disabled auto-merge
October 14, 2026 11:53
The landing page version was typed by hand and had fallen three minor releases behind. index.html now carries a {{version}} placeholder that the Pages workflow replaces with the newest v<major>.<minor>.<patch> tag, failing the deploy if no tag is found or a placeholder survives. The workflow also runs after every successful Release run, through workflow_run because the github-pages environment only deploys from main and a tag-triggered run would be refused.
voyvodka
enabled auto-merge (squash)
October 14, 2026 11:54
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
index.html, served at webhook.sametozkan.com.tr) showed v0.1.6 in the header badge and footer and 0.1.3 in its structured data; the latest release is v0.4.1.index.htmlcarries a{{version}}placeholder in those three places, and the Pages workflow fills it from the newestv<major>.<minor>.<patch>git tag at deploy time. The deploy fails if no such tag exists or a placeholder is left in the page.workflow_run), so a new tag updates the page without touchingindex.html. A tag-triggered run would execute onrefs/tags/*, which thegithub-pagesenvironment refuses (its branch policy allows onlymain);workflow_runexecutes on the default branch. Checkout pins the default branch so a release never deploys an olderindex.html.MIT License · v0.4.1 · by Samet Özkan, linking to https://www.sametozkan.com.tr/ (rel="author"); the structured-dataauthorgains the@idthat site uses for its Person.[Unreleased] → Fixed.The GitHub Release object is created by hand after the tag, so the tag (which also drives Docker and NuGet publishing) is the version source, not the Releases API.
Test plan
v0.4.1, all three placeholders replaced, JSON-LD parses withsoftwareVersion: "0.4.1"