Skip to content

feat(pages)!: require artifact-path input#207

Merged
DevSecNinja merged 1 commit into
mainfrom
feat/pages-require-artifact-path
Jun 23, 2026
Merged

feat(pages)!: require artifact-path input#207
DevSecNinja merged 1 commit into
mainfrom
feat/pages-require-artifact-path

Conversation

@DevSecNinja

Copy link
Copy Markdown
Owner

Summary

artifact-path defaulted to ".", so a caller that doesn't set it silently publishes the entire repo root to GitHub Pages / Cloudflare — including README.md, config files, lockfiles, and other repo internals. This makes artifact-path required: true (no default) so every caller declares exactly what to publish.

Changes

  • artifact-path: required: false + default: "."required: true (default removed). Description unchanged.

Breaking change

This is a breaking change to the reusable workflow: existing callers that relied on the "." default must now pass artifact-path explicitly. Marked with feat(pages)! + a BREAKING CHANGE: footer so release-please bumps the major version and Renovate won't automerge the bump for downstream consumers.

Migration for callers:

with:
  artifact-path: "public"   # or "." to keep previous whole-root behavior

The DevSecNinja/edu-auth consumer is already updated to pass artifact-path: "public", so it's ready for this once it bumps the pin.

Validation

YAML parses; the change was diff-verified byte-identical against the current main file with only the artifact-path block modified.

Remove the `"."` default from `artifact-path` and make it `required: true`.
Defaulting to the repo root silently publishes everything (READMEs, configs,
build metadata); callers should declare exactly what to publish.

BREAKING CHANGE: callers of the reusable Pages workflow must now pass
`artifact-path` explicitly (e.g. `artifact-path: "public"` or `"."`).
@DevSecNinja DevSecNinja merged commit 6197650 into main Jun 23, 2026
16 checks passed
@DevSecNinja DevSecNinja deleted the feat/pages-require-artifact-path branch June 23, 2026 17:07
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