Skip to content
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: reconfigure lerna for releases #631

Merged
merged 1 commit into from Jul 31, 2023
Merged

Conversation

boneskull
Copy link
Contributor

@boneskull boneskull commented Jul 24, 2023

This is the same as #626 but the branch is no longer in my fork.

It modifies the Lerna configuration to publish independent packages (without nx) using conventional commits. This will create/update CHANGELOGs and create GitHub Releases for each workspace upon publish.

This is what Appium does, and I believe the goals for our release process are nearly identical. Please look at the releases/tags in that repo for what you get.

To publish, just run npm run release. Note that we may want to add a preversion lifecycle script which runs a clean/build.

cc @legobeat

lerna.json Outdated Show resolved Hide resolved
@boneskull boneskull self-assigned this Jul 25, 2023
@boneskull boneskull added the chore overhead, tests, dev env, etc. label Jul 25, 2023
@boneskull boneskull changed the title [DRAFT] chore: reconfigure lerna for releases chore: reconfigure lerna for releases Jul 27, 2023
@boneskull boneskull marked this pull request as ready for review July 27, 2023 07:56
lerna.json Show resolved Hide resolved
@leotm
Copy link
Contributor

leotm commented Jul 28, 2023

Note that we may want to add a preversion lifecycle script which runs a clean/build.

captured this follow-up item here

@leotm leotm linked an issue Jul 28, 2023 that may be closed by this pull request
@leotm
Copy link
Contributor

leotm commented Jul 28, 2023

looks like this fixes couple yo issue

lerna.json Show resolved Hide resolved
This is an experimental change.

It modifies the Lerna configuration to publish independent packages (without `nx`) using conventional commits.  This will create/update CHANGELOGs and create GitHub Releases for each workspace upon publish.

This is what [Appium](https://github.com/appium/appium) does, and I believe the goals for our release process are nearly identical.  Please look at the releases/tags in that repo for what you get.

To publish, run `npm run publish`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore overhead, tests, dev env, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Changelog
2 participants