@anolilab/multi-semantic-release 2.0.1 → 2.0.3

package/CHANGELOG.md

@@ -1,3 +1,31 @@
+## @anolilab/multi-semantic-release [2.0.3](https://github.com/anolilab/semantic-release/compare/@anolilab/multi-semantic-release@2.0.2...@anolilab/multi-semantic-release@2.0.3) (2025-07-31)
+
+### Bug Fixes
+
+* update dependencies and improve configuration ([91c8546](https://github.com/anolilab/semantic-release/commit/91c8546aaa2f093f0f36b407b1bd4e4be34decbc))
+
+
+### Dependencies
+
+* **@anolilab/semantic-release-clean-package-json:** upgraded to 3.0.3
+* **@anolilab/semantic-release-pnpm:** upgraded to 2.0.3
+
+## @anolilab/multi-semantic-release [2.0.2](https://github.com/anolilab/semantic-release/compare/@anolilab/multi-semantic-release@2.0.1...@anolilab/multi-semantic-release@2.0.2) (2025-07-02)
+
+### Bug Fixes
+
+* add channel configuration for prereleases in multiple .releaserc.json files ([8aa95b8](https://github.com/anolilab/semantic-release/commit/8aa95b82e6b1e92dab49fe1cde6cf894eb105c0f))
+
+### Documentation
+
+* enhance README with configuration file formats and search order for multi-semantic-release ([823e9e1](https://github.com/anolilab/semantic-release/commit/823e9e16732582b07823e49d55eb789760a79d36))
+
+
+### Dependencies
+
+* **@anolilab/semantic-release-clean-package-json:** upgraded to 3.0.2
+* **@anolilab/semantic-release-pnpm:** upgraded to 2.0.2
+
 ## @anolilab/multi-semantic-release [2.0.1](https://github.com/anolilab/semantic-release/compare/@anolilab/multi-semantic-release@2.0.0...@anolilab/multi-semantic-release@2.0.1) (2025-07-02)
 
 ### Bug Fixes

package/README.md

@@ -140,6 +140,88 @@ Alternatively some options may be set via CLI flags.
 
 **Note:** CLI arguments take precedence over options configured in the configuration file.
 
+## Configuration
+
+Multi-semantic-release can be configured using a configuration file in any of the following formats:
+
+### Configuration File Formats
+
+1. **`package.json`** (under the `"multi-release"` key):
+   ```json
+   {
+     "name": "my-monorepo",
+     "version": "1.0.0",
+     "multi-release": {
+       "deps": {
+         "bump": "inherit",
+       },
+       "ignorePackages": ["packages/legacy/**"],
+       "tagFormat": "${name}@${version}"
+     }
+   }
+   ```
+
+2. **`.multi-releaserc`** (JSON format):
+   ```json
+   {
+     "deps": {
+       "bump": "inherit",
+     },
+     "ignorePackages": ["packages/legacy/**"],
+     "tagFormat": "${name}@${version}"
+   }
+   ```
+
+3. **`.multi-releaserc.json`**:
+   ```json
+   {
+     "deps": {
+       "bump": "inherit",
+     }
+   }
+   ```
+
+4. **`.multi-releaserc.js`** (CommonJS module):
+   ```javascript
+   module.exports = {
+     deps: {
+       bump: "inherit",
+     },
+     ignorePackages: ["packages/legacy/**"]
+   };
+   ```
+
+5. **`.multi-releaserc.cjs`** (CommonJS module):
+   ```javascript
+   module.exports = {
+     deps: {
+       bump: "inherit",
+       excludeDependencies: ["@visulima/packem", "my-circular-package"]
+     }
+   };
+   ```
+
+6. **`multi-release.config.js`** (ES module):
+   ```javascript
+   export default {
+     deps: {
+       bump: "inherit",
+     }
+   };
+   ```
+
+### Configuration Search
+
+Multi-semantic-release will search for configuration files in the following order:
+1. `package.json` (under `"multi-release"` property)
+2. `.multi-releaserc`
+3. `.multi-releaserc.json`
+4. `.multi-releaserc.js`
+5. `.multi-releaserc.cjs`
+6. `multi-release.config.js`
+
+The first configuration file found will be used, and the search stops there.
+
 ### Options
 
 | Option            | Type              | CLI Flag               | Description                                                                                                                                                                                                                                             |
@@ -354,7 +436,7 @@ To make the `tagFormat` option work as intended the following would need to happ
 ## Supported Node.js Versions
 
 Libraries in this ecosystem make the best effort to track
-[Node.js’ release schedule](https://nodejs.org/en/about/releases/). Here’s [a
+[Node.js' release schedule](https://nodejs.org/en/about/releases/). Here's [a
 post on why we think this is important](https://medium.com/the-node-js-collection/maintainers-should-consider-following-node-js-release-schedule-ab08ed4de71a).
 
 ## Contributing

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anolilab/multi-semantic-release",
-  "version": "2.0.1",
+  "version": "2.0.3",
   "description": "A multi semantic release tool for a monorepo.",
   "repository": {
     "type": "git",