prepare v0.6.2

CHANGELOG.md

@@ -6,9 +6,19 @@ Please check
 [GitHub](https://github.com/xpack/hello-world-template-xpack/issues/)
 and close existing issues and pull requests.
 
+## 2024-11-10
+
+* 23878c0 README-liquid update
+* f594f06 package-liquid.json: bump deps
+* 46e18e0 ci.yml bump deps
+* 42f4fa4 meson-liquid.build: fix if syntax
+* 2940592 cosmetics
+* 3212f8f add "All rights reserved."
+
 ## 2023-09-26
 
-* prepare v0.6.1
+* caf6116 ci.yml: bump node
+* a0cc410 prepare v0.6.1
 * 5b76268 .gitignore update
 * 6eb05e7 package-liquid.json: bump deps
 * d1b5076 migrate to ESM

README-DEVELOPER.md

@@ -19,7 +19,7 @@ git clone https://github.com/xpack/hello-world-template-xpack.git \
 To clone the development branch:
 
 ```sh
-git clone --branch xpack-develop \
+git clone --branch xpack-development \
   https://github.com/xpack/hello-world-template-xpack.git \
   hello-world-template-xpack.git
 ```
@@ -54,12 +54,12 @@ The template receives via the `context`:
 Apart from the unused `master` branch, there are two active branches:
 
 - `xpack`, with the latest stable version
-- `xpack-develop`, with the current development version
+- `xpack-development`, with the current development version
 
-All development is done in the `xpack-develop` branch, and contributions via
+All development is done in the `xpack-development` branch, and contributions via
 Pull Requests should be directed to this branch.
 
-When new releases are published, the `xpack-develop` branch is merged
+When new releases are published, the `xpack-development` branch is merged
 into `xpack`.
 
 ## Testing

README-MAINTAINER.md

@@ -48,17 +48,17 @@ Check GitHub issues and pull requests:
 - check the latest commits `npm run git-log`
 - open the `CHANGELOG.md` file
 - check if all previous fixed issues are in
-- commit with a message like _prepare v0.6.1_
+- commit with a message like _prepare v0.6.2_
 
 ## Publish on the npmjs.com server
 
-- select the `xpack-develop` branch
+- select the `xpack-development` branch
 - commit everything
 - `npm run fix`
 - commit all changes
 - `npm run test-all`
 - check the latest commits `npm run git-log`
-- `npm run pack`; check the content of the archive, which should list
+- `npm run npm-pack`; check the content of the archive, which should list
   only the following; possibly adjust `.npmignore`
 
 ```console
@@ -118,14 +118,14 @@ workflow.
 When the package is considered stable:
 
 - with Sourcetree
-- merge `xpack-develop` into `xpack`
+- merge `xpack-development` into `xpack`
 - push to GitHub
-- select `xpack-develop`
+- select `xpack-development`
 
 ## Tag the npm package as `latest`
 
 When the release is considered stable, promote it as `latest`:
 
 - `npm dist-tag ls @xpack/hello-world-template`
-- `npm dist-tag add @xpack/[email protected].1 latest`
+- `npm dist-tag add @xpack/[email protected].2 latest`
 - `npm dist-tag ls @xpack/hello-world-template`

README.md

@@ -3,7 +3,7 @@
 [![license](https://img.shields.io/github/license/xpack/hello-world-template-xpack)](https://github.com/xpack/hello-world-template-xpack/blob/xpack/LICENSE)
 [![CI on Push](https://github.com/xpack/hello-world-template-xpack/actions/workflows/ci.yml/badge.svg)](https://github.com/xpack/hello-world-template-xpack/actions/workflows/ci.yml)
 
-# A source xPack with a template to generate Hello World projects
+# An xpm template to generate Hello World projects
 
 Generate simple _Hello World_
 projects to demonstrate the xPack Build framework.