You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The problem
Current set up is:
main
will trigger a canary publish to NPM for packages that have been created / modifiedFrom 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.
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
The text was updated successfully, but these errors were encountered: