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
When publishing buil-in extensions having a version that includes the 'next' word on it,
they are supposed to be marked as 'preview' which allow consumers to easily identify them before consuming them
however as it can be seen in the picture; Extensions with solid revisions have been already published with the 'preview' flag set to 'true'
There are two sides of this issue:
Correct the logic, so 'next' versions are the only ones marked as 'preview'
Investigate how to correct this in the data base.
.
The text was updated successfully, but these errors were encountered:
Hi @marcdumais-work, I think you want to use the --pre-release[1] flag for next versions. It used to be that preview[2] had the functionality of pre-release, but now these flags work the same as on the MS marketplace.
In short, preview is an indicator to a user that the extension (all versions) is not yet feature complete and may contain bugs. While pre-release lets a user regularly get the latest extension version before the official extension release.
When publishing buil-in extensions having a version that includes the 'next' word on it,
they are supposed to be marked as 'preview' which allow consumers to easily identify them before consuming them
however as it can be seen in the picture; Extensions with solid revisions have been already published with the 'preview' flag set to 'true'
There are two sides of this issue:
.
The text was updated successfully, but these errors were encountered: