Version Packages - #2
Merged
Merged
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
expo-cloudflared@4.2.2
Patch Changes
ccb003b: Setup is now a single
@expo/ngrokalias dependency that works identically on npm, yarn (v1 and Berry), pnpm, and bun — replacing the four per-package-manager recipes.The old recipe (
dependencies: expo-cloudflared+overrides/resolutions: @expo/ngrok) never creatednode_modules/@expo/ngrokin a normal Expo app: those fields only rewrite an existing dependency edge, and nothing depends on@expo/ngrok(Expo fetches it lazily at runtime). Expo therefore fell back to real ngrok. Declaring the alias as a direct dependency is what guarantees the path exists right afterinstall. Also documents the monorepo case — the alias goes in the workspace you runexpo startfrom — including the yarn-Berry gotcha thatresolutionsis honored only at the workspace root.