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

Avoid using lerna for publishing packages. #2193

Open
tada5hi opened this issue Jan 13, 2024 · 0 comments · May be fixed by #2194
Open

Avoid using lerna for publishing packages. #2193

tada5hi opened this issue Jan 13, 2024 · 0 comments · May be fixed by #2194
Assignees
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@tada5hi
Copy link
Contributor

tada5hi commented Jan 13, 2024

Is your feature request related to a problem? Please describe.
The problem is that the docs suggest using lerna to publish already incremented package versions through semantic-release. However, lerna is a complete boilerplate for this and requires unnecessary configuration.

Describe the solution you'd like
I created a library called workspaces-publish, that facilitates the publication of packages encompassing multiple workspaces as defined in a package.json file. It determines the unpublished packages by checking each package manifest of the registry, if one already exists.
Describe alternatives you've considered
...
Additional context
...

@tada5hi tada5hi added priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. labels Jan 13, 2024
@tada5hi tada5hi linked a pull request Jan 13, 2024 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants