diff --git a/CHANGELOG.md b/CHANGELOG.md
index fa9864d..d0a769c 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,6 +4,7 @@ Entries in this file are in reverse chronological order.
## 2022-12-27
+* v0.17.0-1 released
* v0.16.1-1.1 published on npmjs.com
* v0.16.1-1 released
diff --git a/README-MAINTAINER.md b/README-MAINTAINER.md
index 9896c04..c20db2c 100644
--- a/README-MAINTAINER.md
+++ b/README-MAINTAINER.md
@@ -94,8 +94,8 @@ and compare the the xPack [Releases](https://github.com/xpack-dev-tools/patchelf
### Increase the version
-Determine the version (like `0.16.1`) and update the `scripts/VERSION`
-file; the format is `0.16.1-1`. The fourth number is the xPack release number
+Determine the version (like `0.17.0`) and update the `scripts/VERSION`
+file; the format is `0.17.0-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.
@@ -105,7 +105,7 @@ Check GitHub issues and pull requests:
-
-and fix them; assign them to a milestone (like `0.16.1-1`).
+and fix them; assign them to a milestone (like `0.17.0-1`).
### Check `README.md`
@@ -122,8 +122,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.16.1-1 prepared_
-- commit with a message like _prepare v0.16.1-1_
+- add a new entry like _* v0.17.0-1 prepared_
+- commit with a message like _prepare v0.17.0-1_
### Merge upstream repo
@@ -230,8 +230,8 @@ archive and its SHA signature, created in the `deploy` folder:
```console
$ ls -l ~/Work/patchelf-xpack.git/build/darwin-x64/deploy
total 224
--rw-r--r-- 1 ilg staff 109290 Oct 24 23:28 xpack-patchelf-0.16.1-1-darwin-x64.tar.gz
--rw-r--r-- 1 ilg staff 108 Oct 24 23:28 xpack-patchelf-0.16.1-1-darwin-x64.tar.gz.sha
+-rw-r--r-- 1 ilg staff 109290 Oct 24 23:28 xpack-patchelf-0.17.0-1-darwin-x64.tar.gz
+-rw-r--r-- 1 ilg staff 108 Oct 24 23:28 xpack-patchelf-0.17.0-1-darwin-x64.tar.gz.sha
```
#### Apple Silicon macOS
@@ -263,8 +263,8 @@ archive and its SHA signature, created in the `deploy` folder:
```console
$ ls -l ~/Work/patchelf-xpack.git/build/darwin-arm64/deploy
total 200
--rw-r--r-- 1 ilg staff 95328 Oct 24 23:28 xpack-patchelf-0.16.1-1-darwin-arm64.tar.gz
--rw-r--r-- 1 ilg staff 110 Oct 24 23:28 xpack-patchelf-0.16.1-1-darwin-arm64.tar.gz.sha
+-rw-r--r-- 1 ilg staff 95328 Oct 24 23:28 xpack-patchelf-0.17.0-1-darwin-arm64.tar.gz
+-rw-r--r-- 1 ilg staff 110 Oct 24 23:28 xpack-patchelf-0.17.0-1-darwin-arm64.tar.gz.sha
```
#### Intel GNU/Linux
@@ -297,8 +297,8 @@ archive and its SHA signature, created in the `deploy` folder:
```console
$ ls -l ~/Work/patchelf-xpack.git/build/linux-x64/deploy
total 904
--rw-r--r-- 1 root root 918500 Oct 24 20:29 xpack-patchelf-0.16.1-1-linux-x64.tar.gz
--rw-r--r-- 1 root root 107 Oct 24 20:29 xpack-patchelf-0.16.1-1-linux-x64.tar.gz.sha
+-rw-r--r-- 1 root root 918500 Oct 24 20:29 xpack-patchelf-0.17.0-1-linux-x64.tar.gz
+-rw-r--r-- 1 root root 107 Oct 24 20:29 xpack-patchelf-0.17.0-1-linux-x64.tar.gz.sha
```
##### Build the Windows binaries
@@ -333,8 +333,8 @@ archive and its SHA signature, created in the `deploy` folder:
```console
$ ls -l ~/Work/patchelf-xpack.git/build/linux-arm64/deploy
total 848
--rw-r--r-- 1 root root 863136 Oct 24 20:31 xpack-patchelf-0.16.1-1-linux-arm64.tar.gz
--rw-r--r-- 1 root root 109 Oct 24 20:31 xpack-patchelf-0.16.1-1-linux-arm64.tar.gz.sha
+-rw-r--r-- 1 root root 863136 Oct 24 20:31 xpack-patchelf-0.17.0-1-linux-arm64.tar.gz
+-rw-r--r-- 1 root root 109 Oct 24 20:31 xpack-patchelf-0.17.0-1-linux-arm64.tar.gz.sha
```
#### Arm GNU/Linux 32-bit
@@ -365,8 +365,8 @@ archive and its SHA signature, created in the `deploy` folder:
```console
$ ls -l ~/Work/patchelf-xpack.git/build/linux-arm/deploy
total 796
--rw-r--r-- 1 root root 807383 Oct 24 20:31 xpack-patchelf-0.16.1-1-linux-arm.tar.gz
--rw-r--r-- 1 root root 107 Oct 24 20:31 xpack-patchelf-0.16.1-1-linux-arm.tar.gz.sha
+-rw-r--r-- 1 root root 807383 Oct 24 20:31 xpack-patchelf-0.17.0-1-linux-arm.tar.gz
+-rw-r--r-- 1 root root 107 Oct 24 20:31 xpack-patchelf-0.17.0-1-linux-arm.tar.gz.sha
```
### Files cache
@@ -525,13 +525,13 @@ and check the binaries.
On GNU/Linux and macOS systems, use:
```sh
-.../xpack-patchelf-0.16.1-1/bin/patchelf --version
-patchelf 0.16.1
+.../xpack-patchelf-0.17.0-1/bin/patchelf --version
+patchelf 0.17.0
```
## Create a new GitHub pre-release draft
-- in `CHANGELOG.md`, add the release date and a message like _* v0.16.1-1 released_
+- in `CHANGELOG.md`, add the release date and a message like _* v0.17.0-1 released_
- commit with _CHANGELOG update_
- check and possibly update the `templates/body-github-release-liquid.md`
- push the `xpack-develop` branch
@@ -542,8 +542,8 @@ The workflow result and logs are available from the
The result is a
[draft pre-release](https://github.com/xpack-dev-tools/patchelf-xpack/releases/)
-tagged like **v0.16.1-1** (mind the dash in the middle!) and
-named like **xPack NixOS PatchELF v0.16.1-1** (mind the dash),
+tagged like **v0.17.0-1** (mind the dash in the middle!) and
+named like **xPack NixOS PatchELF v0.17.0-1** (mind the dash),
with all binaries attached.
- edit the draft and attach it to the `xpack-develop` branch (important!)
@@ -568,7 +568,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 NixOS PatchELF v0.16.1-1 released_
+ use a message like _xPack NixOS PatchELF v0.17.0-1 released_
- push to GitHub
- wait for the GitHub Pages build to complete
- the preview web is
@@ -610,18 +610,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.16.1-1.1 release_ (without _v_)
+ _package.json: update urls for 0.17.0-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.16.1-1.1 published on npmjs.com_
-- commit with a message like _CHANGELOG: publish npm v0.16.1-1.1_
+- update `CHANGELOG.md`, add a line like _* v0.17.0-1.1 published on npmjs.com_
+- commit with a message like _CHANGELOG: publish npm v0.17.0-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.16.1-1.1`; the first 4 numbers are the same as the
+- `npm version 0.17.0-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`
@@ -650,12 +650,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/patchelf`
-- `npm dist-tag add @xpack-dev-tools/patchelf@0.16.1-1.1 latest`
+- `npm dist-tag add @xpack-dev-tools/patchelf@0.17.0-1.1 latest`
- `npm dist-tag ls @xpack-dev-tools/patchelf`
In case the previous version is not functional and needs to be unpublished:
-- `npm unpublish @xpack-dev-tools/patchelf@0.16.1-1.1`
+- `npm unpublish @xpack-dev-tools/patchelf@0.17.0-1.1`
## Update the Web
@@ -677,7 +677,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 NixOS PatchELF v0.16.1-1 released**
+- paste the release name like **xPack NixOS PatchELF v0.17.0-1 released**
- paste the link to the Web page
[release](https://xpack.github.io/patchelf/releases/)
- click the **Tweet** button
diff --git a/README.md b/README.md
index fd24744..3d59d23 100644
--- a/README.md
+++ b/README.md
@@ -98,8 +98,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/patchelf/0.16.1-1.1/.content/
-/Users/ilg/Library/xPacks/\@xpack-dev-tools/patchelf/0.16.1-1.1/.content/
+$ tree -L 2 /Users/ilg/Library/xPacks/\@xpack-dev-tools/patchelf/0.17.0-1.1/.content/
+/Users/ilg/Library/xPacks/\@xpack-dev-tools/patchelf/0.17.0-1.1/.content/
├── README.md
├── bin
│ └── patchelf
@@ -152,16 +152,16 @@ For more details please read the
### Versioning
The version strings used by the NixOS patchelf project are three number strings
-like `0.16.1`;
+like `0.17.0`;
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.16.1-1`. When published as a npm package, the version gets
-a fifth number, like `0.16.1-1.1`.
+like `0.17.0-1`. When published as a npm package, the version gets
+a fifth number, like `0.17.0-1.1`.
Since adherence of third party packages to semver is not guaranteed,
-it is recommended to use semver expressions like `^0.16.1` and `~0.16.1`
-with caution, and prefer exact matches, like `0.16.1-1.1`.
+it is recommended to use semver expressions like `^0.17.0` and `~0.17.0`
+with caution, and prefer exact matches, like `0.17.0-1.1`.
## Maintainer info
diff --git a/scripts/VERSION b/scripts/VERSION
index 830d51e..b4c5a94 100644
--- a/scripts/VERSION
+++ b/scripts/VERSION
@@ -1 +1 @@
-0.16.1-1
+0.17.0-1