prepare v1.0.2-1

CHANGELOG.md

@@ -4,6 +4,10 @@ Entries in this file are in reverse chronological order.
 
 ## 2023-07-28
 
+* v1.0.2-1 prepared
+* 16f7ad4 READMEs update
+* 7bee0b6 0.64.1-1.1
+* 9ad8e31 CHANGELOG: publish npm v0.64.1-1.1
 * v0.64.1-1.1 published on npmjs.com
 * 8c737ec package.json: update urls for 0.64.1-1.1 release
 * fbd0dfb re-generate workflows

README-MAINTAINER.md

@@ -129,8 +129,8 @@ previous 0.(X-1).Y is probably no longer updated and can be released.
 
 ### Increase the version
 
-Determine the version (like `0.64.1`) and update the `scripts/VERSION`
-file; the format is `0.64.1-1`. The fourth number is the xPack release number
+Determine the version (like `1.0.2`) and update the `scripts/VERSION`
+file; the format is `1.0.2-1`. The fourth number is the xPack release number
 of this version. A fifth number will be added when publishing
 the package on the `npm` server.
 
@@ -140,7 +140,7 @@ Check GitHub issues and pull requests:
 
 - <https://github.com/xpack-dev-tools/meson-build-xpack/issues/>
 
-and fix them; assign them to a milestone (like `0.64.1-1`).
+and fix them; assign them to a milestone (like `1.0.2-1`).
 
 ### Check `README.md`
 
@@ -157,8 +157,8 @@ but in the version specific release page.
 
 - open the `CHANGELOG.md` file
 - check if all previous fixed issues are in
-- add a new entry like _* v0.64.1-1 prepared_
-- commit with a message like _prepare v0.64.1-1_
+- add a new entry like _* v1.0.2-1 prepared_
+- commit with a message like _prepare v1.0.2-1_
 
 ### Update the version specific code
 
@@ -232,8 +232,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/xpack-dev-tools/meson-build-xpack.git/build/darwin-x64/deploy
 total 42608
--rw-r--r--  1 ilg  staff  20773837 Jan 28 12:35 xpack-meson-build-0.64.1-1-darwin-x64.tar.gz
--rw-r--r--  1 ilg  staff       111 Jan 28 12:35 xpack-meson-build-0.64.1-1-darwin-x64.tar.gz.sha
+-rw-r--r--  1 ilg  staff  20773837 Jan 28 12:35 xpack-meson-build-1.0.2-1-darwin-x64.tar.gz
+-rw-r--r--  1 ilg  staff       111 Jan 28 12:35 xpack-meson-build-1.0.2-1-darwin-x64.tar.gz.sha
 ```
 
 #### Apple Silicon macOS
@@ -265,8 +265,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/xpack-dev-tools/meson-build-xpack.git/build/darwin-arm64/deploy
 total 41712
--rw-r--r--  1 ilg  staff  20721998 Jan 28 12:28 xpack-meson-build-0.64.1-1-darwin-arm64.tar.gz
--rw-r--r--  1 ilg  staff       113 Jan 28 12:28 xpack-meson-build-0.64.1-1-darwin-arm64.tar.gz.sha
+-rw-r--r--  1 ilg  staff  20721998 Jan 28 12:28 xpack-meson-build-1.0.2-1-darwin-arm64.tar.gz
+-rw-r--r--  1 ilg  staff       113 Jan 28 12:28 xpack-meson-build-1.0.2-1-darwin-arm64.tar.gz.sha
 ```
 
 #### Intel GNU/Linux
@@ -300,8 +300,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/xpack-dev-tools/meson-build-xpack.git/build/linux-x64/deploy
 total 20724
--rw-r--r-- 1 ilg ilg 21216092 Jan 28 10:33 xpack-meson-build-0.64.1-1-linux-x64.tar.gz
--rw-r--r-- 1 ilg ilg      110 Jan 28 10:33 xpack-meson-build-0.64.1-1-linux-x64.tar.gz.sha
+-rw-r--r-- 1 ilg ilg 21216092 Jan 28 10:33 xpack-meson-build-1.0.2-1-linux-x64.tar.gz
+-rw-r--r-- 1 ilg ilg      110 Jan 28 10:33 xpack-meson-build-1.0.2-1-linux-x64.tar.gz.sha
 ```
 
 ##### Build the Windows binaries
@@ -327,8 +327,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/xpack-dev-tools/meson-build-xpack.git/build/win32-x64/deploy
 total 19740
--rw-r--r-- 1 ilg ilg 20207452 Jan 28 10:41 xpack-meson-build-0.64.1-1-win32-x64.zip
--rw-r--r-- 1 ilg ilg      107 Jan 28 10:41 xpack-meson-build-0.64.1-1-win32-x64.zip.sha
+-rw-r--r-- 1 ilg ilg 20207452 Jan 28 10:41 xpack-meson-build-1.0.2-1-win32-x64.zip
+-rw-r--r-- 1 ilg ilg      107 Jan 28 10:41 xpack-meson-build-1.0.2-1-win32-x64.zip.sha
 ```
 
 #### Arm GNU/Linux 64-bit
@@ -360,8 +360,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/xpack-dev-tools/meson-build-xpack.git/build/linux-arm64/deploy
 total 20444
--rw-r--r-- 1 ilg ilg 20927149 Jan 28 11:14 xpack-meson-build-0.64.1-1-linux-arm64.tar.gz
--rw-r--r-- 1 ilg ilg      112 Jan 28 11:14 xpack-meson-build-0.64.1-1-linux-arm64.tar.gz.sha
+-rw-r--r-- 1 ilg ilg 20927149 Jan 28 11:14 xpack-meson-build-1.0.2-1-linux-arm64.tar.gz
+-rw-r--r-- 1 ilg ilg      112 Jan 28 11:14 xpack-meson-build-1.0.2-1-linux-arm64.tar.gz.sha
 ```
 
 #### Arm GNU/Linux 32-bit
@@ -393,8 +393,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/xpack-dev-tools/meson-build-xpack.git/build/linux-arm/deploy
 total 19924
--rw-r--r-- 1 ilg ilg 20395664 Jan 28 11:19 xpack-meson-build-0.64.1-1-linux-arm.tar.gz
--rw-r--r-- 1 ilg ilg      110 Jan 28 11:19 xpack-meson-build-0.64.1-1-linux-arm.tar.gz.sha
+-rw-r--r-- 1 ilg ilg 20395664 Jan 28 11:19 xpack-meson-build-1.0.2-1-linux-arm.tar.gz
+-rw-r--r-- 1 ilg ilg      110 Jan 28 11:19 xpack-meson-build-1.0.2-1-linux-arm.tar.gz.sha
 ```
 
 ### Files cache
@@ -582,20 +582,20 @@ xattr -cr ${HOME}/Downloads/xpack-*
 On GNU/Linux and macOS systems, use:
 
 ```sh
-.../xpack-meson-build-0.64.1-1/bin/meson-build --version
-0.64.1
+.../xpack-meson-build-1.0.2-1/bin/meson-build --version
+1.0.2
 ```
 
 On Windows use:
 
 ```dos
-...\xpack-meson-build-0.64.1-1\bin\meson-build --version
-0.64.1
+...\xpack-meson-build-1.0.2-1\bin\meson-build --version
+1.0.2
 ```
 
 ## Create a new GitHub pre-release draft
 
-- in `CHANGELOG.md`, add the release date and a message like _* v0.64.1-1 released_
+- in `CHANGELOG.md`, add the release date and a message like _* v1.0.2-1 released_
 - commit with _CHANGELOG update_
 - check and possibly update the `templates/body-github-release-liquid.md`
 - push the `xpack-develop` branch
@@ -606,8 +606,8 @@ The workflow result and logs are available from the
 
 The result is a
 [draft pre-release](https://github.com/xpack-dev-tools/meson-build-xpack/releases/)
-tagged like **v0.64.1-1** (mind the dash in the middle!) and
-named like **xPack Meson Build v0.64.1-1** (mind the dash),
+tagged like **v1.0.2-1** (mind the dash in the middle!) and
+named like **xPack Meson Build v1.0.2-1** (mind the dash),
 with all binaries attached.
 
 - edit the draft and attach it to the `xpack-develop` branch (important!)
@@ -631,7 +631,7 @@ If any, refer to closed
 ## Update the preview Web
 
 - commit the `develop` branch of `xpack/web-jekyll` GitHub repo;
-  use a message like _xPack Meson Build v0.64.1-1 released_
+  use a message like _xPack Meson Build v1.0.2-1 released_
 - push to GitHub
 - wait for the GitHub Pages build to complete
 - the preview web is <https://xpack.github.io/web-preview/news/>
@@ -673,18 +673,18 @@ watching this project.
 - compare the SHA sums with those shown by `cat *.sha`
 - check the executable names
 - commit all changes, use a message like
-  _package.json: update urls for 0.64.1-1.1 release_ (without _v_)
+  _package.json: update urls for 1.0.2-1.1 release_ (without _v_)
 
 ## Publish on the npmjs.com server
 
 - select the `xpack-develop` branch
 - check the latest commits `npm run git-log`
-- update `CHANGELOG.md`, add a line like _* v0.64.1-1.1 published on npmjs.com_
-- commit with a message like _CHANGELOG: publish npm v0.64.1-1.1_
+- update `CHANGELOG.md`, add a line like _* v1.0.2-1.1 published on npmjs.com_
+- commit with a message like _CHANGELOG: publish npm v1.0.2-1.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`
-- `npm version 0.64.1-1.1`; the first 4 numbers are the same as the
+- `npm version 1.0.2-1.1`; the first 4 numbers are the same as the
   GitHub release; the fifth number is the npm specific version
 - the commits and the tag should have been pushed by the `postversion` script;
   if not, push them with `git push origin --tags`
@@ -713,12 +713,12 @@ The tests results are available from the
 When the release is considered stable, promote it as `latest`:
 
 - `npm dist-tag ls @xpack-dev-tools/meson-build`
-- `npm dist-tag add @xpack-dev-tools/meson-build@0.64.1-1.1 latest`
+- `npm dist-tag add @xpack-dev-tools/meson-build@1.0.2-1.1 latest`
 - `npm dist-tag ls @xpack-dev-tools/meson-build`
 
 In case the previous version is not functional and needs to be unpublished:
 
-- `npm unpublish @xpack-dev-tools/meson-build@0.64.1-1.1`
+- `npm unpublish @xpack-dev-tools/meson-build@1.0.2-1.1`
 
 ## Update the Web
 
@@ -740,7 +740,7 @@ In case the previous version is not functional and needs to be unpublished:
 
 - in a separate browser windows, open [TweetDeck](https://tweetdeck.twitter.com/)
 - using the `@xpack_project` account
-- paste the release name like **xPack Meson Build v0.64.1-1 released**
+- paste the release name like **xPack Meson Build v1.0.2-1 released**
 - paste the link to the Web page
   [release](https://xpack.github.io/meson-build/releases/)
 - click the **Tweet** button

README.md

@@ -102,8 +102,8 @@ After install, the package should create a structure like this (macOS files;
 only the first two depth levels are shown):
 
 ```console
-$ tree -L 2 /Users/ilg/Library/xPacks/\@xpack-dev-tools/meson-build/0.64.1-1.1/.content/
-/Users/ilg/Library/xPacks/\@xpack-dev-tools/meson-build/0.64.1-1.1/.content/
+$ tree -L 2 /Users/ilg/Library/xPacks/\@xpack-dev-tools/meson-build/1.0.2-1.1/.content/
+/Users/ilg/Library/xPacks/\@xpack-dev-tools/meson-build/1.0.2-1.1/.content/
 ├── README.md
 ├── bin
 │   └── meson
@@ -172,15 +172,15 @@ For more details please read the
 ### Version information
 
 The version strings used by the Meson project are three number strings
-like `0.64.1`; to this string the xPack distribution adds a four number,
+like `1.0.2`; to this string the xPack distribution adds a four number,
 but since semver allows only three numbers, all additional ones can
 be added only as pre-release strings, separated by a dash,
-like `0.64.1-1`. When published as a npm package, the version gets
-a fifth number, like `0.64.1-1.1`.
+like `1.0.2-1`. When published as a npm package, the version gets
+a fifth number, like `1.0.2-1.1`.
 
 Since adherence of third party packages to semver is not guaranteed,
-it is recommended to use semver expressions like `^0.64.1` and `~0.64.1`
-with caution, and prefer exact matches, like `0.64.1-1.1`.
+it is recommended to use semver expressions like `^1.0.2` and `~1.0.2`
+with caution, and prefer exact matches, like `1.0.2-1.1`.
 
 ## Maintainer info
 

scripts/VERSION

@@ -1 +1 @@
-0.64.1-1
+1.0.2-1