Write down that the site is being held, and what ends it - #60
Merged
Conversation
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
1 participant
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.
The live site is not deployed from main and has not been since 2026-08-21, and nothing in the repository says so. That is the kind of state that survives exactly as long as the person holding it in their head — the next
gh workflow run pages.ymlwithout a--refwould quietly publish a version that is still in review.So the
releaseskill now records three things, next to theworkflow_dispatchtrigger that explains why deploys are manual in the first place:Where the live site comes from.
site/1.0.0— main withsite/rolled back, after a push-triggered deploy on 2026-08-11 put 1.1.0's page live while 1.1.0 was unreleased and iOS 1.0.0 was still in review.Why the policy page is the exception. §6 tells App Review why the app asks to sense the room, so it had to be live before the visionOS build was submitted — and deploying main to get it would have taken the landing page along.
privacy.htmlalone was carried across and deployed from the branch. It is a shape worth reusing: a policy describing a version that has not shipped is written ahead of time, a landing page selling one is an advertisement for something nobody can buy.What ends the hold — 1.1.0 actually on the store, not approved, not submitted, live. Then deploy main and delete the branch and its environment policy.
Two traps kept from the first draft: the
v1.0.0tag is not 1.0.0's site (it predates publication, so its badge says "Coming soon" and links GitHub), and a ref outside thegithub-pagesenvironment's list fails in two seconds naming only the ref.Rebased onto current main, so it sits below the What's New paragraph #59 added rather than fighting it.