[FSSDK-12881] tagging improvement

Author: junaed-optimizely

.github/workflows/ghr_backfill.yml

@@ -7,8 +7,8 @@ name: Backfill GitHub Package Registry
 #
 # dist-tags: scripts/publish.sh computes the tag for each version from the
 # version string against GHR's current latest (latest only when strictly newer,
-# otherwise v<major>-latest; beta/alpha/rc for pre-releases), so latest never
-# moves backwards while backfilling historical versions.
+# otherwise v<major>-last-published; beta/alpha/rc for pre-releases), so latest
+# never moves backwards while backfilling historical versions.
 #
 # Idempotent: scripts/publish.sh skips any version already present on GHR, so
 # this can be re-run safely.

.github/workflows/release.yml

@@ -52,7 +52,7 @@ jobs:
 
       # publish.sh derives name/version from the tarball and computes the
       # dist-tag itself: `latest` only when strictly newer than the registry's
-      # current latest, otherwise v<major>-latest; beta/alpha/rc for
+      # current latest, otherwise v<major>-last-published; beta/alpha/rc for
       # pre-releases. npm publishes first; if it fails the job stops before GHR,
       # keeping the registries in sync.
       - id: release

scripts/publish.sh

@@ -34,11 +34,14 @@
 #   - Computes the dist-tag from the version:
 #       * pre-releases (beta/alpha/rc) get their own tag, never `latest`.
 #       * a stable release gets `latest` ONLY when it is strictly greater (by
-#         semver) than the registry's current `latest`. Otherwise it is tagged
-#         `v<major>-latest` (the JS SDK's long-standing per-major release line,
-#         which consumers install via @<pkg>@v<major>-latest), so `latest` never
-#         moves backwards onto an older release — e.g. 5.x shipped after 6.x, or
-#         a 6.4.1 patch shipped while latest is 6.5.0.
+#         semver) than the registry's current `latest`, so `latest` never moves
+#         backwards onto an older release — e.g. 5.x shipped after 6.x, or a
+#         6.4.1 patch shipped while latest is 6.5.0. Otherwise it is tagged
+#         `v<major>-last-published`: a per-major pointer to the most recently
+#         published version on that major line. It is named for recency (not
+#         "latest") on purpose — an out-of-order backport can leave it below the
+#         highest version in the major. Consumers install a line via
+#         @<pkg>@v<major>-last-published.
 set -euo pipefail
 
 dry_run="${DRY_RUN:-false}"
@@ -120,8 +123,8 @@ case "$version" in
       tag=latest
     else
       major=${version%%.*}
-      tag="v${major}-latest"
-      echo "Current latest is ${current_latest}; ${version} is not newer, tagging as ${tag} to preserve latest."
+      tag="v${major}-last-published"
+      echo "Current latest is ${current_latest}; ${version} is not newer, tagging as ${tag} (latest preserved)."
     fi
     ;;
 esac