chore: mark journey package as private#19
Merged
Conversation
- Set private: true to prevent changesets from attempting to publish - Allows release workflow to succeed for other packages - Journey package can be made public later when ready
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
2 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.
Summary
Marks the
@lytics/playwright-journeypackage as private to prevent changesets from attempting to publish it.Problem
The release workflow was failing because changesets was trying to publish
@lytics/playwright-journey@0.1.1, but the package doesn't exist on npm yet (404 error). This caused the entire workflow to fail, preventing GitHub releases from being created.Solution
Mark the package as
private: trueso changesets will skip it during publishing. This allows:Impact