You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ci(expo): combine unreleased clerk-ios bump changesets into one entry - #801
When clerk-ios ships more than once between clerk/javascript releases, this workflow writes one changeset per release. The @clerk/expo-native-components changelog then lists a bump line for each release (excerpt below), even though users only go from the version they had to the version they get.
The workflow now folds any unreleased expo-bump-clerk-ios-*.md changeset into the new one. The combined entry keeps the original "from" version and links every release in between. It deletes the old file and writes a new one, so the changelog credits the latest bump PR.
What to focus on
The node block in "Update Expo iOS SDK pin", which reads the "from" version and release links back out of the pending changeset text.
Testing
Ran this branch's "Update Expo iOS SDK pin" script against a clerk/javascript main checkout. With the two pending changesets on main and a 1.7.2 release, it wrote one entry from 1.6.2 to 1.7.2 with three release links and deleted both old files. A second run extended that combined entry. With nothing pending, the output matches today's. A rerun of an already pinned version still skips. actionlint passes.
Risk
Only changes the changeset files in the generated clerk/javascript PR. If a pending changeset can't be parsed, "from" falls back to the pinned version, as it does today.
How to revert
A plain revert is enough.
Screenshots / video
From the pending @clerk/expo-native-components@0.4.4 changelog in clerk/javascript#10571:
No actionable comments were generated in the recent review.
Walkthrough
The workflow now combines pending Expo iOS SDK bump changesets into one replacement. It follows version transitions, collects and deduplicates release links, and uses singular or plural release wording based on the link count. It removes the matching pending changesets and stages the .changeset directory.
No actionable merge-blocking issue is established; the workflow appears ready for normal validation and the required code-owner approval.
Pre-merge checks: 7
Check name
Status
Explanation
Title check
The title clearly states the main change: combining unreleased Clerk iOS bump changesets in the Expo workflow.
Description check
The description fills all required template sections and includes the rationale, review focus, testing details, risks, and rollback plan.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Testing, Risk, And Revert
The PR description includes all three required sections. Testing names the workflow script, pending changesets, output, deletion, rerun behavior, and actionlint. Risk explains the affected generated c…
Device Evidence
The pull request changes only .github/workflows/bump-javascript-expo-ios-sdk.yml. It does not change any file under Sources/ClerkKit/, Sources/ClerkKitUI/, or Examples/E2EHost/. Device evidenc…
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Full details: Testing, Risk, And Revert
Explanation
The PR description includes all three required sections. Testing names the workflow script, pending changesets, output, deletion, rerun behavior, and actionlint. Risk explains the affected generated changeset files and fallback behavior. How to revert states that a plain revert is sufficient.
Full details: Device Evidence
Explanation
The pull request changes only .github/workflows/bump-javascript-expo-ios-sdk.yml. It does not change any file under Sources/ClerkKit/, Sources/ClerkKitUI/, or Examples/E2EHost/. Device evidence is therefore not required.
Warning
Linked repositories: Some configured repositories could not be included in this review. Cross-repository analysis may be incomplete. Please check linked-repository access and settings.
CodeRabbit Verify
Run CodeRabbit Verify to test the changes in this pull request.
Recent review info
Automatic approval policy
Commit: 048ebbb665c1.
Setting
Effective value
Source
Automatic approvals
Enabled
Global configuration
Merge risk
Moderate
Global configuration
Security risk
Not set
Global configuration
Not set means no limit was configured after inheritance. Use @coderabbitai configuration to inspect the resolved settings and their sources.
Included review availability: This review used your included allowance. 9 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 10 reviews per hour.
This pull request changes files listed in .github/protected-paths, so it needs an approval from another Team Mobile member before it can merge. CodeRabbit's approval isn't enough for these files.
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
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.
What & why
@clerk/expo-native-componentschangelog then lists a bump line for each release (excerpt below), even though users only go from the version they had to the version they get.expo-bump-clerk-ios-*.mdchangeset into the new one. The combined entry keeps the original "from" version and links every release in between. It deletes the old file and writes a new one, so the changelog credits the latest bump PR.What to focus on
Testing
1.6.2to1.7.2with three release links and deleted both old files. A second run extended that combined entry. With nothing pending, the output matches today's. A rerun of an already pinned version still skips.actionlintpasses.Risk
How to revert
Screenshots / video
From the pending
@clerk/expo-native-components@0.4.4changelog in clerk/javascript#10571:🤖 Generated with Claude under Rob's supervision.