chore: add changeset for #24 feature-flag defaults fix#28
Merged
Conversation
PR #25 (the implementation) was merged without a changeset, so the fix has not appeared in any release yet. This adds the missing changeset so the next release publishes the feature-flag fix. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
srsholmes
added a commit
that referenced
this pull request
May 1, 2026
The .changeset/feature-flag-defaults.md was added in dee332f to ensure the #24 feature-flag fix shipped, but PR #28 carried that changeset to main on its own and 0.1.4 has now been published. Removing the file here so the next release (driven by this PR's cache-race changeset) contains only the cache-race entry. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
PR #25 was merged without a
.changeset/*.mdfile, so its fix has not appeared in any release. This adds the missing changeset so the next release publishes the feature-flag-defaults fix as a standalone patch.Why a separate PR
So #24/#25 ships as its own release (e.g.
0.1.4) rather than being bundled with the cache race-condition fix in #26 (which will then ship as0.1.5).After merging
changesets/actionopens a Version PR bumping0.1.3 → 0.1.4with this entry in CHANGELOG.@srsholmes/vitest-react-native@0.1.4to npm.0.1.5.🤖 Generated with Claude Code