diff --git a/CHANGELOG.md b/CHANGELOG.md index 4f5c2a1..eb6ef5a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,7 +5,11 @@ Don't forget to close GitHub [issues](https://github.com/xpack/xpm-js/issues/). ## 2025-02-26 -* v0.20.6 prepared +* v0.20.7 prepared +* 3bf4b8b #220: implement dependency platforms check +* e2d3852 website: blog post release 0.20.6 published +* 59924fb 0.20.6 +* 661adc6 prepare v0.20.6 * bda8ba4 install.js: cosmetise message * fd23b55 install.js reindents * ca554ca #220: implement dependency platforms check diff --git a/README.md b/README.md index 4273d9f..4a9fabc 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,7 @@ For information on how to install and use this project, please refer to the ## Project source The source code of the current release is available on -[GitHub tag v0.20.6 tree](https://github.com/xpack/xpm-js/tree/v0.20.6). +[GitHub tag v0.20.7 tree](https://github.com/xpack/xpm-js/tree/v0.20.7). ## License diff --git a/package.json b/package.json index 1698c2b..adbab86 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "xpm", - "version": "0.20.6", + "version": "0.20.7-pre", "description": "The xPack project manager command line tool", "type": "module", "exports": { diff --git a/website/docs/developer/_common/_content.mdx b/website/docs/developer/_common/_content.mdx index 9b043d9..7bf39ae 100644 --- a/website/docs/developer/_common/_content.mdx +++ b/website/docs/developer/_common/_content.mdx @@ -95,7 +95,7 @@ To manually fix compliance with the style guide (where possible): { `% npm run fix -> xpm@0.20.6 fix +> xpm@0.20.7 fix > standard --fix test ... `} diff --git a/website/docs/install/_common/_install-cli.mdx b/website/docs/install/_common/_install-cli.mdx index 1897b4d..247a251 100644 --- a/website/docs/install/_common/_install-cli.mdx +++ b/website/docs/install/_common/_install-cli.mdx @@ -35,7 +35,7 @@ npm install --location=global xpm@latest To install a **specific version**, specify it explicitly: { -`npm install --location=global xpm@0.20.6 +`npm install --location=global xpm@0.20.7 `} @@ -69,7 +69,7 @@ already have this path configured and the program should start normally: { `C:\>xpm --version -0.20.6 +0.20.7 `} @@ -91,7 +91,7 @@ To test if **xpm** starts: { `% xpm --version -0.20.6 +0.20.7 `} Show macOS hidden files @@ -152,7 +152,7 @@ To test if xpm starts: `$ which xpm /home/ilg/.nvm/versions/node/${props.nodeVersion}/bin/xpm $ xpm --version -0.20.6 +0.20.7 `} @@ -176,7 +176,7 @@ benefit from it by using the `npx` command, as a trampoline to start **xpm**: { `$ npx xpm --version -0.20.6 +0.20.7 `} However, for regular usage, this method is not efficient, since diff --git a/website/docs/maintainer/_common/_content.mdx b/website/docs/maintainer/_common/_content.mdx index 55b88af..cf67da9 100644 --- a/website/docs/maintainer/_common/_content.mdx +++ b/website/docs/maintainer/_common/_content.mdx @@ -62,9 +62,9 @@ kept as a legacy CommonJS dependency. As required by npm modules, this one also uses [SemVer](https://semver.org). -- determine the next version (like 0.20.6) +- determine the next version (like 0.20.7) - update the version in the top `package.json` file -- use the new version, suffixed by `-pre`, like 0.20.6-pre. +- use the new version, suffixed by `-pre`, like 0.20.7-pre. ### Update the `websiteConfig` in top `package.json` (if necessary) @@ -96,7 +96,7 @@ Check GitHub Issues and Pull Requests: - https://github.com/xpack/xpm-js/pulls and fix them; assign them to a milestone -(like 0.20.6). +(like 0.20.7). ### Update `CHANGELOG.md` @@ -135,8 +135,8 @@ to: * ``` -- add a new entry like _**\* v0.20.6 prepared**_ -- **commit** with a message like _**prepare v0.20.6**_ +- add a new entry like _**\* v0.20.7 prepared**_ +- **commit** with a message like _**prepare v0.20.7**_ ### Prepare the release @@ -153,7 +153,7 @@ to: ### Set the new version { -`npm version 0.20.6 +`npm version 0.20.7 `} ### CI tests @@ -174,7 +174,7 @@ npm run generate-website-blog-post - edit the front matter properties - select the correct summary -- **commit** with _**website: blog post release 0.20.6 published**_ +- **commit** with _**website: blog post release 0.20.7 published**_ - **push** the `development` branch ## Publish the release to npmjs.com @@ -190,7 +190,8 @@ npm publish --access public ``` After a few moments the version will be visible at -[xpm Versions](https://www.npmjs.com/package/xpm?activeTab=versions). +npmjs.com, +the Versions tab. ### Manual install test @@ -267,7 +268,7 @@ npm dist-tag ls xpm When the release is considered stable, promote it as `latest`: { -`npm dist-tag add xpm@0.20.6 latest +`npm dist-tag add xpm@0.20.7 latest npm dist-tag ls xpm `} diff --git a/website/src/pages/index.tsx b/website/src/pages/index.tsx index a077387..4075227 100644 --- a/website/src/pages/index.tsx +++ b/website/src/pages/index.tsx @@ -38,7 +38,7 @@ function HomepageHeader() {

- npm install --location=global xpm@0.20.6 + npm install --location=global xpm@0.20.7