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
Problem:
package.ts generates "alpha" builds using version 1.9999. This was
driven by the notion that we might want all "alpha" testers to be
auto-updated if we ever bump the prod major version. But in practice
there is no clear demarcation where or when that happens. And it means
we need to bump the "alpha" version whenever we bump the prod major
version.
Solution:
Use 99.x for "alpha" builds.
ref 991bfcb
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -455,10 +455,9 @@ There are several ways to make pre-production changes available on a "preview" o
455
455
- **Beta artifacts:** For a "private beta" launch, `src/dev/beta.ts` contains
456
456
logic to check a hardcoded, stable URL serving the latest `.vsix` build for
457
457
the private beta. The hardcoded URL defined in [`dev/config.ts:betaUrl`](https://github.com/aws/aws-toolkit-vscode/blob/d9c27234c0732b021d07e184a865213d6efde8ec/src/dev/config.ts#L9)
458
-
also forces the Toolkit to declare version `1.9999.0` (since "private beta"
459
-
has no semver and would conflict with the VSCode marketplace version,
460
-
causing unwanted auto-updating by VSCode). Beta builds of the Toolkit
461
-
automatically query the URL once per session per day.
458
+
also forces the Toolkit to declare version `99.0` (since "private beta" has no semver and to
459
+
avoid unwanted auto-updating from VSCode marketplace). Beta builds of the Toolkit automatically
0 commit comments