fix(release): fall back to skeleton init on uninitialized template repo - #76
Merged
Conversation
The Release workflow previously hard-failed when ext/ was uninitialized (the pskel template repository itself). Restore the dummy fallback: the Source job initializes the default skeleton via "pskel init skeleton" (same pattern as the CI init jobs), uploads the initialized ext as an artifact, and the Windows matrix downloads it before staging sources. Downstream projects with an initialized ext are unaffected. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Summary
The Release workflow hard-failed on the pskel template repository itself because
ext/is uninitialized. This restores the dummy fallback:Sourcejob: whenext/.gitkeepmarks the project uninitialized, runpskel init skeleton(same pattern as the CI init jobs) instead of erroring, and upload the initializedext/as an artifactWindowsjob: download the initialized extension artifact before staging sources so the matrix builds work in the fallback caseext/are unaffected (needs-init=falseskips all fallback steps; thecomposer.jsonguard remains)Note: rerunning the failed release run will not pick up this fix — tag-push runs use the workflow at the tagged commit, so the tag needs to be re-created on the fixed main (or push a new tag).
🤖 Generated with Claude Code