-
Notifications
You must be signed in to change notification settings - Fork 20
build(next): Add release script #114
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
Merged
Merged
Conversation
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
dragidavid
commented
Jan 22, 2025
dragidavid
commented
Jan 22, 2025
Collaborator
|
Hey David thanks! #111 is merged so this PR is pointing to "main" correctly. However, because we use "squash", you may want to rebase this on top of "main" again, so the diff will be corrected. In the meantime, here's the diff for other reviewers: f3e3b79...devxp-2530-release |
04e1cc9 to
c06a240
Compare
antoniocapelo
previously approved these changes
Jan 23, 2025
Collaborator
Author
|
Going to leave this unmerged until the morning, in case we get some more eyes on it overnight. 👀 |
sandrina-p
reviewed
Jan 23, 2025
sandrina-p
reviewed
Jan 28, 2025
sandrina-p
reviewed
Jan 28, 2025
* Fix * Update jest.config.js * Update babel.config.js * chore: add default node version --------- Co-authored-by: David Dragovacz <[email protected]>
- includes separate `dev` and `beta` versions - `dev` will work the same way as the main `dev` script that we have where we append the version with the timestamp - `beta` will increment the version in the `/next/package.json` file
a572418 to
65a62c3
Compare
prevents the `dev` release when on `main` branch only allows a `beta` release when on `main` branch and local branch up to date
- this checks the version in the `next` package before merging and fails if it is anything other than `beta` - this commit should make the build fail since I'm checking if it is `beta` (for testing purposes)
sandrina-p
reviewed
Jan 31, 2025
sandrina-p
approved these changes
Jan 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To follow up on #108, #110 and #111, this PR adds the release scripts to
next. It belongs to the same internal ticket of DEVXP-2530.This PR adds the new
release_nextscript which publishes thenextpackage to NPM tagged withnextfor easy distinction.The script is based on the
devandmainrelease scripts.