fix: remove workspaces and other dev fields from published package.json #371
Conversation
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
- Fixes #360: Yarn v1 warning about workspaces in published packages - Adds CI step to clean package.json before publishing - Removes workspaces, packageManager, scripts, and devDependencies from published package - Restores original package.json after publishing - Uses 'if: always()' to ensure restoration even if release fails
- Replace manual CI package.json cleaning with semantic-release plugin - Plugin automatically removes workspaces, packageManager, scripts, devDependencies - Maintains clean published package.json while preserving development setup - More maintainable and follows semantic-release best practices
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR fixes a Yarn v1 compatibility issue by configuring semantic-release to automatically remove development-only fields from the published package.json file. The changes ensure that fields like workspaces and other dev-specific configurations are stripped during the release process to prevent warnings.
- Adds the
@anolilab/semantic-release-clean-package-jsonplugin as a development dependency - Configures semantic-release to use explicit plugins including the new clean-package-json plugin
Reviewed Changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| package.json | Adds the semantic-release-clean-package-json plugin to devDependencies |
| .releaserc.json | Configures semantic-release with explicit plugins list including the clean-package-json plugin |
Files not reviewed (1)
- pnpm-lock.yaml: Language not supported
|
🎉 This PR is included in version 2.2.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
carlbray
pushed a commit
to carlbray/eslint-plugin-playwright
that referenced
this pull request
Aug 17, 2025
* fix: remove workspaces and other dev fields from published package.json - Fixes mskelton#360: Yarn v1 warning about workspaces in published packages - Adds CI step to clean package.json before publishing - Removes workspaces, packageManager, scripts, and devDependencies from published package - Restores original package.json after publishing - Uses 'if: always()' to ensure restoration even if release fails * refactor: use @anolilab/semantic-release-clean-package-json plugin - Replace manual CI package.json cleaning with semantic-release plugin - Plugin automatically removes workspaces, packageManager, scripts, devDependencies - Maintains clean published package.json while preserving development setup - More maintainable and follows semantic-release best practices * Cursor rules
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #360 - removes workspaces and other development-only fields from published package.json to prevent Yarn v1 warnings