<commit_before># Manifest Driven release-please

release-please can be setup to use source controlled files containing releaser
specific configuration (the `release-please-config.json`) as well package
version tracking (the `.release-please-manifest.json`).


The motivation of the manifest-based releaser is support support for monorepos:

* a combined [Release PR](https://github.com/googleapis/release-please#whats-a-release-pr) will be created for all configured packages.
* release configuration for potentially hundreds of libraries is combined in two configuration files.

Note: currently only `node` and `python` release types are supported.

## Quick Start

Create a minimal `release-please-config.json`, e.g., for a single JS package:
```js
{
  "packages": {
    "path/to/pkg": {}
  }
}
```

Create an empty `.release-please-manifest.json`

Commit/push/merge these to your remote GitHub repo (using either the repo's
default branch or a test branch in which case you'll use the `--default-branch`
flag in the next step).

Run release-please:
```sh
release-please [--token=your/apikey.txt] [--default-branch=testing] manifest-pr
```<commit_msg>docs: fix typo (#920)<commit_after># Manifest Driven release-please

release-please can be setup to use source controlled files containing releaser
specific configuration (the `release-please-config.json`) as well package
version tracking (the `.release-please-manifest.json`).


The motivation of the manifest-based releaser is support for monorepos:

* a combined [Release PR](https://github.com/googleapis/release-please#whats-a-release-pr) will be created for all configured packages.
* release configuration for potentially hundreds of libraries is combined in two configuration files.

Note: currently only `node` and `python` release types are supported.

## Quick Start

Create a minimal `release-please-config.json`, e.g., for a single JS package:
```js
{
  "packages": {
    "path/to/pkg": {}
  }
}
```

Create an empty `.release-please-manifest.json`

Commit/push/merge these to your remote GitHub repo (using either the repo's
default branch or a test branch in which case you'll use the `--default-branch`
flag in the next step).

Run release-please:
```sh
release-please [--token=your/apikey.txt] [--default-branch=testing] manifest-pr
```
{'fraction_non_alphanumeric': 0.10754553339115351, 'fraction_numerical': 0.0013009540329575022, 'mean_word_length': 4.640586797066015, 'pattern_counts': {'":': 4, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '630568', 'n_tokens_mistral': 674, 'n_tokens_neox': 633, 'n_words': 254}