Skip to content

Default privatePackages.tag to true to match old buggy behavior - #1394

Closed
jakebailey wants to merge 1 commit into
changesets:mainfrom
jakebailey:private-packages-tag
Closed

jakebailey wants to merge 1 commit into
changesets:mainfrom
jakebailey:private-packages-tag

Conversation

@jakebailey

Copy link
Copy Markdown
Contributor

Per #1383 (comment)

Due to a bug fixed in #1361, tag: false did not actually have any effect, so private packages were still tagged. This surprised many people, so I think it may be worthwile to just default this to "true" to match the buggy behavior.

@changeset-bot

changeset-bot Bot commented Jun 24, 2024

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 94ab951

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages
Name Type
@changesets/config Patch
@changesets/apply-release-plan Patch
@changesets/cli Patch
@changesets/get-release-plan Patch

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

@codesandbox-ci

Copy link
Copy Markdown

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@jakebailey jakebailey closed this Jul 1, 2024
@snitovets

Copy link
Copy Markdown

That's why my packages stopped to have tags and therefor breaks the other steps. I'm glad that I found the reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants