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
We started out the new package using the version 6 to ease conversations and discussions around the different versions rather than speaking in terms of different packages themselves and thus started publishing nightly builds to npm using v6-alpha versions. We have used the term v6 in labels, issues and PRs
At some point a few months ago when we were ready to do our first beta for the new package, we chose to start from version 1 because it was a brand new package. This has caused quite some confusion along the lines. After another round of discussions, we have decided to continue with v6.
This issue is to ensure
We have nightly builds published to npm using v6 for @autorest/typescript
The next preview for @autorest/typescript package uses v6
Actually, Ignore my previous comment. The github release also will happen and the tag will be set correctly. So, the daily/nightly build will run everyday in the morning (Except weekdays) at 9:30 AM. The alpha version will be released to npm and github. Eg:
This repository house 2 packages that work with
autorest
in different branches, both generate TS SDKs for given swagger file inputv4x
andv5x
branches house v4 and v5 of the @microsoft.azure/autorest.typescript packagemain
branch houses the new package @autorest/typescriptWe started out the new package using the version 6 to ease conversations and discussions around the different versions rather than speaking in terms of different packages themselves and thus started publishing nightly builds to npm using v6-alpha versions. We have used the term v6 in labels, issues and PRs
At some point a few months ago when we were ready to do our first beta for the new package, we chose to start from version 1 because it was a brand new package. This has caused quite some confusion along the lines. After another round of discussions, we have decided to continue with v6.
This issue is to ensure
@autorest/typescript
@autorest/typescript
package uses v6The text was updated successfully, but these errors were encountered: