Skip to content

Commit 34a09db

Browse files
fix(pages): publish .well-known — the upload was stripping it (#105)
The canonical bundle was reaching `_site` and then being deleted on the way out. `actions/upload-pages-artifact` defaults to `include-hidden-files: false`, and its archiving step is a `tar` that carries `--exclude=.[^/]*`. That pattern matches every top-level entry beginning with a dot, so `.well-known/` was stripped from the artifact after the overlay step had placed it correctly. Evidence from the last run of `pages.yml` — the job's own output: ``` published tree: _site _site/.well-known _site/.well-known/ai.txt _site/.well-known/humans.txt _site/.well-known/security.txt ``` ...followed by a successful upload and a successful deploy, and then a 404 at `/.well-known/security.txt`. The overlay is not at fault; the upload is. `include-hidden-files: true` publishes dot-entries deliberately. `.git` and `.github` remain excluded by the action regardless. Confirmed by contrast: `ubicity`, the only repository in the estate that hand-rolls its `tar` (for SHA-pinning reasons), is the only one serving `security.txt`.
1 parent 09655dd commit 34a09db

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

.github/workflows/pages.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -71,6 +71,10 @@ jobs:
7171
uses: actions/upload-pages-artifact@fc324d3547104276b827a68afc52ff2a11cc49c9 # v5
7272
with:
7373
path: '_site'
74+
# actions/upload-pages-artifact strips dot-entries by default
75+
# (its tar runs --exclude=.[^/]*), which silently removed
76+
# .well-known/ from the artifact. Publish it deliberately.
77+
include-hidden-files: true
7478
deploy:
7579
environment:
7680
name: github-pages

0 commit comments

Comments
 (0)