prepare v1.4.2-1

xpack-dev-tools · Sep 9, 2024 · 54c92da · 54c92da
1 parent 8cc14d3
commit 54c92da
Show file tree

Hide file tree

Showing 6 changed files with 182 additions and 52 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -2,9 +2,139 @@
 
 Entries in this file are in reverse chronological order.
 
+## 2024-09-09
+
+* v1.4.2-1 prepared
+* 8cc14d3 build-assets/package.json updates
+* 799c954 re-generate workflows
+* 2264130 meson.sh: explain _MEIPASS patch
+
+## 2024-08-17
+
+* ad76681 website remove preliminary
+* b942da6 build-assets/package.json: updates
+* ea5b2a2 templates/body-blog update
+* 0c31c5f templates/body-github: update
+* 7d694b3 re-generate workflows
+
+## 2024-08-16
+
+* 1276ba3 templates/body-github: update
+
+## 2024-08-14
+
+* b9eaafa build-assets/package.json: updates
+
+## 2024-08-09
+
+* 4618c13 READMEs update
+* 31ea9fc package.json: git+https
+* 3df8514 build-assets/package.json: updates
+* b8d0764 templates/body-blog update
+
+## 2024-08-07
+
+* c6a5f6a build-assets/package.json: updates
+* a0cdb12 build-assets/package.json: updates
+* 24d7fef website: preliminary content
+* a029f03 re-generate workflows
+* 17f7540 move to build-assets
+
+## 2024-08-06
+
+* be696b3 package.json: bump deps
+
+## 2024-08-04
+
+* d4f683a package.json: bump deps
+* c0f0db6 package.json: update generate-workflows
+* 96408bd templates/jekyll update
+* 3f8eb48 meson.sh: XBB_BUILD_ROOT_PATH
+* 55bccfa READMEs update
+* 89567e6 package.json: add actions, bump deps
+
+## 2024-07-27
+
+* f88b544 package.json: add actions, bump deps
+* 58c1c64 templates/jekyll update
+
+## 2024-07-23
+
+* e4f0afa READMEs update
+* e0a76d1 .npmignore update
+* e6fcbcb re-generate scripts
+* c9e1259 body-jekyll update
+* c473373 re-generate workflows
+* 81e4159 package.json: rework generate workflows
+* 712ad40 package.json: loglevel info
+* aa85a2b package.json: bump deps
+
+## 2024-06-18
+
+* 796aa31 READMEs update
+
+## 2024-06-17
+
+* 5af6bcb package.json: rework generate workflows
+* eca4625 package.json: bump deps
+* dfa2032 application.sh: update
+
+## 2024-05-23
+
+* b515b39 package.json: clang 16.0.6-1.1
+
+## 2024-05-18
+
+* 2907bcd READMEs update
+* 13bd4fa package.json: XBB_ENVIRONMENT_SKIP_CHECKS
+
+## 2024-05-16
+
+* 6ec42dc READMEs update
+* e47fa79 versioning.sh: no need for --disable-lib-suffixes
+
+## 2024-05-14
+
+* 53c7f75 versioning.sh: ncurses with --disable-lib-suffixes
+
+## 2024-05-07
+
+* 7e0c8bc versioning.sh: remove DISABLE_WIDEC
+
+## 2024-05-03
+
+* 0db01da package.json: add bison to deps
+
+## 2024-05-02
+
+* 7193eab package.json: add m4 to deps
+* 3ae91a7 package.json: clang 17.0.6-1.1
+* 928e4e4 README update
+
+## 2024-04-22
+
+* 20f8e0e versioning.sh: avoid xz 5.6
+
+## 2024-04-03
+
+* 1aff05e meson.sh: cosmetics
+* 6b0ad93 rework meson.sh with actual python; no setuptools
+* 2a145c7 meson.sh: re-enable cleanups (config, opt)
+* 032a647 versioning.sh: cosmetics
+* 6e1514d meson.sh: separate windows code
+* 2ef1029 meson.c: consistent sys.path with default python
+
+## 2024-04-02
+
+* 24388fc add --with-meson-python
+* 32e13da prepare 1.3.2-2
+* b497277 package.json bump deps
+
 ## 2024-04-01
 
-* v1.3.2-1.1 published on npmjs.com
+* 81d01ab 1.3.2-1.1
+* 36aeba3 package.json: .pre
+* 5c788fa CHANGELOG: publish npm v1.3.2-1.1
 * a5006a3 package.json: update urls for 1.3.2-1.1 release
 * c3b7227 README update
 * ca1c4ae body-jekyll update

diff --git a/README-LONG.md b/README-LONG.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/1.3.2-2.1/.content/
-/Users/ilg/Library/xPacks/\@xpack-dev-tools/meson-build/1.3.2-2.1/.content/
+$ tree -L 2 /Users/ilg/Library/xPacks/\@xpack-dev-tools/meson-build/1.4.2-1.1/.content/
+/Users/ilg/Library/xPacks/\@xpack-dev-tools/meson-build/1.4.2-1.1/.content/
 ├── README.md
 ├── bin
 │   └── meson
@@ -169,15 +169,15 @@ For more details please read the
 ### Version information
 
 The version strings used by the Meson project are three number strings
-like `1.3.2`; to this string the xPack distribution adds a four number,
+like `1.4.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 `1.3.2-2`. When published as a npm package, the version gets
-a fifth number, like `1.3.2-2.1`.
+like `1.4.2-1`. When published as a npm package, the version gets
+a fifth number, like `1.4.2-1.1`.
 
 Since adherence of third party packages to semver is not guaranteed,
-it is recommended to use semver expressions like `^1.3.2` and `~1.3.2`
-with caution, and prefer exact matches, like `1.3.2-2.1`.
+it is recommended to use semver expressions like `^1.4.2` and `~1.4.2`
+with caution, and prefer exact matches, like `1.4.2-1.1`.
 
 ## Maintainer info
 

diff --git a/build-assets/README-MAINTAINER.md b/build-assets/README-MAINTAINER.md
@@ -112,8 +112,8 @@ previous 1.(X-1).Y is probably no longer updated and can be released.
 
 ### Increase the version
 
-Determine the version (like `1.3.2`) and update the `scripts/VERSION`
-file; the format is `1.3.2-2`. The fourth number is the xPack release number
+Determine the version (like `1.4.2`) and update the `scripts/VERSION`
+file; the format is `1.4.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.
 
@@ -123,7 +123,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 `1.3.2-2`).
+and fix them; assign them to a milestone (like `1.4.2-1`).
 
 ### Check `README.md`
 
@@ -138,14 +138,14 @@ but in the version specific release page.
 
 ### Update version in `package.json` to a pre-release
 
-Use the new version, suffixed by `pre`, like `1.3.2-2.1.pre`.
+Use the new version, suffixed by `pre`, like `1.4.2-1.1.pre`.
 
 ### Update `CHANGELOG.md`
 
 - open the `CHANGELOG.md` file
 - check if all previous fixed issues are in
-- add a new entry like _* v1.3.2-2 prepared_
-- commit with a message like _prepare v1.3.2-2_
+- add a new entry like _* v1.4.2-1 prepared_
+- commit with a message like _prepare v1.4.2-1_
 
 ### Update the version specific code
 
@@ -229,8 +229,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 48400
--rw-r--r--  1 ilg  staff  24249282 Apr  1 09:19 xpack-meson-build-1.3.2-2-darwin-x64.tar.gz
--rw-r--r--  1 ilg  staff       110 Apr  1 09:19 xpack-meson-build-1.3.2-2-darwin-x64.tar.gz.sha
+-rw-r--r--  1 ilg  staff  24249282 Apr  1 09:19 xpack-meson-build-1.4.2-1-darwin-x64.tar.gz
+-rw-r--r--  1 ilg  staff       110 Apr  1 09:19 xpack-meson-build-1.4.2-1-darwin-x64.tar.gz.sha
 ```
 
 #### Apple Silicon macOS
@@ -264,8 +264,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 48320
--rw-r--r--  1 ilg  staff  23917236 Apr  1 09:14 xpack-meson-build-1.3.2-2-darwin-arm64.tar.gz
--rw-r--r--  1 ilg  staff       112 Apr  1 09:14 xpack-meson-build-1.3.2-2-darwin-arm64.tar.gz.sha
+-rw-r--r--  1 ilg  staff  23917236 Apr  1 09:14 xpack-meson-build-1.4.2-1-darwin-arm64.tar.gz
+-rw-r--r--  1 ilg  staff       112 Apr  1 09:14 xpack-meson-build-1.4.2-1-darwin-arm64.tar.gz.sha
 ```
 
 #### Intel GNU/Linux
@@ -301,8 +301,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 23748
--rw-r--r-- 1 ilg ilg 24313653 Apr  1 06:16 xpack-meson-build-1.3.2-2-linux-x64.tar.gz
--rw-r--r-- 1 ilg ilg      109 Apr  1 06:16 xpack-meson-build-1.3.2-2-linux-x64.tar.gz.sha
+-rw-r--r-- 1 ilg ilg 24313653 Apr  1 06:16 xpack-meson-build-1.4.2-1-linux-x64.tar.gz
+-rw-r--r-- 1 ilg ilg      109 Apr  1 06:16 xpack-meson-build-1.4.2-1-linux-x64.tar.gz.sha
 ```
 
 ##### Build the Intel Windows binaries
@@ -329,8 +329,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 26132
--rw-r--r-- 1 ilg ilg 26754927 Apr  1 06:07 xpack-meson-build-1.3.2-2-win32-x64.zip
--rw-r--r-- 1 ilg ilg      106 Apr  1 06:07 xpack-meson-build-1.3.2-2-win32-x64.zip.sha
+-rw-r--r-- 1 ilg ilg 26754927 Apr  1 06:07 xpack-meson-build-1.4.2-1-win32-x64.zip
+-rw-r--r-- 1 ilg ilg      106 Apr  1 06:07 xpack-meson-build-1.4.2-1-win32-x64.zip.sha
 ```
 
 #### Arm GNU/Linux 64-bit
@@ -364,8 +364,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 23500
--rw-r--r-- 1 ilg ilg 24057814 Apr  1 07:16 xpack-meson-build-1.3.2-2-linux-arm64.tar.gz
--rw-r--r-- 1 ilg ilg      111 Apr  1 07:16 xpack-meson-build-1.3.2-2-linux-arm64.tar.gz.sha
+-rw-r--r-- 1 ilg ilg 24057814 Apr  1 07:16 xpack-meson-build-1.4.2-1-linux-arm64.tar.gz
+-rw-r--r-- 1 ilg ilg      111 Apr  1 07:16 xpack-meson-build-1.4.2-1-linux-arm64.tar.gz.sha
 ```
 
 #### Arm GNU/Linux 32-bit
@@ -399,8 +399,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 22848
--rw-r--r-- 1 ilg ilg 23389476 Apr  1 07:18 xpack-meson-build-1.3.2-2-linux-arm.tar.gz
--rw-r--r-- 1 ilg ilg      109 Apr  1 07:18 xpack-meson-build-1.3.2-2-linux-arm.tar.gz.sha
+-rw-r--r-- 1 ilg ilg 23389476 Apr  1 07:18 xpack-meson-build-1.4.2-1-linux-arm.tar.gz
+-rw-r--r-- 1 ilg ilg      109 Apr  1 07:18 xpack-meson-build-1.4.2-1-linux-arm.tar.gz.sha
 ```
 
 ### Update README-MAINTAINER listing output
@@ -627,20 +627,20 @@ xattr -cr ${HOME}/Downloads/xpack-*
 On GNU/Linux and macOS systems, use:
 
 ```sh
-.../xpack-meson-build-1.3.2-2/bin/meson --version
-1.3.2
+.../xpack-meson-build-1.4.2-1/bin/meson --version
+1.4.2
 ```
 
 On Windows use:
 
 ```dos
-...\xpack-meson-build-1.3.2-2\bin\meson --version
-1.3.2
+...\xpack-meson-build-1.4.2-1\bin\meson --version
+1.4.2
 ```
 
 ## Create a new GitHub pre-release draft
 
-- in `CHANGELOG.md`, add the release date and a message like _* v1.3.2-2 released_
+- in `CHANGELOG.md`, add the release date and a message like _* v1.4.2-1 released_
 - commit with _CHANGELOG update_
 - check and possibly update the `templates/body-github-release-liquid.md`
 - push the `xpack-develop` branch
@@ -651,8 +651,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 **v1.3.2-2** (mind the dash in the middle!) and
-named like **xPack Meson Build v1.3.2-2** (mind the dash),
+tagged like **v1.4.2-1** (mind the dash in the middle!) and
+named like **xPack Meson Build v1.4.2-1** (mind the dash),
 with all binaries attached.
 
 - edit the draft and attach it to the `xpack-develop` branch (important!)
@@ -676,7 +676,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 v1.3.2-2 released_
+  use a message like _xPack Meson Build v1.4.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/>
@@ -717,18 +717,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 1.3.2-2.1 release_ (without _v_)
+  _package.json: update urls for 1.4.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 _* v1.3.2-2.1 published on npmjs.com_
-- commit with a message like _CHANGELOG: publish npm v1.3.2-2.1_
+- update `CHANGELOG.md`, add a line like _* v1.4.2-1.1 published on npmjs.com_
+- commit with a message like _CHANGELOG: publish npm v1.4.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 1.3.2-2.1`; the first 4 numbers are the same as the
+- `npm version 1.4.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`
@@ -757,12 +757,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@1.3.2-2.1 latest`
+- `npm dist-tag add @xpack-dev-tools/meson-build@1.4.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@1.3.2-2.1`
+- `npm unpublish @xpack-dev-tools/meson-build@1.4.2-1.1`
 
 ## Update the Web
 
@@ -784,7 +784,7 @@ In case the previous version is not functional and needs to be unpublished:
 
 - in a separate browser windows, open [X/Twitter](https://twitter.com)
 - using the `@xpack_project` account
-- paste the release name like **xPack Meson Build v1.3.2-2 released**
+- paste the release name like **xPack Meson Build v1.4.2-1 released**
 - paste the link to the Web page
   [release](https://xpack.github.io/meson-build/releases/)
 - click the **Tweet** button

diff --git a/build-assets/scripts/VERSION b/build-assets/scripts/VERSION
@@ -1 +1 @@
-1.3.2-2
+1.4.2-1