@anolilab/multi-semantic-release 1.1.6 → 1.1.8

package/CHANGELOG.md

@@ -1,3 +1,18 @@
+## @anolilab/multi-semantic-release [1.1.8](https://github.com/anolilab/semantic-release/compare/@anolilab/multi-semantic-release@1.1.7...@anolilab/multi-semantic-release@1.1.8) (2025-01-16)
+
+
+### Dependencies
+
+* **@anolilab/semantic-release-clean-package-json:** upgraded to 1.0.0
+* **@anolilab/semantic-release-pnpm:** upgraded to 1.1.8
+
+## @anolilab/multi-semantic-release [1.1.7](https://github.com/anolilab/semantic-release/compare/@anolilab/multi-semantic-release@1.1.6...@anolilab/multi-semantic-release@1.1.7) (2025-01-14)
+
+
+### Dependencies
+
+* **@anolilab/semantic-release-pnpm:** upgraded to 1.1.7
+
 ## @anolilab/multi-semantic-release [1.1.6](https://github.com/anolilab/semantic-release/compare/@anolilab/multi-semantic-release@1.1.5...@anolilab/multi-semantic-release@1.1.6) (2024-12-15)
 
 ### Bug Fixes

package/README.md

@@ -38,12 +38,12 @@ written into `package.json` at release time. This means there's no need to hard-
 
 ### Key features
 
--   CLI & JS API
--   Automated & configurable cross-pkg version bumping
--   Provides alpha & beta-branched release flow
--   Supports npm (v7+), yarn, pnpm, bolt-based monorepos
--   Optional packages ignoring
--   Linux/MacOs/Windows support
+- CLI & JS API
+- Automated & configurable cross-pkg version bumping
+- Provides alpha & beta-branched release flow
+- Supports npm (v7+), yarn, pnpm, bolt-based monorepos
+- Optional packages ignoring
+- Linux/MacOs/Windows support
 
 ## Install
 
@@ -67,8 +67,8 @@ multi-semantic-release
 
 ## Requirements
 
--   Node.js >= 20.6.1
--   [git-notes enabled](https://github.com/semantic-release/semantic-release/blob/2e4b901c4f412980a425469fae49cfaef500d47a/docs/support/troubleshooting.md#release-not-found-release-branch-after-git-push---force)
+- Node.js >= 20.6.1
+- [git-notes enabled](https://github.com/semantic-release/semantic-release/blob/2e4b901c4f412980a425469fae49cfaef500d47a/docs/support/troubleshooting.md#release-not-found-release-branch-after-git-push---force)
 
 ### yarn / npm (v7+)
 
@@ -138,9 +138,9 @@ For example, let's say your project has 4 packages (i.e. a, b, c and d) and you
 
 multi-semantic-release can be configured a number of ways:
 
--   A `.multi-releaserc` file, written in YAML or JSON, with optional extensions: `.yaml`/ `.yml`/ `.json`/ `.js`
--   A `multi-release.config.js` file that exports an object
--   A `multi-release` key in the workspace root package.json
+- A `.multi-releaserc` file, written in YAML or JSON, with optional extensions: `.yaml`/ `.yml`/ `.json`/ `.js`
+- A `multi-release.config.js` file that exports an object
+- A `multi-release` key in the workspace root package.json
 
 Alternatively some options may be set via CLI flags.
 
@@ -173,7 +173,7 @@ Alternatively some options may be set via CLI flags.
 
 ### Examples
 
--   Via multi-release key in the project's package.json file:
+- Via multi-release key in the project's package.json file:
 
 ```json
 {
@@ -186,7 +186,7 @@ Alternatively some options may be set via CLI flags.
 }
 ```
 
--   Via `.multi-releaserc` file:
+- Via `.multi-releaserc` file:
 
 ```json
 {
@@ -197,7 +197,7 @@ Alternatively some options may be set via CLI flags.
 }
 ```
 
--   Via CLI:
+- Via CLI:
 
 ```sh
 $ multi-semantic-release --ignore-packages=packages/a/**,packages/b/** --deps.bump=inherit
@@ -249,11 +249,11 @@ You can also combine the CLI ignore options with the `!` operator at each packag
 
 We use this tool to release our JS platform code inhouse (GitHub Enterprise + JB TeamCity) and for our OSS (GitHub + Travis CI). Guaranteed working configurations available in projects.
 
--   [anolilab/multi-semantic-release](https://github.com/anolilab/semantic-release)
--   [visulima/visulima](https://github.com/visulima/visulima)
--   [qiwi/substrate](https://github.com/qiwi/substrate)
--   [qiwi/json-rpc](https://github.com/qiwi/json-rpc)
--   [qiwi/lint-config-qiwi](https://github.com/qiwi/lint-config-qiwi)
+- [anolilab/multi-semantic-release](https://github.com/anolilab/semantic-release)
+- [visulima/visulima](https://github.com/visulima/visulima)
+- [qiwi/substrate](https://github.com/qiwi/substrate)
+- [qiwi/json-rpc](https://github.com/qiwi/json-rpc)
+- [qiwi/lint-config-qiwi](https://github.com/qiwi/lint-config-qiwi)
 
 ## Troubleshooting
 
@@ -274,8 +274,8 @@ The npm token (https://github.com/semantic-release/npm/blob/master/README.md#npm
 
 Do not rush to change your token. _Perhaps_ this is related to [`npm whoami` request](https://github.com/semantic-release/npm/blob/master/lib/verify-auth.js#L21) throttling on your registry (just a hypothesis: https://github.com/semantic-release/npm/pull/416). At this point you can:
 
--   Rerun your build as many times as necessary. You may get lucky in a new attempt.
--   Use [semrel-extra/npm plugin](https://github.com/semrel-extra/npm) for npm publishing (recommended).
+- Rerun your build as many times as necessary. You may get lucky in a new attempt.
+- Use [semrel-extra/npm plugin](https://github.com/semrel-extra/npm) for npm publishing (recommended).
 
 ### git: connection reset by peer
 
@@ -288,10 +288,10 @@ Anyway we've added a special [`--sequental-init`](#cli) flag to queue up these c
 
 Automatically finds packages as long as workspaces are configured as-per the workspace-feature of one of the support package managers.
 
--   [Yarn workspaces](https://yarnpkg.com/lang/en/docs/workspaces/).
--   [Npm workspaces (Version 7.x)](https://docs.npmjs.com/cli/v7/using-npm/workspaces)
--   [pnpm workspace](https://pnpm.js.org/workspaces/)
--   [bolt workspaces](https://github.com/boltpkg/bolt#configuration)
+- [Yarn workspaces](https://yarnpkg.com/lang/en/docs/workspaces/).
+- [Npm workspaces (Version 7.x)](https://docs.npmjs.com/cli/v7/using-npm/workspaces)
+- [pnpm workspace](https://pnpm.js.org/workspaces/)
+- [bolt workspaces](https://github.com/boltpkg/bolt#configuration)
 
 I'm aware Lerna is the best-known tool right now, but in future it seems clear it will be replaced by functionality in Yarn and NPM directly. If you use Yarn workspaces today (January 2019), then publishing is the only remaining feature Lerna is _really_ required for (though it'd be lovely if Yarn added parallel script execution). Thus using multi-semantic-release means you can probably remove Lerna entirely from your project.
 
@@ -299,17 +299,17 @@ I'm aware Lerna is the best-known tool right now, but in future it seems clear i
 
 Other packages that enable semantic-release for monorepos work by iterating into each package and running the `semantic-release` command. This is conceptually simple but unfortunately not viable because:
 
--   If a package is published that depends on minor changes that have been made in a sibling package it could cause extremely subtle errors (the worst kind!) — if the project follows semver religiously this should never happen, but it's better to eliminate the _potential_ for errors
--   Dependency version numbers need to reflect the _next_ release at time of publishing, so a package needs to know the state of _all other packages_ before it can publish correctly — this central state needs to be coordinated by something
+- If a package is published that depends on minor changes that have been made in a sibling package it could cause extremely subtle errors (the worst kind!) — if the project follows semver religiously this should never happen, but it's better to eliminate the _potential_ for errors
+- Dependency version numbers need to reflect the _next_ release at time of publishing, so a package needs to know the state of _all other packages_ before it can publish correctly — this central state needs to be coordinated by something
 
 ### Local dependencies and version numbers
 
 A key requirement is handling local dep version numbers elegantly. multi-semantic-release does the following:
 
--   The next version number of all packages is established first
--   If a release has not changed but has local deps that _have_ changed... do a `patch` bump on that package too
--   Before packages are released (in semantic-release's prepare step), the correct current/next version number of _all_ local dependencies is written into the `package.json` file (overwriting any existing value)
--   This ensures the package at the time of publishing will be atomically correct with all other packages in the monorepo.
+- The next version number of all packages is established first
+- If a release has not changed but has local deps that _have_ changed... do a `patch` bump on that package too
+- Before packages are released (in semantic-release's prepare step), the correct current/next version number of _all_ local dependencies is written into the `package.json` file (overwriting any existing value)
+- This ensures the package at the time of publishing will be atomically correct with all other packages in the monorepo.
 
 The above means that, possibly, if someone upgrades dependencies and pulls down a package from NPM _during the multirelease_ (before all its deps have been published at their next versions), then their `npm install` will fail (it will work if they try again in a few minutes). On balance I thought it was more important to be atomically correct (this situation should be fairly rare assuming projects commit their lockfiles).
 
@@ -323,22 +323,22 @@ The plugin starts all release at once, then pauses them (using Promises) at vari
 
 The inline plugin does the following:
 
--   **verifyConditions:** _not used_
--   **analyzeCommits:**
-    -   Replaces `context.commits` with a list of commits filtered to the folder only
-    -   Calls `plugins.analyzeCommits()` to get the next release type (e.g. from @semantic-release/commit-analyzer)
-    -   Waits for _all_ packages to catch up to this point.
-    -   For packages that haven't bumped, checks if it has local deps (or deps of deps) that have bumped and returns `patch` if that's true
--   **verifyRelease:** _not used_
--   **generateNotes:**
-    -   Calls `plugins.generateNotes()` to get the notes (e.g. from @semantic-release/release-notes-generator)
-    -   Appends a section listing any local deps bumps (e.g. "my-pkg-2: upgraded to 1.2.1")
--   **prepare:**
-    -   Writes in the correct version for local deps in `dependencies`, `devDependencies`, `peerDependencies` in `package.json`
-    -   Serialize the releases so they happen one-at-a-time (because semantic-release calls `git push` asynchronously, multiple releases at once fail because Git refs aren't locked — semantic-release should use `execa.sync()` so Git operations are atomic)
--   **publish:** _not used_
--   **success:** _not used_
--   **fail:** _not used_
+- **verifyConditions:** _not used_
+- **analyzeCommits:**
+    - Replaces `context.commits` with a list of commits filtered to the folder only
+    - Calls `plugins.analyzeCommits()` to get the next release type (e.g. from @semantic-release/commit-analyzer)
+    - Waits for _all_ packages to catch up to this point.
+    - For packages that haven't bumped, checks if it has local deps (or deps of deps) that have bumped and returns `patch` if that's true
+- **verifyRelease:** _not used_
+- **generateNotes:**
+    - Calls `plugins.generateNotes()` to get the notes (e.g. from @semantic-release/release-notes-generator)
+    - Appends a section listing any local deps bumps (e.g. "my-pkg-2: upgraded to 1.2.1")
+- **prepare:**
+    - Writes in the correct version for local deps in `dependencies`, `devDependencies`, `peerDependencies` in `package.json`
+    - Serialize the releases so they happen one-at-a-time (because semantic-release calls `git push` asynchronously, multiple releases at once fail because Git refs aren't locked — semantic-release should use `execa.sync()` so Git operations are atomic)
+- **publish:** _not used_
+- **success:** _not used_
+- **fail:** _not used_
 
 ### Jank
 
@@ -346,28 +346,28 @@ The integration with semantic release is pretty janky — this is a quick summar
 
 1. Had to filter `context.commits` object before it was used by `@semantic-release/commit-analyzer` (so it only lists commits for the corresponding directory).
 
--   The actual Git filtering is easy peasy: see [getCommitsFiltered.js](https://github.com/dhoulb/multi-semantic-release/blob/master/lib/getCommitsFiltered.js)
--   But overriding `context.commits` was very difficult! I did it eventually creating an _inline plugin_ and passing it into `semanticRelease()` via `options.plugins`
--   The inline plugin proxies between semantic release and other configured plugins. It does what it needs to then calls e.g. `plugins.analyzeCommits()` with an overridden `context.commits` — see [createInlinePluginCreator.js](https://github.com/dhoulb/multi-semantic-release/blob/master/lib/createInlinePluginCreator.js)
--   I think this is messy — inline plugins aren't even documented :(
+- The actual Git filtering is easy peasy: see [getCommitsFiltered.js](https://github.com/dhoulb/multi-semantic-release/blob/master/lib/getCommitsFiltered.js)
+- But overriding `context.commits` was very difficult! I did it eventually creating an _inline plugin_ and passing it into `semanticRelease()` via `options.plugins`
+- The inline plugin proxies between semantic release and other configured plugins. It does what it needs to then calls e.g. `plugins.analyzeCommits()` with an overridden `context.commits` — see [createInlinePluginCreator.js](https://github.com/dhoulb/multi-semantic-release/blob/master/lib/createInlinePluginCreator.js)
+- I think this is messy — inline plugins aren't even documented :(
 
 2. Need to run the analyze commit step on _all_ plugins before any proceed to the publish step
 
--   The inline plugin returns a Promise for every package then waits for all packages to analyze their commits before resolving them one at a time
--   If packages have local deps (e.g. `dependencies` in package.json points to an internal package) this step also does a `patch` bump if any of them did a bump.
--   This has to work recursively! See [hasChangedDeep.js](https://github.com/dhoulb/multi-semantic-release/blob/master/lib/hasChangedDeep.js)
+- The inline plugin returns a Promise for every package then waits for all packages to analyze their commits before resolving them one at a time
+- If packages have local deps (e.g. `dependencies` in package.json points to an internal package) this step also does a `patch` bump if any of them did a bump.
+- This has to work recursively! See [hasChangedDeep.js](https://github.com/dhoulb/multi-semantic-release/blob/master/lib/hasChangedDeep.js)
 
 3. The configuration can be layered (i.e. global `.releaserc` and then per-directory overrides for individual packages).
 
--   Had to duplicate the internal cosmiconfig setup from semantic release to get this working :(
+- Had to duplicate the internal cosmiconfig setup from semantic release to get this working :(
 
 4. I found Git getting itself into weird states because e.g. `git tag` is done asynchronously
 
--   To get around this I had to stagger package publishing so they were done one at a time (which slows things down)
--   I think calls to `execa()` in semantic release should be replaced with `execa.sync()` to ensure Git's internal state is atomic.
--   Fortunately, another workaround has been implemented. `Synchronizer` is the neat part. It is critical to make the tag and commit publishing phases strictly sequential. [Event emitter allows](https://github.com/dhoulb/multi-semantic-release/blob/master/lib/getSynchronizer.js):
-    -   To synchronize release stages for all packages.
-    -   To ensure the completeness of checks and the sufficiency of conditions for a conflict-free process.
+- To get around this I had to stagger package publishing so they were done one at a time (which slows things down)
+- I think calls to `execa()` in semantic release should be replaced with `execa.sync()` to ensure Git's internal state is atomic.
+- Fortunately, another workaround has been implemented. `Synchronizer` is the neat part. It is critical to make the tag and commit publishing phases strictly sequential. [Event emitter allows](https://github.com/dhoulb/multi-semantic-release/blob/master/lib/getSynchronizer.js):
+    - To synchronize release stages for all packages.
+    - To ensure the completeness of checks and the sufficiency of conditions for a conflict-free process.
 
 ### Git tags
 
@@ -377,9 +377,9 @@ I can personally see the potential for this option in coordinating a semantic-re
 
 To make the `tagFormat` option work as intended the following would need to happen:
 
--   semantic-release needs to check if a given tag already exists at a given commit, and not create it / push it if that's true
--   Release notes for multiple package releases need to be merged BUT the Github release only done once (by having the notes merged at the semantic-release level but only published once, or having the Github plugin merge them)
--   Make it clear in documentation that the default tag `v1.0.0` will have the same effect as Lerna's fixed mode (all changed monorepo packages released at same time)
+- semantic-release needs to check if a given tag already exists at a given commit, and not create it / push it if that's true
+- Release notes for multiple package releases need to be merged BUT the Github release only done once (by having the notes merged at the semantic-release level but only published once, or having the Github plugin merge them)
+- Make it clear in documentation that the default tag `v1.0.0` will have the same effect as Lerna's fixed mode (all changed monorepo packages released at same time)
 
 ## Supported Node.js Versions
 
@@ -395,12 +395,12 @@ If you would like to help take a look at the [list of issues](https://github.com
 
 ## Credits
 
--   [Daniel Bannert](https://github.com/prisis)
--   [All Contributors](https://github.com/anolilab/semantic-release/graphs/contributors)
-    -   [hanseltime](https://github.com/hanseltime) -> https://github.com/qiwi/multi-semantic-release/pull/96
-    -   [lyh543](https://github.com/lyh543) -> https://github.com/dhoulb/multi-semantic-release/issues/111
--   [dhoub/multi-semantic-release](https://github.com/dhoulb/multi-semantic-release)
--   [qiwi/multi-semantic-release](https://github.com/qiwi/multi-semantic-release)
+- [Daniel Bannert](https://github.com/prisis)
+- [All Contributors](https://github.com/anolilab/semantic-release/graphs/contributors)
+    - [hanseltime](https://github.com/hanseltime) -> https://github.com/qiwi/multi-semantic-release/pull/96
+    - [lyh543](https://github.com/lyh543) -> https://github.com/dhoulb/multi-semantic-release/issues/111
+- [dhoub/multi-semantic-release](https://github.com/dhoulb/multi-semantic-release)
+- [qiwi/multi-semantic-release](https://github.com/qiwi/multi-semantic-release)
 
 ## License
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anolilab/multi-semantic-release",
-  "version": "1.1.6",
+  "version": "1.1.8",
   "description": "A multi semantic release tool for a monorepo.",
   "repository": {
     "type": "git",
@@ -9,12 +9,6 @@
   },
   "license": "0BSD",
   "author": "Dave Houlbrooke <dave@shax.com>",
-  "maintainers": [
-    {
-      "name": "Daniel Bannert",
-      "email": "d.bannert@anolilab.de"
-    }
-  ],
   "type": "module",
   "exports": {
     ".": "./lib/multi-semantic-release.js",
@@ -46,44 +40,6 @@
     "stream-buffers": "^3.0.3",
     "yargs": "^17.7.2"
   },
-  "devDependencies": {
-    "@anolilab/eslint-config": "^15.0.3",
-    "@anolilab/prettier-config": "^5.0.14",
-    "@anolilab/semantic-release-pnpm": "1.1.6",
-    "@babel/core": "^7.26.0",
-    "@rushstack/eslint-plugin-security": "^0.8.3",
-    "@secretlint/secretlint-rule-preset-recommend": "^9.0.0",
-    "@semantic-release/changelog": "^6.0.3",
-    "@semantic-release/commit-analyzer": "13.0.0",
-    "@semantic-release/exec": "^6.0.3",
-    "@semantic-release/git": "^10.0.1",
-    "@semantic-release/github": "^11.0.1",
-    "@semantic-release/release-notes-generator": "14.0.1",
-    "@types/node": "18.19.68",
-    "@vitest/coverage-v8": "^2.1.8",
-    "@vitest/ui": "^2.1.8",
-    "conventional-changelog-conventionalcommits": "8.0.0",
-    "cross-env": "^7.0.3",
-    "eslint": "^8.57.1",
-    "eslint-plugin-deprecation": "^3.0.0",
-    "eslint-plugin-etc": "^2.0.3",
-    "eslint-plugin-import": "npm:eslint-plugin-i@^2.29.1",
-    "eslint-plugin-mdx": "^3.1.5",
-    "eslint-plugin-n": "^17.15.0",
-    "eslint-plugin-vitest": "^0.4.1",
-    "eslint-plugin-vitest-globals": "^1.5.0",
-    "eslint-plugin-you-dont-need-lodash-underscore": "^6.14.0",
-    "file-url": "^4.0.0",
-    "prettier": "^3.4.2",
-    "publint": "^0.2.12",
-    "rimraf": "^6.0.1",
-    "secretlint": "9.0.0",
-    "semantic-release": "^24.2.0",
-    "sort-package-json": "^2.12.0",
-    "tempy": "^3.1.0",
-    "typescript": "^5.7.2",
-    "vitest": "^2.1.8"
-  },
   "peerDependencies": {
     "semantic-release": "^20.0 || ^21.0 || >=22.0.3"
   },
@@ -98,34 +54,5 @@
   "publishConfig": {
     "access": "public",
     "provenance": true
-  },
-  "anolilab": {
-    "eslint-config": {
-      "plugin": {},
-      "warn_on_unsupported_typescript_version": false,
-      "info_on_disabling_jsx_react_rule": false,
-      "info_on_disabling_prettier_conflict_rule": false,
-      "info_on_disabling_jsonc_sort_keys_rule": false,
-      "import_ignore_exports": [
-        "**/*.cjs",
-        "**/__tests__/**/*.js"
-      ]
-    }
-  },
-  "scripts": {
-    "build": "echo 'There is no need for build' && exit 0",
-    "build:prod": "echo 'There is no need for build' && exit 0",
-    "clean": "rimraf node_modules dist .eslintcache",
-    "dev": "echo 'There is no need for dev' && exit 0",
-    "lint:eslint": "eslint . --ext js,cjs,mjs,jsx,ts,tsx,json,yaml,yml,md,mdx --max-warnings=0 --config .eslintrc.cjs",
-    "lint:eslint:fix": "eslint . --ext js,cjs,mjs,jsx,ts,tsx,json,yaml,yml,md,mdx --max-warnings=0 --config .eslintrc.cjs --fix",
-    "lint:packagejson": "publint --strict",
-    "lint:prettier": "prettier --config=.prettierrc.cjs --check .",
-    "lint:prettier:fix": "prettier --config=.prettierrc.cjs --write .",
-    "lint:types": "tsc --noEmit || exit 0",
-    "test": "vitest run",
-    "test:coverage": "vitest run --coverage",
-    "test:ui": "vitest --ui --coverage.enabled=true",
-    "test:watch": "vitest"
   }
 }