website: re-generate commons

Author: ilg-ul

website/docs/developer/_common/_platform-docker-section.mdx

@@ -47,8 +47,8 @@ or, for more verbosity, run the similar development build:
 archive and its SHA signature, created in
 the <code>build-assets/build/{props.platform}/deploy</code> folder:
 
-- <code>xpack-sed-{customField('xpackVersion')}-{props.platform}.tar.gz</code>
-- <code>xpack-sed-{customField('xpackVersion')}-{props.platform}.tar.gz.sha</code>
+- <code>xpack-sed-4.9.0-3-{props.platform}.tar.gz</code>
+- <code>xpack-sed-4.9.0-3-{props.platform}.tar.gz.sha</code>
 
 To rerun the build, invoke the **deep-clean** action and repeat from install:
 

website/docs/developer/_common/_platform-native-section.mdx

@@ -44,8 +44,8 @@ or, for more verbosity, run the similar development build:
 archive and its SHA signature, created in
 the <code>build-assets/build/{props.platform}/deploy</code> folder:
 
-- <code>xpack-sed-{customField('xpackVersion')}-{props.platform}.tar.gz</code>
-- <code>xpack-sed-{customField('xpackVersion')}-{props.platform}.tar.gz.sha</code>
+- <code>xpack-sed-4.9.0-3-{props.platform}.tar.gz</code>
+- <code>xpack-sed-4.9.0-3-{props.platform}.tar.gz.sha</code>
 
 To rerun the build, invoke the **deep-clean** action and repeat from install:
 

website/docs/install/_common/_automatic-install-quick-test.mdx

@@ -18,17 +18,17 @@ To check if the {props.longName} installed by **xpm** starts properly, use somet
 <TabItem value="macos" label="macOS">
 
 <CodeBlock language="console"> {
-`% ~/Library/xPacks/@xpack-dev-tools/${props.shortName}/${customField('xpackVersion')}.${customField('npmSubversion')}/.content/bin/${props.programName} --version
-${props.branding}${customField('upstreamVersion')}
+`% ~/Library/xPacks/@xpack-dev-tools/${props.shortName}/4.9.0-3.1/.content/bin/${props.programName} --version
+${props.branding}4.9
 `} </CodeBlock>
 
 </TabItem>
 
 <TabItem value="linux" label="GNU/Linux">
 
 <CodeBlock language="console"> {
-`$ ~/.local/xPacks/@xpack-dev-tools/${props.shortName}/${customField('xpackVersion')}.${customField('npmSubversion')}/.content/bin/${props.programName} --version
-${props.branding}${customField('upstreamVersion')}
+`$ ~/.local/xPacks/@xpack-dev-tools/${props.shortName}/4.9.0-3.1/.content/bin/${props.programName} --version
+${props.branding}4.9
 `} </CodeBlock>
 
 </TabItem>

website/docs/install/_common/_manual-install-quick-test.mdx

@@ -18,17 +18,17 @@ To check if the {props.longName} installed manually starts properly, use somethi
 <TabItem value="macos" label="macOS">
 
 <CodeBlock language="console"> {
-`% ~/Library/xPacks/${props.shortName}/xpack-${props.shortName}-${customField('xpackVersion')}/bin/${props.programName} --version
-${props.branding}${customField('upstreamVersion')}
+`% ~/Library/xPacks/${props.shortName}/xpack-${props.shortName}-4.9.0-3/bin/${props.programName} --version
+${props.branding}4.9
 `} </CodeBlock>
 
 </TabItem>
 
 <TabItem value="linux" label="GNU/Linux">
 
 <CodeBlock language="console"> {
-`$ ~/.local/xPacks/${props.shortName}/xpack-${props.shortName}-${customField('xpackVersion')}/bin/${props.programName} --version
-${props.branding}${customField('upstreamVersion')}
+`$ ~/.local/xPacks/${props.shortName}/xpack-${props.shortName}-4.9.0-3/bin/${props.programName} --version
+${props.branding}4.9
 `} </CodeBlock>
 
 </TabItem>

website/docs/install/index.mdx

@@ -246,7 +246,7 @@ The command to install the **latest** available version of **sed** is:
 To install a **specific version**, specify it explicitly:
 
 <CodeBlock language="sh"> {
-`xpm install @xpack-dev-tools/sed@${customField('releaseVersion')} --verbose
+`xpm install @xpack-dev-tools/sed@4.9.0-3.1 --verbose
 `} </CodeBlock>
 
 <Tabs groupId="operating-systems">
@@ -349,7 +349,7 @@ The result looks like this:
     "dependencies": {},
     "devDependencies": {
       "@xpack-dev-tools/sed": {
-        "specifier": "${customField('xpackVersion')}.${customField('npmSubversion')}",
+        "specifier": "4.9.0-3.1",
         "local": "link",
         "platforms": "all"
       }
@@ -405,15 +405,15 @@ the project build configurations need a PATH adjustment:
 <TabItem value="macos" label="macOS">
 
 <CodeBlock language="sh"> {
-`export PATH=$HOME/Library/xPacks/\@pack-dev-tools/sed/${customField('xpackVersion')}.${customField('npmSubversion')}/.content/bin:$PATH
+`export PATH=$HOME/Library/xPacks/\@pack-dev-tools/sed/4.9.0-3.1/.content/bin:$PATH
 `} </CodeBlock>
 
 </TabItem>
 
 <TabItem value="linux" label="GNU/Linux">
 
 <CodeBlock language="sh"> {
-`export PATH=$HOME/.local/xPacks/@xpack-dev-tools/sed/${customField('xpackVersion')}.${customField('npmSubversion')}/.content/bin:$PATH
+`export PATH=$HOME/.local/xPacks/@xpack-dev-tools/sed/4.9.0-3.1/.content/bin:$PATH
 `} </CodeBlock>
 
 </TabItem>
@@ -503,8 +503,8 @@ are packed as `.tar.gz` archives.
 Download the latest version named like:
 
 <ul>
-<li><code>xpack-sed-{customField('xpackVersion')}-darwin-x64.tar.gz</code></li>
-<li><code>xpack-sed-{customField('xpackVersion')}-darwin-arm64.tar.gz</code></li>
+<li><code>xpack-sed-4.9.0-3-darwin-x64.tar.gz</code></li>
+<li><code>xpack-sed-4.9.0-3-darwin-arm64.tar.gz</code></li>
 </ul>
 
 :::note
@@ -519,14 +519,14 @@ unpack the archive and move it to a location of your choice.
 
 The recommended location is
 the <code>~/Library/xPacks/sed</code> folder, for
-example <code>/Users/ilg/Library/xPacks/sed/xpack-sed-{customField('xpackVersion')}</code>:
+example <code>/Users/ilg/Library/xPacks/sed/xpack-sed-4.9.0-3</code>:
 
 <CodeBlock language="console"> {
 `mkdir -p ~/Library/xPacks/sed
 cd ~/Library/xPacks/sed
 
-tar xvf ~/Downloads/xpack-sed-${customField('xpackVersion')}-darwin-x64.tar.gz
-chmod -R -w xpack-sed-${customField('xpackVersion')}
+tar xvf ~/Downloads/xpack-sed-4.9.0-3-darwin-x64.tar.gz
+chmod -R -w xpack-sed-4.9.0-3
 `} </CodeBlock>
 
 </TabItem>
@@ -538,9 +538,9 @@ are packed as `.tar.gz` archives.
 Download the latest version named like:
 
 <ul>
-<li><code>xpack-sed-{customField('xpackVersion')}-linux-x64.tar.gz</code></li>
-<li><code>xpack-sed-{customField('xpackVersion')}-linux-arm64.tar.gz</code></li>
-<li><code>xpack-sed-{customField('xpackVersion')}-linux-arm.tar.gz</code></li>
+<li><code>xpack-sed-4.9.0-3-linux-x64.tar.gz</code></li>
+<li><code>xpack-sed-4.9.0-3-linux-arm64.tar.gz</code></li>
+<li><code>xpack-sed-4.9.0-3-linux-arm.tar.gz</code></li>
 </ul>
 
 :::note
@@ -555,14 +555,14 @@ unpack the archive and move it to a location of your choice.
 
 The recommended location is
 the <code>~/.local/xPacks/sed</code> folder, for
-example <code>/home/ilg/.local/xPacks/sed/xpack-sed-{customField('xpackVersion')}</code>:
+example <code>/home/ilg/.local/xPacks/sed/xpack-sed-4.9.0-3</code>:
 
 <CodeBlock language="console"> {
 `mkdir -p ~/.local/xPacks/sed
 cd ~/.local/xPacks/sed
 
-tar xvf ~/Downloads/xpack-sed-${customField('xpackVersion')}-linux-x64.tar.gz
-chmod -R -w xpack-sed-${customField('xpackVersion')}
+tar xvf ~/Downloads/xpack-sed-4.9.0-3-linux-x64.tar.gz
+chmod -R -w xpack-sed-4.9.0-3
 `} </CodeBlock>
 
 </TabItem>

website/docs/maintainer/_common/_platform-docker-build.mdx

@@ -41,8 +41,8 @@ xpm run docker-build-development --config ${props.platform} -C ~/Work/xpack-dev-
 archive and its SHA signature, created in
 the <code>build-assets/build/{props.platform}/deploy</code> folder:
 
-- <code>xpack-sed-{customField('xpackVersion')}-{props.platform}.{props.platform === 'win32-x64' ? 'zip' : 'tar.gz'}</code>
-- <code>xpack-sed-{customField('xpackVersion')}-{props.platform}.{props.platform === 'win32-x64' ? 'zip' : 'tar.gz'}.sha</code>
+- <code>xpack-sed-4.9.0-3-{props.platform}.{props.platform === 'win32-x64' ? 'zip' : 'tar.gz'}</code>
+- <code>xpack-sed-4.9.0-3-{props.platform}.{props.platform === 'win32-x64' ? 'zip' : 'tar.gz'}.sha</code>
 
 To update the build scripts and build the release binaries:
 

website/docs/maintainer/_common/_platform-native-build.mdx

@@ -40,8 +40,8 @@ xpm run build-development --config ${props.platform} -C ~/Work/xpack-dev-tools/s
 archive and its SHA signature, created in
 the <code>build-assets/build/{props.platform}/deploy</code> folder:
 
-- <code>xpack-sed-{customField('xpackVersion')}-{props.platform}.tar.gz</code>
-- <code>xpack-sed-{customField('xpackVersion')}-{props.platform}.tar.gz.sha</code>
+- <code>xpack-sed-4.9.0-3-{props.platform}.tar.gz</code>
+- <code>xpack-sed-4.9.0-3-{props.platform}.tar.gz.sha</code>
 
 To update the build scripts and build the release binaries:
 

website/docs/maintainer/index.mdx

@@ -164,10 +164,10 @@ update the dependencies in `build-assets/package.json`.
 
 ### Increase the version and update it in the top `package.json`
 
-- determine the version (like <code>{customField('xpackVersion')}</code>)
+- determine the version (like <code>4.9.0-3.1</code>)
 - update the version in top `package.json`
 - use the new version, suffixed by `.pre`,
-like <code>{customField('xpackVersion')}.{customField('npmSubversion')}.pre</code>.
+like <code>4.9.0-3.1.pre</code>.
 
 ### Update the `websiteConfig` in `website/package.json` (if necessary)
 
@@ -191,9 +191,9 @@ the **Increase the version and update VERSION** section.
 
 ### Increase the version and update VERSION
 
-Determine the version (like <code>{customField('xpackVersion')}</code>)
+Determine the version (like <code>4.9.0-3</code>)
 and update the `build-assets/scripts/VERSION` file; the format
-is <code>{customField('xpackVersion')}</code>.
+is <code>4.9.0-3</code>.
 {isXpackSubversionDouble() ?
 'The fourth & fifth numbers are the xPack release number of this version. A sixth' :
 'The fourth number is the xPack release number of this version. A fifth'} number will be added to the version in `package.json` when the package is published to the `npm` server.
@@ -212,7 +212,7 @@ Check GitHub issues and pull requests:
 - https://github.com/xpack-dev-tools/sed-xpack/issues
 - https://github.com/xpack-dev-tools/sed-xpack/pulls
 
-and fix them; assign them to a milestone (like <code>{customField('xpackVersion')}</code>).
+and fix them; assign them to a milestone (like <code>4.9.0-3</code>).
 
 ### Update `CHANGELOG.md`
 
@@ -250,8 +250,8 @@ to:
 - check if all previous fixed issues are in
 - check the latest commits `xpm run git-log`; if necessary, copy/paste lines,
   group by dates and edit them using the below regular expressions
-- add a new entry like _**\* v{customField('xpackVersion')} prepared**_
-- commit with the message _**prepare v{customField('xpackVersion')}**_
+- add a new entry like _**\* v4.9.0-3 prepared**_
+- commit with the message _**prepare v4.9.0-3**_
 
 
 ### Push the changes to the `xpack-development` branch
@@ -410,7 +410,7 @@ Copy the trees displayed at the end of the test builds and paste to
 - `website/docs/install/_folders-hierarchies-windows.mdx`
 
 If present, replace the actual version
-(like **{customField('upstreamVersion')}**) with the following expression:
+(like **4.9**) with the following expression:
 
 ```txt
 ${customField('upstreamVersion')}
@@ -714,7 +714,7 @@ xattr -cr ${HOME}/Downloads/xpack-*
 ### Create a new GitHub pre-release
 
 - in `CHANGELOG.md`, add the release date and a message
-  like _**\* v{customField('xpackVersion')} released**_
+  like _**\* v4.9.0-3 released**_
 - commit with the message _**CHANGELOG update**_
 - check and possibly update the `build-assets/templates/body-github-release-liquid.mdx`
 - push the `xpack-development` branch to GitHub
@@ -729,8 +729,8 @@ The workflow result and logs are available from the
 
 The result is a
 [draft pre-release](https://github.com/xpack-dev-tools/sed-xpack/releases)
-tagged like **v{customField('xpackVersion')}** (mind the dash in the middle!) and
-named like **xPack GNU sed v{customField('xpackVersion')}** (mind the dash),
+tagged like **v4.9.0-3** (mind the dash in the middle!) and
+named like **xPack GNU sed v4.9.0-3** (mind the dash),
 with all binaries attached.
 
 - edit the draft and be sure it is attached to the `xpack-development` branch (important!)
@@ -758,7 +758,7 @@ xpm run generate-website-blog-post -C ~/Work/xpack-dev-tools/sed-xpack.git/build
 
 - edit the front matter properties
 - select the correct summary
-- commit with the message _**website: blog post release {customField('xpackVersion')} published**_
+- commit with the message _**website: blog post release 4.9.0-3 published**_
 
 ### Update the web install page
 
@@ -790,22 +790,22 @@ xpm run update-package-binaries -C ~/Work/xpack-dev-tools/sed-xpack.git/build-as
 - compare the SHA sums with those shown by `cat *.sha`
 - check the executable names
 - commit all changes with the message
-  _**package.json: update urls for {customField('xpackVersion')}.{customField('npmSubversion')} release**_
+  _**package.json: update urls for 4.9.0-3.1 release**_
 
 ### Publish on the npmjs.com server
 
 - select the `xpack-development` branch
 - check the latest commits `xpm run git-log`
-- update `CHANGELOG.md`, add a line like _**\* v{customField('xpackVersion')} published on npmjs.com**_
-- commit with the message _**CHANGELOG: publish npm v{customField('xpackVersion')}.{customField('npmSubversion')}**_
+- update `CHANGELOG.md`, add a line like _**\* v4.9.0-3.1 published on npmjs.com**_
+- commit with the message _**CHANGELOG: publish npm v4.9.0-3.1**_
 - `npm pack` and check the content of the archive, which should list
   only the `package.json`, the `README.md`, `LICENSE` and `CHANGELOG.md`;
   possibly adjust `.npmignore`
 - configure the version; the first 4 numbers are the same as the
   GitHub release; the fifth number is the npm specific version:
 
 <CodeBlock language="sh"> {
-`npm version ${customField('xpackVersion')}.${customField('npmSubversion')}
+`npm version 4.9.0-3.1
 `} </CodeBlock>
 
 - the commits and the tag should have been pushed by the `postversion` script;
@@ -845,7 +845,7 @@ The tests results are available from the
 When the release is considered stable, promote it as `latest`:
 
 <CodeBlock language="sh"> {
-`npm dist-tag add @xpack-dev-tools/sed@${customField('xpackVersion')}.${customField('npmSubversion')} latest
+`npm dist-tag add @xpack-dev-tools/sed@4.9.0-3.1 latest
 `} </CodeBlock>
 
 Check the result:
@@ -857,7 +857,7 @@ Check the result:
 In case the release proves problematic and needs to be unpublished:
 
 <CodeBlock language="sh"> {
-`npm unpublish @xpack-dev-tools/sed@${customField('xpackVersion')}.${customField('npmSubversion')}
+`npm unpublish @xpack-dev-tools/sed@4.9.0-3.1
 `} </CodeBlock>
 
 ### Build the static website locally
@@ -947,7 +947,7 @@ Close those that were addressed.
 
 - in a separate browser windows, open [X/Twitter](https://twitter.com)
 - using the **`@xpack_project`** account
-- paste the release name like _**xPack GNU sed v{customField('xpackVersion')} released**_
+- paste the release name like _**xPack GNU sed v4.9.0-3 released**_
 - paste the link to the blog post
   [release](https://github.com/xpack-dev-tools/sed-xpack/releases)
 - click the **Tweet** button

website/docs/user/_common/_arm-toolchain-versioning.mdx

@@ -15,19 +15,19 @@ import LinksVsForwarders from '@site/src/components/LinksVsForwarders'
 The version string used by the
 upstream {props.upstreamName ? props.upstreamName : 'GNU sed'} project
 is a three number string
-like <code>{customField('releaseSemver')}</code>;
+like <code>4.9.0</code>;
 to this string the xPack distribution adds a fourth number,
 but since [SemVer](https://semver.org) allows only three numbers,
 all additional ones can
 be added only as pre-release strings, separated by a dash,
-like <code>{customField('releaseSemver')}-<b>{customField('xpackSubversion')}</b></code>. When
+like <code>4.9.0-<b>3</b></code>. When
 published as a npm package, the version gets
 a fifth number,
-like <code>{customField('xpackVersion')}.<b>{customField('npmSubversion')}</b></code>.
+like <code>4.9.0-3.<b>1</b></code>.
 
 Since adherence of third party packages to SemVer is not guaranteed,
 it is recommended to avoid referring to the xPack GNU sed dependency via
 a SemVer expressions
-like <code>^{customField('xpackVersion')}</code> or <code>~{customField('xpackVersion')}</code>, and
+like <code>^4.9.0-3</code> or <code>~4.9.0-3</code>, and
 prefer exact matches,
-like <code>{customField('xpackVersion')}.{customField('npmSubversion')}</code>.
+like <code>4.9.0-3.1</code>.