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

Carbon Labs: change release process to publish minor versions on merge to main #361

Open
1 task done
annawen1 opened this issue Jan 8, 2025 · 0 comments
Open
1 task done

Comments

@annawen1
Copy link
Member

annawen1 commented Jan 8, 2025

The problem

Current set up is:

  • every merge to main will trigger a canary publish to NPM for packages that have been created / modified
  • for a minor release, this needs to happen manually - triggering a GitHub Action and requires a series of steps

From past experience from the contributors we've had so far in Carbon Labs, contributors want to test out their changes right away in NPM. They usually want a more "official" version and request for a minor release which leads to overhead as minor versions have to be manually triggered.

The solution

Change the set up so that minor versions are released on every merge.

  • Remove the canary publish workflow
  • Remove the manual minor release workflow

Lerna automatically detects packages that have been modified and will only bump up the versions for those packages. This will reduce help to reduce overhead.

Examples

No response

Application/Product

No response

Business priority

None

Available extra resources

No response

Code of Conduct

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant