Repository navigation
Conversation
Make @callstack/repack-expo publishable: drop private, add a public publishConfig, set the version to the published 0.0.1 alpha, and stop ignoring it in changesets so future releases go through the normal flow.
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
Makes
@callstack/repack-expoa publishable package.0.0.1has already been published manually to npm under thealphatag, so the package exists on the registry and can be released through the normal changesets flow from now on.private: trueand add a publicpublishConfigmatching the other plugins0.0.1to match what is publishedignorelist so changesets can version it (it is versioned independently, outside the 5.xfixedgroup)@callstack/repack-expo@alpha)No changeset is included:
0.0.1is already on npm, sochangeset publishwill skip it.Before merging
@callstack/repack-expo(GitHub Actions,callstack/repack, workflowrelease.yml) so the release job can publish future versions via OIDCNotes
Because
0.0.1was the first version, npm also pointedlatestat it. A regular changeset for this package will publish the next version aslatest. To keep automated releases onalpha, changesets pre mode would be needed, and that applies to the whole repo.Test plan
pnpm --filter @callstack/repack-expo... build,typecheck,testpnpm pack:workspace:^rewritten to^5.4.2, CLI shebang present, no staledistfilesnpm view @callstack/repack-expo dist-tags→alpha: 0.0.1