-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[chore] Improve release tooling #10516
Conversation
step "manual tests: Run the EE tests" | ||
echo "Copy the the packages folder content inside the node_modules of ra-enterprise, then run a full build and run the tests" | ||
echo "Tip: You can use the 'copy-ra-oss-packages-to-ee.sh' script if you have it" | ||
echo "Press Enter when this is done" | ||
read |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should agree on a directory structure and do this automatically
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes I have plans for this, but will do that in a later PR (hopefully)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is really cool!
scripts/update-changelog.ts
Outdated
'[demo]', | ||
'[website]', | ||
'[storybook]', | ||
'[demo]', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
demo is there twice
Back to WIP as I need to check the github tag will happen before the |
All fixed! back to RFR! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome!
Problem
A large part of the react-admin release process is manual, thus cumbersome and prone to errors.
Solution
Further automate the release process.
Script these steps and include them in the npm lifecycleOut of scope
Some release steps are not automated yet (due to time constraints).
Examples:
How To Test
These scripts support a
RELEASE_DRY_RUN
env variable allowing to skip all mutations to git, GitHub or npm, except 1 git commit (but not pushed!) from lerna.First, create a
.env
file from the.env.template
file and fill it in with your Github token.Then run:
When this is done, don't forget to revert the commit created by lerna to update the versions:
Additional Checks
master
for a bugfix, ornext
for a feature