fix: remove pnpm-workspace.yaml configuration that breaks CI/CD#73
Merged
fix: remove pnpm-workspace.yaml configuration that breaks CI/CD#73
Conversation
The pnpm-workspace.yaml file was missing the required 'packages' field and caused CI/CD pipeline failures with ERR_PNPM_INVALID_WORKSPACE_CONFIGURATION. Since this is a single-package application (not a monorepo), the workspace configuration is unnecessary and should be removed. Closes #72
Update all GitHub Actions workflows (build, test, deploy) from pnpm v8 to v10 to match the local development environment and fix lockfile compatibility issues. This ensures consistent behavior between local development and CI/CD pipelines. Closes #72
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
Fixes the CI/CD pipeline failure caused by the invalid
pnpm-workspace.yamlconfiguration.Problem
The
pnpm install --frozen-lockfilecommand in GitHub Actions was failing with:Root Cause
The
pnpm-workspace.yamlfile was present but missing the requiredpackagesfield. Since this is a single-package application (not a monorepo), the workspace configuration is unnecessary and causes validation failures.Solution
Removed the
pnpm-workspace.yamlfile entirely. This allows pnpm to operate in single-package mode without workspace validation errors.Closes #72