Open
Conversation
|
Build successful! 🎉 |
|
Build successful! 🎉 |
LFDanLu
commented
May 2, 2026
| "version:nightly": "yarn workspaces foreach --all --no-private -t version -d 3.0.0-nightly-$(git rev-parse --short HEAD)-$(date +'%y%m%d') && yarn apply-nightly --all", | ||
| "publish:nightly": "yarn workspaces foreach --all --no-private -t npm publish --tag nightly --access public", | ||
| "build:api-published": "node scripts/buildPublishedAPI.js", | ||
| "build:api-published": "node scripts/buildBranchAPI.js --githash=$(git log --grep='^Publish$' --oneline -1 | awk '{print $1}') --output=base-api", |
Member
Author
There was a problem hiding this comment.
fixes yarn check-published-apis by comparing vs the last publish commit instead of pulling from npm (see #9917 (comment)). base-api here is to point it to a different dist dir since buildBranchAPI uses branch-api by default
|
Build successful! 🎉 |
|
Build successful! 🎉 |
|
Build successful! 🎉 |
|
Build successful! 🎉 |
|
Build successful! 🎉 |
|
Build successful! 🎉 |
|
Build successful! 🎉 |
|
Build successful! 🎉 |
|
Build successful! 🎉 |
|
Build successful! 🎉 |
|
Build successful! 🎉 |
|
Build successful! 🎉 |
…ommit rather than just last week the latter is to handle the case where we run this flow multiple times a day or in the same week and there arent any new changes. Previously it would still use the current weeks diff results rather than reporting that there are no changes
running diff right after new release when there are new changes, running diff between releases, where there are no changes between last run, and when there are no changes from the released code
|
Build successful! 🎉 |
|
Build successful! 🎉 |
|
Build successful! 🎉 |
LFDanLu
changed the title
|
Build successful! 🎉 |
|
Build successful! 🎉 |
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
2 participants
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.
Github actions workflows for Chromatic and TSDiffer. I've tested the TSDiffer flow locally, but the github actions are untested yet. Whole lotta AI stuff here, but I've looked over it and it seems ok
✅ Pull Request Checklist:
📝 Test Instructions:
🧢 Your Project:
RSP