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
The latest stable release is 2.1.3, and this version does not have typescript. I don't see any reason why you haven't released canary.1 as stable yet. Canary.1 stays as canary for 3 years and has zero issues with it.
Maybe it's time to make it the latest stable version?
Also, some libaries like @temporalio/common start using canary version for production. It's confusing me.
The text was updated successfully, but these errors were encountered:
My team also want to add this as a production dependency, and it would be great to not have to choose between a years-old one without typescript or a canary version - esp. since we want to use ms-compatible strings as an API input so want to point at somewhere legit-seeming from our docs. It seems like all that's needed is to set version to 3.0.0 and run npm publish.
The latest stable release is 2.1.3, and this version does not have typescript. I don't see any reason why you haven't released canary.1 as stable yet. Canary.1 stays as canary for 3 years and has zero issues with it.
Maybe it's time to make it the latest stable version?
Also, some libaries like
@temporalio/common
start using canary version for production. It's confusing me.The text was updated successfully, but these errors were encountered: