-
Notifications
You must be signed in to change notification settings - Fork 664
☂️ Published Release #18
Comments
all packages will have the same version when you publish or will be independent? |
The only package that will be published will be |
So, Do you consider implement semantic release for that? |
Looks like there's already a rome on npm. Do you know yet how you plan to handle that? |
Are you targeting a particular timeline for the release or is it just whenever things are ready? |
When things are ready. Unclear what that actually means. I can guarantee a release by the end of the month though, even if it's not ready we'll still publish to npm and figure out the remaining gaps. |
Feel like changesets would be a good option for Rome to keep track of release notes over time. |
I'm going to be making another issue to track this. |
This issue is to track the milestone Published Release.
Rome is still in development and once we are confident we have something usable and stablefor a wider audience we'll publish to npm.
The text was updated successfully, but these errors were encountered: