feat(changesets-renovate): filter out private packages#2545
Open
silouanwright wants to merge 2 commits intoscaleway:mainfrom
Open
feat(changesets-renovate): filter out private packages#2545silouanwright wants to merge 2 commits intoscaleway:mainfrom
silouanwright wants to merge 2 commits intoscaleway:mainfrom
Conversation
🦋 Changeset detectedLatest commit: d4baef6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Author
|
👋 |
ea4e8bc to
aba524c
Compare
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
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.
In a monorepo, people may choose to have some packages published, and keep other packages private.
Private packages (which are represented with a
private: truekey) ideally shouldn't be published. An example below:{ "name": "@scope/package-name", "version": "0.0.0", "private": true, "description": "An internal package for providing a shared configuration to apps", "main": "./index.js", }In the original GitHub Action from Backstage this is based off, the code is in fact filtering out private packages:
Would love to see that functionality represented in this package as well.