fix: ensure 256 is published with latest tag @W-19436974 (#497)

Author: nrkruk

.github/workflows/onRelease.yml

@@ -48,7 +48,7 @@ jobs:
       #ctc: true
       sign: true
       # At CLCO, the new patch branch's version will be released as 'prerelease'. After R2b, delete the logic below for 'latest' and update 'prerelease' candidate to 'latest'
-      tag: ${{ needs.getDistTag.outputs.tag || (needs.getMajorVersion.outputs.major == '3' && 'latest') ||'next' }}
+      tag: ${{ needs.getDistTag.outputs.tag || (needs.getMajorVersion.outputs.major == '3' && 'latest') || (needs.getMajorVersion.outputs.major == '4' && 'prerelease') || 'next' }}
       githubTag: ${{ github.event.release.tag_name || inputs.tag }}
 
     secrets: inherit

package.json

@@ -242,14 +242,18 @@
       },
       {
         "versionNumber": "63.0",
-        "tagName": "latest"
+        "tagName": "v2"
       },
       {
         "versionNumber": "64.0",
-        "tagName": "prerelease"
+        "tagName": "latest"
       },
       {
         "versionNumber": "65.0",
+        "tagName": "prerelease"
+      },
+      {
+        "versionNumber": "66.0",
         "tagName": "next"
       }
     ]