From f2f055afc66ddb1c94b316f44efc5a72bc5dc285 Mon Sep 17 00:00:00 2001 From: sejas Date: Mon, 15 May 2023 13:36:29 +0100 Subject: [PATCH 1/2] wp-now: add publishing instructions to wp-now --- packages/wp-now/README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/packages/wp-now/README.md b/packages/wp-now/README.md index 96b3322d317..10370c4af77 100644 --- a/packages/wp-now/README.md +++ b/packages/wp-now/README.md @@ -162,6 +162,19 @@ Some similarities between `wp-env` and `wp-now` to be aware of: - deployments are not possible with neither `wp-env`, nor `wp-now`; - possible to switch easily the PHP version +## Publishing to npm + +The `wp-now` package is part of a larger monorepo, sharing its space with other sibiling packages. To publish the `wp-now` package to npm, you must first understand the automated release process facilitated by lerna. This process includes automatically incrementing the version number, creating a new tag, and publishing all modified packages to npm simultaneously. Notably, all published packages share the same version number. + +Each package identifies a distinct organization in its package.json file. To publish the `wp-now` package, you need access to the npm organizations `@wp-playground`, `@php-wasm`, and `@wp-now`. + +To initiate the publishing process for the wp-now package, execute the following commands: + +```bash +npm login # this is required only once and it will store the credentials in ~/.npmrc file. +npm run release +``` + ## Contributing We welcome contributions from the community! Please refer to the main [README.md](../../README.md) file for instructions on how to contribute to this project. From 003ca2034527ee30562b75792683aea2e4a455e4 Mon Sep 17 00:00:00 2001 From: sejas Date: Mon, 15 May 2023 13:44:04 +0100 Subject: [PATCH 2/2] wp-now: update wording --- packages/wp-now/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/wp-now/README.md b/packages/wp-now/README.md index 10370c4af77..e71a89515f7 100644 --- a/packages/wp-now/README.md +++ b/packages/wp-now/README.md @@ -166,9 +166,9 @@ Some similarities between `wp-env` and `wp-now` to be aware of: The `wp-now` package is part of a larger monorepo, sharing its space with other sibiling packages. To publish the `wp-now` package to npm, you must first understand the automated release process facilitated by lerna. This process includes automatically incrementing the version number, creating a new tag, and publishing all modified packages to npm simultaneously. Notably, all published packages share the same version number. -Each package identifies a distinct organization in its package.json file. To publish the `wp-now` package, you need access to the npm organizations `@wp-playground`, `@php-wasm`, and `@wp-now`. +Each package identifies a distinct organization in its `package.json` file. To publish the `wp-now` package, you need access to the npm organizations `@wp-playground`, `@php-wasm`, and `@wp-now`. -To initiate the publishing process for the wp-now package, execute the following commands: +To initiate the publishing process for the all the modified packages, execute the following commands: ```bash npm login # this is required only once and it will store the credentials in ~/.npmrc file.