Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
N
next.js
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Alex
next.js
Commits
5c165904
Unverified
Commit
5c165904
authored
Apr 27, 2026
by
Sebastian "Sebbie" Silbermann
Committed by
GitHub
Apr 27, 2026
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[ci] Automatically start React sync when new `react@experimental` is available (#93235)
parent
16e5f9e6
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
69 additions
and
0 deletions
+69
-0
update_react_poller.yml
.github/workflows/update_react_poller.yml
+69
-0
No files found.
.github/workflows/update_react_poller.yml
0 → 100644
View file @
5c165904
name
:
Poll React Sync
on
:
schedule
:
# GitHub runs cronjobs at most every 5 minutes.
# Ideally we get 2 minutes or lower which is what we used to have with Vercel cronjobs.
-
cron
:
'
*/5
*
*
*
*'
concurrency
:
group
:
poll-react-sync
cancel-in-progress
:
true
jobs
:
poll
:
runs-on
:
ubuntu-latest
permissions
:
actions
:
write
steps
:
# We're using react@experimental as a signal for a new React sync because
# in facebook/react we publish experimental after canary. If we would just
# look at canary, we might update before experimental is published.
-
name
:
Fetch latest react@experimental version
id
:
current
run
:
|
CURRENT=$(npm --silent view --json react@experimental version | tr -d '"')
if [ -z "$CURRENT" ]; then
echo "Failed to resolve react@experimental version" >&2
exit 1
fi
echo "version=$CURRENT" >> "$GITHUB_OUTPUT"
echo "Current react@experimental: $CURRENT"
-
name
:
Check whether this version was already seen
id
:
cache
uses
:
actions/cache@v4
with
:
# The key encodes the version. Cache hit = already processed; cache miss = new version.
# The path just needs to exist so the post-step can save the cache entry on a miss.
path
:
.cache/marker
key
:
react-experimental-${{ steps.current.outputs.version }}
-
name
:
Mark version as seen
if
:
steps.cache.outputs.cache-hit != 'true'
run
:
|
mkdir -p .cache
printf '%s' '${{ steps.current.outputs.version }}' > .cache/marker
-
name
:
Resolve corresponding react@canary version
id
:
canary
if
:
steps.cache.outputs.cache-hit != 'true'
run
:
|
CANARY=$(npm --silent view --json react@canary version | tr -d '"')
if [ -z "$CANARY" ]; then
echo "Failed to resolve react@canary version" >&2
exit 1
fi
echo "version=$CANARY" >> "$GITHUB_OUTPUT"
echo "Current react@canary: $CANARY"
-
name
:
Dispatch update_react.yml
if
:
steps.cache.outputs.cache-hit != 'true'
env
:
GH_TOKEN
:
${{ secrets.GITHUB_TOKEN }}
GH_REPO
:
${{ github.repository }}
EXPERIMENTAL
:
${{ steps.current.outputs.version }}
CANARY
:
${{ steps.canary.outputs.version }}
run
:
|
echo "react@experimental changed to $EXPERIMENTAL. Dispatching update_react.yml with react@canary=$CANARY."
gh workflow run update_react.yml --ref ${{ github.ref_name }} -f version="$CANARY"
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment