Our three website repos share a release story that has no pack: they hand-roll their versioning and their Pages deploy.
Two things:
-
Date-anchored version numbering — v<major>.<ymmdd>.<n>, where ymmdd is the last digit of the year followed by MMDD. The plain MMDD form isn't monotonic across a year boundary (1.1231.3 > 1.0101.1); prefixing the year digit fixes it (1.61231.3 → 1.70101.1). <n> is the day's release counter: 1 for the day's first release, previous + 1 for each further release the same day. <major> absorbs the decade wrap (9xxxx → 0xxxx) so ordering holds forever.
-
A static-website pack — the standard for a plain static site: release-on-push to main, the version bump, the GitHub Release, the Pages deploy, PR CI (tests + the conformance sweep), and the one-time repo settings that can only be turned on by hand (tracked as an adoption issue in the adopting repo, not as a repo file). Adoption asks the one genuine fork in the road — is this simple GitHub Pages serving, or does the site deploy elsewhere. The published artifact is an explicit publish set declared by the repo (like the chrome pack's ship_paths), never "the repo root minus the agent dirs".
Our three website repos share a release story that has no pack: they hand-roll their versioning and their Pages deploy.
Two things:
Date-anchored version numbering —
v<major>.<ymmdd>.<n>, whereymmddis the last digit of the year followed byMMDD. The plainMMDDform isn't monotonic across a year boundary (1.1231.3>1.0101.1); prefixing the year digit fixes it (1.61231.3→1.70101.1).<n>is the day's release counter: 1 for the day's first release, previous + 1 for each further release the same day.<major>absorbs the decade wrap (9xxxx→0xxxx) so ordering holds forever.A
static-websitepack — the standard for a plain static site: release-on-push tomain, the version bump, the GitHub Release, the Pages deploy, PR CI (tests + the conformance sweep), and the one-time repo settings that can only be turned on by hand (tracked as an adoption issue in the adopting repo, not as a repo file). Adoption asks the one genuine fork in the road — is this simple GitHub Pages serving, or does the site deploy elsewhere. The published artifact is an explicit publish set declared by the repo (like the chrome pack'sship_paths), never "the repo root minus the agent dirs".