ci: drop stale docs/ step blocking Deploy Website - #8
Merged
Conversation
Same fix as pr-checks (72f58f8): the standalone docs/ package was removed in the Astro/Starlight migration (2ce4da8); docs now build inside web/ via the Astro content collection. The leftover "Install docs dependencies" step ran npm ci in a nonexistent docs/ directory, failing Deploy Website on merge to master (and would fail the release workflows' deploy-web jobs too).
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.
Follow-up to #7. The Astro/Starlight migration removed the standalone top-level
docs/package (docs now build insideweb/as a Starlight content collection), but three workflows still had a leftover step runningnpm ciin the nonexistentdocs/directory:deploy.yml— failed on merge of Migrate docs to Astro/Starlight, move to freeoxide org, bump to 0.2.0 #7, blocking the production website deploy (11s, "No such file or directory")release.yml(Publish Crate → deploy-web job)changelog-release.yml(deploy-web job — about to fail the same way on the v0.2.0 release)The downstream
Buildstep runsbun run buildinweb/(the default working directory), so removing the dead install step is sufficient —web/is self-contained.Same root cause and fix as the
pr-checks.ymlchange in 72f58f8. Merging this re-triggers Deploy Website, which should now succeed.