ci: Fix docs building after the pnpm migration#1149
Merged
Conversation
github-actions
Bot
added
the
t-management
vladfrangu
approved these changes
May 20, 2026
Member
vladfrangu
left a comment
vladfrangu
left a comment
There was a problem hiding this comment.
I thought git ignored invalid files when staging, or so I remember. anyways, fast tracking
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
3 participants
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.
After the NPM -> PNPM migration, the
website/package-lock.jsonfile no longer exists. Thesigned-commitaction is still trying to stage it during the docs build, and it throws an error on that.This fixes it.