keepchanges 1.0.2 → 1.0.3

package/README.md

@@ -1,6 +1,8 @@
 # keepchanges
 
-Generate and maintain `CHANGELOG.md` from Conventional Commits.
+A release CLI for Conventional Commits. Generate and maintain a changelog, optionally bump
+the project version, create a release commit and Git tag, publish a GitHub or Gitea Release,
+and upload GitHub Release assets.
 
 Inspired by [changelogithub](https://github.com/antfu-collective/changelogithub).
 
@@ -8,17 +10,20 @@ Inspired by [changelogithub](https://github.com/antfu-collective/changelogithub)
 
 ## Features
 
-- Generates release notes from Conventional Commits between the latest Git tag and `HEAD`
-- Reads the complete Git history for a first release
-- Inserts a new release before existing content in `CHANGELOG.md`
-- Updates `package.json#version` for npm projects
-- Adds repository commit links, comparison links, authors, and co-authors
-- Can commit, tag, push, and publish a GitHub or Gitea Release
-- Provides a manual release URL when no GitHub/Gitea token is available
+- Generates release notes from Conventional Commits between Git tags
+- Inserts new releases into an existing `CHANGELOG.md` and updates `package.json#version`
+  for npm projects
+- Disables version bumps and changelog writes independently with `--no-bump` and
+  `--no-changelog`
+- Creates release commits and annotated tags, then pushes them to the remote repository
+- Supports building artifacts from a fixed release commit before publishing
+- Creates or updates GitHub and Gitea Releases
+- Uploads files, directories, or glob matches as GitHub Release assets
+- Adds repository links for commits, pull requests, comparisons, authors, and co-authors
 
 The current release includes `feat`, `fix`, `perf`, breaking changes marked with `!`,
-and commits with a `BREAKING CHANGE` or `BREAKING-CHANGE` trailer. Other commit
-types are ignored.
+and commits with a `BREAKING CHANGE` or `BREAKING-CHANGE` trailer. Other commit types
+are ignored.
 
 ## Quick start
 
@@ -36,50 +41,90 @@ The version may also include a leading `v`:
 npx keepchanges v1.1.0
 ```
 
-By default, the command writes `CHANGELOG.md`. For an npm package, it also
-updates `package.json#version` to `1.1.0`, but it does not create a Git commit.
+By default, the command writes `CHANGELOG.md`. For an npm package, it also updates
+`package.json#version` to `1.1.0`, but it does not create a Git commit.
 
-## Command
+## Release workflows
 
-```text
-npx keepchanges <version> [options]
+Combine the release stages to match how your project manages versions and builds artifacts:
+
+| Workflow | Bump version | Write changelog | Build timing | Release sequence |
+| --- | --- | --- | --- | --- |
+| Full version release | Yes | Yes | After creating the release commit | `--tag`, build, then `--release --asset` |
+| Externally managed version | No | Yes | Before release | Build, then `--release --no-bump --asset` |
+| Artifacts only | No | No | Before release | Build, then `--release --no-bump --no-changelog --asset` |
+
+### Full version release
+
+Let keepchanges update the version and changelog, then create the release commit and tag.
+Build from that exact commit before publishing the same tag and uploading its artifacts:
+
+```bash
+npx keepchanges 1.1.0 --tag
+pnpm build
+GITHUB_TOKEN=github_pat_xxx npx keepchanges 1.1.0 --release --asset dist
 ```
 
-### Arguments and options
+The second command reuses the existing tag. It does not move the tag or commit the artifacts.
 
-| Argument or option | Default | Description |
-| --- | --- | --- |
-| `<version>` | Required | Version to generate. Accepts `1.1.0` or `v1.1.0`. A version containing `-`, such as `1.1.0-beta.1`, is treated as a prerelease. |
-| `--from <ref>` | Inferred from target | Overrides the exclusive starting Git ref used to read commits. Without it, the latest matching tag is used for `HEAD`, or the previous matching tag relative to an explicit `--to`. If no previous tag exists, history starts at the first commit. A version such as `1.0.0` uses the configured tag prefix. |
-| `--to <ref>` | `HEAD` | Sets the ending Git ref. A version such as `1.1.0` uses the configured tag prefix. It cannot be combined with `--release`, and must resolve to the current `HEAD` when used with `--commit`. |
-| `--repository <source>` | Auto-detected | Sets a GitHub `owner/repo` slug or a complete GitHub/Gitea URL. It takes precedence over `package.json` and `origin`. |
-| `--output <path>` | `CHANGELOG.md` | Sets the changelog file path. Relative paths are resolved from the current working directory. |
-| `--dry` | `false` | Prints the current release preview without writing files or performing commit, tag, push, or release API mutations. |
-| `--commit` | `false` | Creates a Git commit after writing. It commits only the changelog and detected version file, using `chore(release): v<version>` by default. |
-| `--release` | `false` | Runs the complete release flow: writes files, creates or reuses a release commit, creates an annotated tag, pushes `HEAD` and the tag, then creates or updates the repository Release. This implies `--commit`. |
-| `--author <author>` | Release bot | Sets the generated release commit author in `"Name <email>"` format; requires `--commit` or `--release`. |
-| `-t, --token <token>` | Environment | Resolves authors and publishes Releases. GitHub precedence is `--token`, `GITHUB_TOKEN`, then `GH_TOKEN`; Gitea uses `GITEA_TOKEN`. |
-| `--tag-prefix <prefix>` | `v` | Sets the prefix used to find and create version tags, such as `package@`. |
-| `--no-tag-prefix` | `false` | Finds and creates version tags without a prefix. |
-| `--name <name>` | Version tag | Sets the remote Release name; only valid with `--release`. |
-| `-d, --draft` | `false` | Creates a draft Release; only valid with `--release`. |
-| `--prerelease` | Inferred | Explicitly marks a prerelease. By default it is inferred from `-` in the version; only valid with `--release`. |
-| `--emoji` | `true` | Controls section title emojis. As with changelogithub, CAC's `--no-emoji` form disables them. |
-| `--capitalize` | `true` | Controls entry capitalization; `--no-capitalize` disables it. |
-| `--group` | `true` | Groups repeated scopes; `--no-group` disables it. |
+### Changelog without a version bump
 
-## Examples
+If another tool or workflow manages the project version, build first, then let keepchanges
+write the changelog, create the commit and tag, and publish the assets:
 
-Write to a different file:
+```bash
+pnpm build
+GITHUB_TOKEN=github_pat_xxx npx keepchanges 1.1.0 --release \
+  --no-bump \
+  --asset dist
+```
+
+### Artifacts only
+
+If the release needs neither a version update nor a changelog write, build first, then create
+the tag and Release from the current `HEAD`:
+
+```bash
+pnpm build
+GITHUB_TOKEN=github_pat_xxx npx keepchanges 1.1.0 --release \
+  --no-bump \
+  --no-changelog \
+  --asset dist
+```
+
+## GitHub Release assets
+
+`--asset` accepts a file, directory, or glob. Directories are traversed recursively, and the
+option is repeatable, so one release can include multiple folders or match sets:
+
+```bash
+GITHUB_TOKEN=github_pat_xxx npx keepchanges 1.1.0 --release \
+  --asset 'packages/*/dist' \
+  --asset artifacts \
+  --asset checksums.txt
+```
+
+Quote globs so keepchanges, rather than the shell, expands them consistently. Before publishing,
+keepchanges verifies that every path exists, every glob matches at least one file, and all final
+file names are unique. Updating an existing Release replaces assets with the same name.
+
+Asset uploads currently support GitHub only and require a GitHub token. Token precedence is
+`--token`, `GITHUB_TOKEN`, then `GH_TOKEN`. Without `--asset`, a regular `--release` can run
+without a token: it commits, tags, and pushes before printing a manual Release URL.
+
+## Common tasks
+
+Write to a different changelog file:
 
 ```bash
 npx keepchanges 1.1.0 --output docs/CHANGELOG.md
 ```
 
-Preview the current release without changing files:
+Preview without changing files or the remote repository:
 
 ```bash
 npx keepchanges 1.1.0 --dry
+npx keepchanges 1.1.0 --release --dry
 ```
 
 Write the changelog, update the version, and create a commit:
@@ -95,42 +140,71 @@ npx keepchanges 1.1.0 --commit \
   --author "Release Author <release@example.com>"
 ```
 
-Create a GitHub Release:
+Create a GitHub Release without assets:
 
 ```bash
 GITHUB_TOKEN=github_pat_xxx npx keepchanges 1.1.0 --release
 ```
 
-Use version tags without a prefix:
+Use version tags without a prefix or with a package-specific prefix:
 
 ```bash
 npx keepchanges 1.1.0 --no-tag-prefix
-```
-
-Use a package-specific tag prefix:
-
-```bash
 npx keepchanges 1.1.0 --tag-prefix 'package@'
 ```
 
-Rebuild a historical release without specifying its previous tag:
+Regenerate a historical release:
 
 ```bash
 npx keepchanges 1.0.0 --to 1.0.0 --dry
 ```
 
-Preview a Release without writing, committing, tagging, pushing, or calling the
-release API:
+## Command reference
 
-```bash
-npx keepchanges 1.1.0 --release --dry
+```text
+npx keepchanges <version> [options]
 ```
 
-## Generation and release behavior
+| Argument or option | Default | Description |
+| --- | --- | --- |
+| `<version>` | Required | Version to generate, such as `1.1.0`, `v1.1.0`, or `1.1.0-beta.1`. |
+| `--from <ref>` | Inferred from target | Sets the exclusive starting Git ref used to read commits. |
+| `--to <ref>` | `HEAD` | Sets the ending Git ref. Cannot be combined with `--tag` or `--release`. |
+| `--repository <source>` | Auto-detected | Sets a GitHub `owner/repo` slug or complete GitHub/Gitea URL. |
+| `--output <path>` | `CHANGELOG.md` | Sets the changelog file path. |
+| `--dry` | `false` | Prints a preview without writing files or performing commit, tag, push, or release API mutations. |
+| `--commit` | `false` | Creates a Git commit after writing. |
+| `--tag` | `false` | Writes, commits, creates an annotated tag, and pushes without creating a repository Release. |
+| `--release` | `false` | Commits, tags, pushes, and creates or updates a repository Release; implies `--commit`. |
+| `--asset <path>` | None | Uploads GitHub Release assets from files, directories, or globs. Repeatable; requires `--release` and a GitHub token. |
+| `--bump` / `--no-bump` | `true` | Controls whether the detected project version file is updated. |
+| `--changelog` / `--no-changelog` | `true` | Controls whether the changelog is written. Release notes are generated either way. |
+| `--author <author>` | Release bot | Sets the release commit author in `"Name <email>"` format. |
+| `-t, --token <token>` | Environment | Sets the repository access token used to resolve authors and publish Releases. |
+| `--tag-prefix <prefix>` | `v` | Sets the prefix used to find and create version tags. |
+| `--no-tag-prefix` | `false` | Finds and creates version tags without a prefix. |
+| `--name <name>` | Version tag | Sets the remote Release name; only valid with `--release`. |
+| `-d, --draft` | `false` | Creates a draft Release; only valid with `--release`. |
+| `--prerelease` | Inferred | Marks a prerelease; only valid with `--release`. |
+| `--emoji` / `--no-emoji` | `true` | Controls section title emojis. |
+| `--capitalize` / `--no-capitalize` | `true` | Controls changelog entry capitalization. |
+| `--group` / `--no-group` | `true` | Controls grouping for repeated scopes. |
 
-The repository is read from `--repository`, then `package.json#repository`, and
-finally the Git `origin`. GitHub URLs are detected automatically. A self-hosted Gitea repository
-must be declared explicitly in `package.json`:
+## Behavior
+
+### Changelog and repository metadata
+
+Without `--from`, keepchanges finds the nearest earlier version tag that matches the configured
+tag prefix. If no earlier tag exists, it reads from the first reachable commit. Stable releases
+compare with the previous stable tag; prereleases compare with the nearest previous tag.
+
+The repository is resolved from `--repository`, then `package.json#repository`, and finally the
+Git `origin`. When a repository is available, entries include commit and pull request links, and
+the release ends with a version comparison link. Entries use Git author names and include
+`Co-Authored-By` participants. With a provider token, keepchanges attempts to resolve email
+addresses to usernames. Bot accounts are omitted.
+
+A self-hosted Gitea repository must be declared explicitly in `package.json`:
 
 ```json
 {
@@ -142,56 +216,38 @@ must be declared explicitly in `package.json`:
 }
 ```
 
-When a repository is detected, entries include commit and pull request links,
-and the release ends with a version comparison link. GitHub and Gitea both
-support author resolution and Release publishing. Gitea uses `GITEA_TOKEN` to
-resolve primary commit authors and publish Releases.
-
-Version tags use the `v` prefix by default. The configured prefix applies to
-new tags, existing-tag lookup, version-shaped `--from` and `--to` values,
-comparison links, and repository Release names. Branch names, commit hashes,
-`HEAD`, and other non-version refs are used unchanged. Tag lookup only considers
-the configured prefix, so independent tag sequences do not affect each other.
-When `--to` is provided without `--from`, the CLI finds the previous matching
-tag relative to that target instead of the current `HEAD`. For the first tag in
-a sequence, it reads all commits reachable from the target.
+GitHub and Gitea both support author resolution and Release publishing. Gitea uses
+`GITEA_TOKEN`, but does not currently support asset uploads.
 
-Entries use Git author names by default and include `Co-Authored-By`
-participants. Bot accounts are omitted. With the corresponding provider token,
-the CLI attempts to resolve email addresses to usernames.
+### Tags and history ranges
 
-`--commit` commits only the changelog and detected version file. Other staged
-and unstaged changes remain untouched.
+Version tags use the `v` prefix by default. The configured prefix applies to tag creation and
+lookup, version-shaped `--from` and `--to` values, comparison links, and Release names. Branch
+names, commit hashes, `HEAD`, and other non-version refs remain unchanged. Tag sequences with
+different prefixes are independent.
 
-When the tag does not exist, `--release`:
+When `--to` is provided without `--from`, keepchanges finds the previous matching tag relative
+to that target instead of the current `HEAD`. With `--commit`, `--to` must resolve to the current
+`HEAD`.
 
-1. Writes the changelog and updates the version file.
-2. Creates or reuses a release commit.
-3. Creates an annotated tag.
-4. Pushes `HEAD` and the tag to `origin`.
-5. Creates a repository Release, or prints a manual URL without a GitHub/Gitea token.
+### Commit and release safety
 
-When the tag already exists, `--release` never moves it. It regenerates Release
-notes from the previous version to the existing tag and creates or updates the
-Release. A remote-only tag is fetched, while a local-only tag is pushed. The
-command stops without force-updating when local and remote tags point to
-different commits.
+`--commit` commits only the changelog and detected version file. Other staged and unstaged
+changes remain untouched.
 
-Stable releases compare with the previous stable tag. Prereleases compare with
-the nearest previous tag. With `--release`, `--dry` takes precedence and
-prevents all file writes and remote mutations. Its manual URL opens a new
-Release for a new tag and the edit page for an existing tag.
+`--release` reuses an existing tag, regenerates its Release notes, and creates or updates the
+Release. A remote-only tag is fetched, while a local-only tag is pushed. If local and remote
+tags point to different commits, the command stops without force-updating or moving the tag.
 
-> [!NOTE]
-> A regular `--release` without a token still writes files, commits, tags, and
-> pushes before providing the manual Release URL. Use `--release --dry`
-> for a completely non-mutating preview.
+`--dry` takes precedence over other options and prevents all file writes and remote mutations.
+Without `--asset` and a provider token, `--release` still writes locally, commits, tags, and
+pushes before printing a URL for manually creating or editing the Release.
 
 ## Programmatic API
 
-The package root exports `generateChangelog`, the commit parser, default config,
-and core types. The CLI is only available as the `keepchanges` binary, while
-programmatic callers can provide changelog style overrides:
+The package root exports `generateChangelog`, the commit parser, default config, and core types.
+The CLI is available only as the `keepchanges` binary. Programmatic callers can override the
+changelog style:
 
 ```ts
 import { generateChangelog } from 'keepchanges'

package/README.zh-CN.md

@@ -1,6 +1,7 @@
 # keepchanges
 
-基于 Conventional Commits 生成并维护 `CHANGELOG.md`。
+面向 Conventional Commits 的发布 CLI：生成并维护 changelog，并按需更新项目版本、
+创建 release commit 和 Git tag、发布 GitHub/Gitea Release，以及上传 GitHub Release 附件。
 
 灵感来自 [changelogithub](https://github.com/antfu-collective/changelogithub)。
 
@@ -8,13 +9,14 @@
 
 ## 功能
 
-- 根据最近的 Git tag 到 `HEAD` 之间的 Conventional Commits 生成变更记录
-- 首次发布时读取完整 Git 历史
-- 将新版本插入 `CHANGELOG.md` 的已有内容之前
-- 为 npm 项目同步更新 `package.json` 中的 `version`
-- 为提交、对比页面、作者和共同作者生成仓库平台信息
-- 可选择自动提交、创建 tag、推送并发布 GitHub/Gitea Release
-- 没有 GitHub/Gitea token 时提供手动发布链接
+- 根据 Git tag 之间的 Conventional Commits 生成 Release notes
+- 将新版本插入现有 `CHANGELOG.md`，并为 npm 项目更新 `package.json#version`
+- 可分别通过 `--no-bump` 和 `--no-changelog` 关闭版本更新与 changelog 写入
+- 可自动创建 release commit、annotated tag 并推送到远程仓库
+- 支持先固定 release commit，再基于该 commit 构建产物
+- 可创建或更新 GitHub/Gitea Release
+- 可将文件、目录或 glob 匹配结果上传为 GitHub Release 附件
+- 为 commit、PR、版本对比、作者和共同作者生成仓库平台信息
 
 当前会收录 `feat`、`fix`、`perf`、带 `!` 的破坏性变更，以及包含
 `BREAKING CHANGE` 或 `BREAKING-CHANGE` trailer 的提交。其他提交类型会被忽略。
@@ -29,56 +31,95 @@
 npx keepchanges 1.1.0
 ```
 
-也可以使用带 `v` 前缀的版本号：
+版本号也可以包含 `v` 前缀：
 
 ```bash
 npx keepchanges v1.1.0
 ```
 
-默认行为会写入 `CHANGELOG.md`。如果当前项目是 npm 包，还会将
-`package.json#version` 更新为 `1.1.0`，但不会自动创建 Git commit。
+默认会写入 `CHANGELOG.md`。如果当前项目是 npm 包，还会将
+`package.json#version` 更新为 `1.1.0`，但不会创建 Git commit。
 
-## 命令格式
+## 发布工作流
 
-```text
-npx keepchanges <version> [options]
+keepchanges 可以根据项目的版本管理和构建方式组合发布阶段：
+
+| 场景 | 更新版本 | 写入 changelog | 构建时机 | 发布方式 |
+| --- | --- | --- | --- | --- |
+| 完整版本发布 | 是 | 是 | 创建 release commit 后 | `--tag`，构建，再 `--release --asset` |
+| 外部管理版本 | 否 | 是 | 发布前 | 构建，再 `--release --no-bump --asset` |
+| 仅发布构建产物 | 否 | 否 | 发布前 | 构建，再 `--release --no-bump --no-changelog --asset` |
+
+### 完整版本发布
+
+先由 keepchanges 更新版本和 changelog、创建 commit 和 tag，再基于该 commit
+构建产物。随后发布同一个 tag，并上传构建产物：
+
+```bash
+npx keepchanges 1.1.0 --tag
+pnpm build
+GITHUB_TOKEN=github_pat_xxx npx keepchanges 1.1.0 --release --asset dist
 ```
 
-### 参数
+第二次执行会复用已有 tag，不会移动 tag 或重新提交构建产物。
 
-| 参数 | 默认值 | 说明 |
-| --- | --- | --- |
-| `<version>` | 必填 | 要生成的版本号。可以传入 `1.1.0` 或 `v1.1.0`。包含 `-` 的版本会作为预发布版本，例如 `1.1.0-beta.1`。 |
-| `--from <ref>` | 根据目标推断 | 指定读取 commit 时不包含在结果中的起始 Git ref，并覆盖自动选择结果。省略时，目标为 `HEAD` 会使用匹配前缀的最近 tag；显式传入 `--to` 会查找该目标之前匹配前缀的 tag。如果不存在前一个 tag，则从首个 commit 开始读取。`1.0.0` 这类版本会自动应用配置的 tag 前缀。 |
-| `--to <ref>` | `HEAD` | 指定读取 commit 的结束 Git ref。`1.1.0` 这类版本会自动应用配置的 tag 前缀。不能与 `--release` 一起使用；与 `--commit` 一起使用时必须指向当前 `HEAD`。 |
-| `--repository <source>` | 自动检测 | 指定 `owner/repo` 格式的 GitHub 仓库或 GitHub/Gitea 完整 URL。优先级高于 `package.json` 和 `origin`。 |
-| `--output <path>` | `CHANGELOG.md` | 指定 changelog 文件路径。相对路径以当前工作目录为基准。 |
-| `--dry` | `false` | 输出当前版本预览，不写入文件，也不执行 commit、tag、push 或发布 API。 |
-| `--commit` | `false` | 写入文件后创建 Git commit。只提交 changelog 和检测到的版本文件，默认提交信息为 `chore(release): v<version>`。 |
-| `--release` | `false` | 执行完整发布流程：写入文件、创建或复用 release commit、创建 annotated tag、推送 `HEAD` 和 tag，然后创建或更新仓库 Release。该参数隐含 `--commit`。 |
-| `--author <author>` | release bot | 设置自动创建的 release commit 作者，格式必须为 `"Name <email>"`；需要与 `--commit` 或 `--release` 一起使用。 |
-| `-t, --token <token>` | 环境变量 | 仓库访问令牌，用于解析作者及发布 Release。GitHub 优先级为 `--token`、`GITHUB_TOKEN`、`GH_TOKEN`；Gitea 使用 `GITEA_TOKEN`。 |
-| `--tag-prefix <prefix>` | `v` | 设置查找和创建版本 tag 时使用的前缀，例如 `package@`。 |
-| `--no-tag-prefix` | `false` | 查找和创建不带前缀的版本 tag。 |
-| `--name <name>` | 版本 tag | 设置远程 Release 名称；仅适用于 `--release`。 |
-| `-d, --draft` | `false` | 创建 draft Release；仅适用于 `--release`。 |
-| `--prerelease` | 根据版本推断 | 显式标记为 prerelease；默认根据版本是否包含 `-` 推断，仅适用于 `--release`。 |
-| `--emoji` | `true` | 控制 section 标题 emoji。与 changelogithub 一样，可使用 CAC 的 `--no-emoji` 形式关闭。 |
-| `--capitalize` | `true` | 控制 changelog 条目首字母大写；可使用 `--no-capitalize` 关闭。 |
-| `--group` | `true` | 当 scope 重复时分组；可使用 `--no-group` 关闭。 |
+### 保留 changelog，跳过版本更新
+
+如果版本由其他工具或流程管理，可以先构建，再让 keepchanges 写入 changelog、
+创建 commit 和 tag，并发布附件：
 
-## 常见用法
+```bash
+pnpm build
+GITHUB_TOKEN=github_pat_xxx npx keepchanges 1.1.0 --release \
+  --no-bump \
+  --asset dist
+```
+
+### 只发布构建产物
+
+如果不需要版本更新和 changelog，可以先构建，再从当前 `HEAD` 创建 tag 和 Release：
+
+```bash
+pnpm build
+GITHUB_TOKEN=github_pat_xxx npx keepchanges 1.1.0 --release \
+  --no-bump \
+  --no-changelog \
+  --asset dist
+```
+
+## GitHub Release 附件
 
-指定输出文件：
+`--asset` 支持单个文件、目录和 glob。目录会递归展开；该参数可以重复使用，
+因此可以同时上传多个文件夹或匹配结果：
+
+```bash
+GITHUB_TOKEN=github_pat_xxx npx keepchanges 1.1.0 --release \
+  --asset 'packages/*/dist' \
+  --asset artifacts \
+  --asset checksums.txt
+```
+
+建议始终给 glob 加引号，确保由 keepchanges 而不是 shell 展开。发布前会验证所有
+附件：路径必须存在、glob 必须至少匹配一个文件，并且最终文件名必须唯一。
+更新已有 Release 时，同名附件会被替换。
+
+附件上传目前只支持 GitHub，并且必须提供 GitHub token。token 的读取顺序为
+`--token`、`GITHUB_TOKEN`、`GH_TOKEN`。如果没有指定 `--asset`，则普通
+`--release` 可以在没有 token 时完成 commit、tag 和 push，随后输出手动发布链接。
+
+## 常见任务
+
+指定 changelog 文件：
 
 ```bash
 npx keepchanges 1.1.0 --output docs/CHANGELOG.md
 ```
 
-预览当前版本，不修改文件：
+预览结果，不修改文件或远程仓库：
 
 ```bash
 npx keepchanges 1.1.0 --dry
+npx keepchanges 1.1.0 --release --dry
 ```
 
 写入 changelog、更新版本并创建 commit：
@@ -87,47 +128,77 @@ npx keepchanges 1.1.0 --dry
 npx keepchanges 1.1.0 --commit
 ```
 
-指定 release commit 的作者：
+指定 release commit 作者：
 
 ```bash
 npx keepchanges 1.1.0 --commit \
   --author "Release Author <release@example.com>"
 ```
 
-创建 GitHub Release：
+创建不带附件的 GitHub Release：
 
 ```bash
 GITHUB_TOKEN=github_pat_xxx npx keepchanges 1.1.0 --release
 ```
 
-使用无前缀版本 tag：
+使用无前缀或 package 专属版本 tag：
 
 ```bash
 npx keepchanges 1.1.0 --no-tag-prefix
-```
-
-使用 package 专属 tag 前缀：
-
-```bash
 npx keepchanges 1.1.0 --tag-prefix 'package@'
 ```
 
-不指定前一个 tag，重新生成历史版本：
+重新生成历史版本：
 
 ```bash
 npx keepchanges 1.0.0 --to 1.0.0 --dry
 ```
 
-预览 Release，不写文件、不提交、不创建 tag、不推送且不调用发布 API：
+## 命令参考
 
-```bash
-npx keepchanges 1.1.0 --release --dry
+```text
+npx keepchanges <version> [options]
 ```
 
-## 生成和发布行为
+| 参数 | 默认值 | 说明 |
+| --- | --- | --- |
+| `<version>` | 必填 | 要生成的版本号，例如 `1.1.0`、`v1.1.0` 或 `1.1.0-beta.1`。 |
+| `--from <ref>` | 根据目标推断 | 指定读取 commit 时不包含在结果中的起始 Git ref。 |
+| `--to <ref>` | `HEAD` | 指定结束 Git ref。不能与 `--tag` 或 `--release` 一起使用。 |
+| `--repository <source>` | 自动检测 | 指定 GitHub `owner/repo` 或 GitHub/Gitea 完整 URL。 |
+| `--output <path>` | `CHANGELOG.md` | 指定 changelog 文件路径。 |
+| `--dry` | `false` | 输出预览，不执行文件写入、commit、tag、push 或发布 API。 |
+| `--commit` | `false` | 写入后创建 Git commit。 |
+| `--tag` | `false` | 写入、commit、创建 annotated tag 并 push，但不创建仓库 Release。 |
+| `--release` | `false` | 完成 commit、tag、push，并创建或更新仓库 Release；隐含 `--commit`。 |
+| `--asset <path>` | 无 | 上传 GitHub Release 附件；支持文件、目录、glob 和重复传参。需要 `--release` 和 GitHub token。 |
+| `--bump` / `--no-bump` | `true` | 控制是否更新检测到的项目版本文件。 |
+| `--changelog` / `--no-changelog` | `true` | 控制是否写入 changelog；关闭后仍会生成 Release notes。 |
+| `--author <author>` | release bot | 指定 release commit 作者，格式为 `"Name <email>"`。 |
+| `-t, --token <token>` | 环境变量 | 指定仓库访问令牌，用于解析作者和发布 Release。 |
+| `--tag-prefix <prefix>` | `v` | 指定查找和创建版本 tag 时使用的前缀。 |
+| `--no-tag-prefix` | `false` | 查找和创建不带前缀的版本 tag。 |
+| `--name <name>` | 版本 tag | 指定远程 Release 名称；仅适用于 `--release`。 |
+| `-d, --draft` | `false` | 创建 draft Release；仅适用于 `--release`。 |
+| `--prerelease` | 根据版本推断 | 标记 prerelease；仅适用于 `--release`。 |
+| `--emoji` / `--no-emoji` | `true` | 控制 section 标题 emoji。 |
+| `--capitalize` / `--no-capitalize` | `true` | 控制 changelog 条目首字母大写。 |
+| `--group` / `--no-group` | `true` | 控制重复 scope 分组。 |
+
+## 行为说明
+
+### Changelog 和仓库信息
 
-仓库地址优先读取 `--repository`，其次读取 `package.json#repository`，最后读取 Git 的 `origin`。
-GitHub 地址会被自动识别。自托管 Gitea 需要在 `package.json` 中显式声明：
+省略 `--from` 时，keepchanges 会查找目标之前匹配 tag 前缀的最近版本 tag。
+如果不存在前一个 tag，则从首个可达 commit 开始读取。稳定版本与前一个稳定 tag
+对比，预发布版本与最近的前一个 tag 对比。
+
+仓库地址依次读取 `--repository`、`package.json#repository` 和 Git `origin`。
+识别仓库后，记录会包含 commit 和 PR 链接，末尾会包含版本对比链接。默认使用
+Git 作者名并包含 `Co-Authored-By` 参与者；提供平台 token 后，会尝试将邮箱解析为
+用户名。bot 账号会被忽略。
+
+自托管 Gitea 仓库需要在 `package.json` 中显式声明：
 
 ```json
 {
@@ -139,50 +210,36 @@ GitHub 地址会被自动识别。自托管 Gitea 需要在 `package.json` 中
 }
 ```
 
-识别到仓库后，每条记录会包含 commit 和 PR 链接，末尾会包含版本对比链接。
-GitHub 和 Gitea 均支持作者解析和 Release 发布；Gitea 使用 `GITEA_TOKEN`
-解析 commit 主作者并发布 Release。
+GitHub 和 Gitea 均支持作者解析与 Release 发布。Gitea 使用 `GITEA_TOKEN`，
+但目前不支持附件上传。
 
-版本 tag 默认使用 `v` 前缀。配置的前缀会统一应用于新 tag、已有 tag 查找、
-版本形式的 `--from` 和 `--to`、比较链接及仓库 Release 名称。分支名、commit
-hash、`HEAD` 等非版本 ref 保持不变。自动查找 tag 时只考虑配置的前缀，因此
-彼此独立的 tag 序列不会相互影响。
-省略 `--from` 并传入 `--to` 时，CLI 会相对于该目标查找匹配前缀的前一个 tag，
-而不是使用当前 `HEAD` 的最近 tag。如果目标是该序列中的首个 tag，则读取该目标
-可达的全部 commit。
+### Tag 和历史范围
 
-默认使用 Git 提交中的作者名，并将 `Co-Authored-By` 参与者一起写入记录，bot
-账号会被忽略。提供对应平台的 token 后，会尝试将邮箱解析为用户名。
+版本 tag 默认使用 `v` 前缀。配置的前缀会应用于 tag 创建和查找、版本形式的
+`--from` 和 `--to`、比较链接及 Release 名称。分支名、commit hash 和 `HEAD`
+等非版本 ref 保持不变。不同前缀的 tag 序列彼此独立。
 
-`--commit` 只提交 changelog 和检测到的版本文件。其他已暂存或未暂存的改动会
-保持原状。
+显式传入 `--to` 而不传 `--from` 时，会相对于该目标查找前一个匹配的 tag，
+而不是使用当前 `HEAD` 的最近 tag。与 `--commit` 一起使用时，`--to` 必须指向
+当前 `HEAD`。
 
-`--release` 在 tag 不存在时：
+### Commit 和发布安全
 
-1. 写入 changelog 并更新版本文件。
-2. 创建或复用 release commit。
-3. 创建 annotated tag。
-4. 将 `HEAD` 和 tag 推送到 `origin`。
-5. 创建仓库 Release；GitHub/Gitea 没有 token 时输出手动发布链接。
-
-`--release` 在 tag 已存在时不会移动 tag。它会根据前一个版本到现有 tag
-重新生成 Release notes，并创建或更新 Release。只有远程存在 tag 时会先将它
-拉取到本地；只有本地存在 tag 时会推送该 tag。本地与远程 tag 指向不同 commit
-时会停止，不会强制覆盖。
+`--commit` 只提交 changelog 和检测到的版本文件，其他已暂存或未暂存的改动会
+保持原状。
 
-稳定版本会与前一个稳定 tag 对比，预发布版本会与最近的前一个 tag 对比。与
-`--release` 搭配的 `--dry` 优先级最高，不会执行任何写入或远程修改。手动链接
-会为新 tag 打开创建 Release 页面，为已有 tag 打开编辑页面。
+`--release` 会复用已有 tag，重新生成该版本的 Release notes，并创建或更新
+Release。远程独有的 tag 会被拉取，本地独有的 tag 会被推送；本地和远程 tag
+指向不同 commit 时会停止，不会强制覆盖或移动 tag。
 
-> [!NOTE]
-> 没有 token 的普通 `--release` 仍会执行本地写入、commit、tag 和 push，
-> 然后提供手动创建 Release 的链接。如需完全无副作用的预览，请使用
-> `--release --dry`。
+`--dry` 优先于其他选项，不会执行任何文件写入或远程修改。未指定 `--asset` 且
+没有平台 token 时，`--release` 仍会执行本地写入、commit、tag 和 push，随后
+提供手动创建或编辑 Release 的链接。
 
 ## 程序化 API
 
 包根入口导出 `generateChangelog`、commit parser、默认配置及核心类型。
-CLI 仅作为 `keepchanges` 二进制命令。程序化调用可以传入 changelog 样式覆盖：
+CLI 仅作为 `keepchanges` 二进制命令。程序化调用可以覆盖 changelog 样式：
 
 ```ts
 import { generateChangelog } from 'keepchanges'

package/dist/cli.mjs

@@ -1,14 +1,15 @@
 #!/usr/bin/env node
-import { a as insertRelease, c as defaultConfig, i as hasRelease, n as parseCommits, o as readChangelog, r as generateChangelog, s as writeChangelog } from "./commit-DBopyhs1.mjs";
-import { readFile, writeFile } from "node:fs/promises";
+import { a as insertRelease, c as defaultConfig, i as hasRelease, n as parseCommits, o as readChangelog, r as generateChangelog, s as writeChangelog } from "./commit-DswG6QDH.mjs";
+import { lstat, readFile, readdir, writeFile } from "node:fs/promises";
 import { normalizeFull } from "verkit";
 import process from "node:process";
 import { cac } from "cac";
-import { resolve } from "node:path";
+import { basename, resolve } from "node:path";
 import ansis from "ansis";
+import { glob, isDynamicPattern } from "tinyglobby";
 import { x } from "tinyexec";
 //#region package.json
-var version = "1.0.2";
+var version = "1.0.3";
 //#endregion
 //#region src/git.ts
 function versionTagPattern(tagPrefix) {
@@ -166,6 +167,7 @@ const giteaRepository = {
 const githubRepository = {
 	name: "GitHub",
 	tokenEnv: "GITHUB_TOKEN",
+	supportsReleaseAssets: true,
 	parse(source) {
 		const match = /github\.com[:/]([^/]+\/[^/]+?)(?:\.git)?$/.exec(source);
 		if (!match) return;
@@ -224,10 +226,13 @@ const githubRepository = {
 		let url = releasesUrl;
 		let method = "POST";
 		let action = "created";
+		let existingAssets = [];
 		if (existing.ok) {
-			url = `${releasesUrl}/${(await existing.json()).id}`;
+			const data = await existing.json();
+			url = `${releasesUrl}/${data.id}`;
 			method = "PATCH";
 			action = "updated";
+			existingAssets = data.assets ?? [];
 		} else if (existing.status !== 404) throw new Error(`GitHub release lookup failed (${existing.status})`);
 		const response = await fetch(url, {
 			method,
@@ -241,8 +246,33 @@ const githubRepository = {
 			})
 		});
 		if (!response.ok) throw new Error(`GitHub release publishing failed (${response.status})`);
+		const data = await response.json();
+		if (release.assets?.length) {
+			if (!data.upload_url) throw new Error("GitHub release response did not include an upload URL");
+			const uploadUrl = data.upload_url.replace(/\{.*$/, "");
+			for (const asset of release.assets) {
+				const existingAsset = existingAssets.find((candidate) => candidate.name === asset.name);
+				if (existingAsset) {
+					const deleteResponse = await fetch(`https://api.github.com/repos/${repository.path}/releases/assets/${existingAsset.id}`, {
+						method: "DELETE",
+						headers
+					});
+					if (!deleteResponse.ok) throw new Error(`GitHub release asset replacement failed for ${asset.name} (${deleteResponse.status})`);
+				}
+				const uploadResponse = await fetch(`${uploadUrl}?name=${encodeURIComponent(asset.name)}`, {
+					method: "POST",
+					headers: {
+						"accept": "application/vnd.github+json",
+						"authorization": `Bearer ${token}`,
+						"content-type": "application/octet-stream"
+					},
+					body: asset.data
+				});
+				if (!uploadResponse.ok) throw new Error(`GitHub release asset upload failed for ${asset.name} (${uploadResponse.status})`);
+			}
+		}
 		return {
-			url: (await response.json()).html_url,
+			url: data.html_url,
 			action
 		};
 	}
@@ -332,7 +362,7 @@ function printPublishedRelease(provider, result, stdout, colors) {
 //#endregion
 //#region src/cli/createChanges.ts
 async function createChanges(options, environment) {
-	if (options.commit && options.to !== defaultConfig.cli.to) {
+	if ((options.commit || options.tag || options.release) && options.to !== defaultConfig.cli.to) {
 		const [toCommit, headCommit] = await Promise.all([git(environment.cwd, "rev-parse", options.to).then((value) => value.trim()), git(environment.cwd, "rev-parse", "HEAD").then((value) => value.trim())]);
 		if (toCommit !== headCommit) throw new Error("--to must resolve to HEAD when used with --commit");
 	}
@@ -343,9 +373,12 @@ async function createChanges(options, environment) {
 	const repository = await resolveRepository(environment.cwd, options.repository);
 	const token = repository?.provider.token(options.token, env);
 	validateReleaseSupport(options, repository);
-	let taggedCommit = options.release ? await getTagCommit(environment.cwd, tag) : void 0;
+	if (options.release && !options.dry && options.assets.length && !token) throw new Error(`A ${repository.provider.name} token is required to upload release assets`);
+	const releaseAssets = options.release && !options.dry && options.assets.length ? await readReleaseAssets(environment.cwd, options.assets) : [];
+	const createsTag = options.tag || options.release;
+	let taggedCommit = createsTag ? await getTagCommit(environment.cwd, tag) : void 0;
 	let releaseRef = taggedCommit ? tag : void 0;
-	const remoteTaggedCommit = options.release ? await getRemoteTagCommit(environment.cwd, tag) : void 0;
+	const remoteTaggedCommit = createsTag ? await getRemoteTagCommit(environment.cwd, tag) : void 0;
 	if (taggedCommit && remoteTaggedCommit && taggedCommit !== remoteTaggedCommit) throw new Error(`Tag ${tag} differs between local and origin`);
 	if (remoteTaggedCommit && !taggedCommit) if (options.dry) {
 		taggedCommit = remoteTaggedCommit;
@@ -396,38 +429,45 @@ async function createChanges(options, environment) {
 		}
 		return;
 	}
-	if (options.release && taggedCommit) {
+	if (createsTag && taggedCommit) {
 		if (!remoteTaggedCommit) await git(environment.cwd, "push", "origin", `refs/tags/${tag}`);
-		await publishRelease(repository, repositoryRelease, token, preview, environment, "edit");
+		if (!options.release) return;
+		await publishRelease(repository, repositoryRelease, token, preview, environment, releaseAssets, "edit");
 		return;
 	}
-	const outputPath = resolve(environment.cwd, options.output);
-	const currentChangelog = await readChangelog(outputPath);
-	const releaseExists = hasRelease(currentChangelog, options.version);
-	await writeChangelog(outputPath, insertRelease(currentChangelog, release));
-	const versionPath = await updateVersion(environment.cwd, options.version);
-	if (options.commit || options.release) await commitReleaseFiles(options, environment.cwd, outputPath, versionPath, releaseExists, tag);
-	if (options.release) {
+	let outputPath;
+	let releaseExists = false;
+	if (options.changelog) {
+		outputPath = resolve(environment.cwd, options.output);
+		const currentChangelog = await readChangelog(outputPath);
+		releaseExists = hasRelease(currentChangelog, options.version);
+		await writeChangelog(outputPath, insertRelease(currentChangelog, release));
+	}
+	const versionPath = options.bump ? await updateVersion(environment.cwd, options.version) : void 0;
+	if (options.commit || createsTag) await commitReleaseFiles(options, environment.cwd, outputPath, versionPath, releaseExists, tag);
+	if (createsTag) {
 		const gitIdentity = resolveGitIdentity(options.author);
 		await git(environment.cwd, ...gitIdentity, "tag", "-a", tag, "-m", tag);
 		await git(environment.cwd, "push", "origin", "HEAD", `refs/tags/${tag}`);
-		await publishRelease(repository, repositoryRelease, token, preview, environment);
+		if (options.release) await publishRelease(repository, repositoryRelease, token, preview, environment, releaseAssets);
 	}
 }
 function validateReleaseSupport(options, repository) {
 	if (!options.release) return;
 	if (!repository) throw new Error("A supported repository is required to release");
 	if (!repository.provider.publishRelease && !repository.provider.manualReleaseUrl) throw new Error(`${repository.provider.name} does not support releases`);
+	if (options.assets.length && !repository.provider.supportsReleaseAssets) throw new Error(`${repository.provider.name} does not support release assets`);
 }
 async function commitReleaseFiles(options, cwd, outputPath, versionPath, releaseExists, tag) {
 	const releasePaths = [outputPath, versionPath].filter((path) => path !== void 0);
+	if (!releasePaths.length) return;
 	if (!(await git(cwd, "status", "--porcelain", "--", ...releasePaths)).trim()) return;
 	await git(cwd, "add", "--", ...releasePaths);
 	const versionChanges = versionPath ? await git(cwd, "status", "--porcelain", "--", versionPath) : "";
 	const commitMessage = versionPath && !versionChanges.trim() ? `docs(changelog): ${releaseExists ? "update" : "add"} ${tag} release notes` : `chore(release): ${tag}`;
 	await git(cwd, ...resolveGitIdentity(options.author), "commit", "-m", commitMessage, ...options.author ? ["--author", options.author] : [], "--only", "--", ...releasePaths);
 }
-async function publishRelease(repository, release, token, preview, environment, manualAction = "create") {
+async function publishRelease(repository, release, token, preview, environment, assets, manualAction = "create") {
 	const stdout = environment.stdout ?? ((value) => process.stdout.write(value));
 	const colors = environment.colors ?? ansis;
 	printChangesPreview(preview, stdout, colors);
@@ -437,9 +477,52 @@ async function publishRelease(repository, release, token, preview, environment,
 		printManualReleaseUrl(repository, release, stdout, colors, manualAction);
 		return;
 	}
-	const result = await repository.provider.publishRelease(repository, release, token, environment.fetch ?? globalThis.fetch);
+	const result = await repository.provider.publishRelease(repository, {
+		...release,
+		assets
+	}, token, environment.fetch ?? globalThis.fetch);
 	printPublishedRelease(repository.provider.name, result, stdout, colors);
 }
+async function readReleaseAssets(cwd, paths) {
+	const files = /* @__PURE__ */ new Set();
+	async function collect(path) {
+		const metadata = await lstat(path).catch(() => void 0);
+		if (!metadata) throw new Error(`Release asset does not exist: ${path}`);
+		if (metadata.isFile()) {
+			files.add(path);
+			return;
+		}
+		if (!metadata.isDirectory()) throw new Error(`Release asset must be a file or directory: ${path}`);
+		const entries = await readdir(path, { withFileTypes: true });
+		for (const entry of entries.sort((left, right) => left.name.localeCompare(right.name))) await collect(resolve(path, entry.name));
+	}
+	for (const path of paths) {
+		if (!isDynamicPattern(path)) {
+			await collect(resolve(cwd, path));
+			continue;
+		}
+		const matches = await glob(path, {
+			absolute: true,
+			cwd,
+			dot: true,
+			expandDirectories: false,
+			followSymbolicLinks: false,
+			onlyFiles: false
+		});
+		if (!matches.length) throw new Error(`Release asset pattern did not match: ${path}`);
+		for (const match of matches.sort((left, right) => left.localeCompare(right))) await collect(match);
+	}
+	const names = /* @__PURE__ */ new Set();
+	return Promise.all([...files].map(async (path) => {
+		const name = basename(path);
+		if (names.has(name)) throw new Error(`Release assets must have unique file names: ${name}`);
+		names.add(name);
+		return {
+			name,
+			data: await readFile(path)
+		};
+	}));
+}
 function resolveGitIdentity(author) {
 	const match = /^([^<>\r\n]+)<([^<>\r\n]+)>$/.exec(author);
 	if (!match) throw new Error("Author must use the \"Name <email>\" format");
@@ -462,8 +545,9 @@ function resolveOptions(versionArgument, options) {
 	if (typeof options.tagPrefix === "string") tagPrefix = options.tagPrefix;
 	else if (options.tagPrefix === false) tagPrefix = "";
 	if (options.to !== void 0 && release) throw new Error("--to cannot be used with --release");
-	if (options.author !== void 0 && !commit && !release) throw new Error("--author requires --commit or --release");
-	if (!release && (options.name !== void 0 || options.draft !== void 0 || options.prerelease !== void 0)) throw new Error("--name, --draft, and --prerelease require --release");
+	if (options.to !== void 0 && options.tag) throw new Error("--to cannot be used with --tag");
+	if (options.author !== void 0 && !commit && !options.tag && !release) throw new Error("--author requires --commit, --tag, or --release");
+	if (!release && (options.name !== void 0 || options.draft !== void 0 || options.prerelease !== void 0 || (options.asset?.length ?? 0) > 0)) throw new Error("--name, --draft, --prerelease, and --asset require --release");
 	return {
 		version,
 		from: options.from,
@@ -472,7 +556,11 @@ function resolveOptions(versionArgument, options) {
 		output: options.output ?? defaultConfig.cli.output,
 		dry: options.dry ?? defaultConfig.cli.dry,
 		commit,
+		tag: options.tag ?? defaultConfig.cli.tag,
 		release,
+		assets: options.asset ?? [],
+		bump: options.bump ?? defaultConfig.cli.bump,
+		changelog: options.changelog ?? defaultConfig.cli.changelog,
 		author: options.author ?? defaultConfig.cli.author,
 		token: options.token,
 		tagPrefix,
@@ -486,7 +574,10 @@ function resolveOptions(versionArgument, options) {
 }
 //#endregion
 //#region src/cli.ts
-const cli = cac("keepchanges").option("--from <ref>", "Start Git reference").option("--to <ref>", "End Git reference").option("--repository <source>", "Repository slug or URL").option("--output <path>", "Changelog file path").option("--dry", "Preview without modifying files or remotes").option("--commit", "Commit the changelog and version update").option("--release", "Publish a repository release").option("--author <author>", "Commit author in \"Name <email>\" format").option("-t, --token <token>", "Repository token").option("--no-tag-prefix", "Create version tags without a prefix").option("--tag-prefix <prefix>", "Prefix used for version tags", { default: defaultConfig.cli.tagPrefix }).option("--name <name>", "Repository release name").option("-d, --draft", "Create a draft repository release").option("--prerelease", "Mark the repository release as prerelease").option("--emoji", "Use emojis in changelog section titles").option("--capitalize", "Capitalize changelog entries").option("--group", "Group repeated commit scopes");
+const cli = cac("keepchanges").option("--from <ref>", "Start Git reference").option("--to <ref>", "End Git reference").option("--repository <source>", "Repository slug or URL").option("--output <path>", "Changelog file path").option("--dry", "Preview without modifying files or remotes").option("--commit", "Commit the changelog and version update").option("--tag", "Commit, tag, and push without publishing a release").option("--release", "Publish a repository release").option("--asset <path>", "Release asset file, directory, or glob", {
+	type: [],
+	default: []
+}).option("--bump", "Update the project version; --no-bump disables it", { default: defaultConfig.cli.bump }).option("--changelog", "Write the changelog; --no-changelog disables it", { default: defaultConfig.cli.changelog }).option("--author <author>", "Commit author in \"Name <email>\" format").option("-t, --token <token>", "Repository token").option("--no-tag-prefix", "Create version tags without a prefix").option("--tag-prefix <prefix>", "Prefix used for version tags", { default: defaultConfig.cli.tagPrefix }).option("--name <name>", "Repository release name").option("-d, --draft", "Create a draft repository release").option("--prerelease", "Mark the repository release as prerelease").option("--emoji", "Use emojis in changelog section titles").option("--capitalize", "Capitalize changelog entries").option("--group", "Group repeated commit scopes");
 cli.command("<version>").usage("<version> [options]").action(async (versionArgument, options) => {
 	await createChanges(resolveOptions(versionArgument, options), { cwd: process.cwd() });
 });

package/dist/{commit-DBopyhs1.mjs → commit-DswG6QDH.mjs}

@@ -7,7 +7,10 @@ const defaultConfig = {
 		to: "HEAD",
 		dry: false,
 		commit: false,
+		tag: false,
 		release: false,
+		bump: true,
+		changelog: true,
 		author: "github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>",
 		tagPrefix: "v",
 		draft: false

package/dist/index.d.mts

@@ -19,6 +19,13 @@ interface RepositoryRelease {
   body: string;
   prerelease: boolean;
   draft: boolean;
+  assets?: RepositoryReleaseAsset[];
+}
+interface RepositoryReleaseAsset {
+  /** File name shown on the Release; names must be unique within a Release. */
+  name: string;
+  /** Exact bytes sent to the repository provider. */
+  data: Uint8Array;
 }
 interface RepositoryReleaseResult {
   url: string;
@@ -28,6 +35,7 @@ type ManualReleaseAction = 'create' | 'edit';
 interface RepositoryProvider {
   name: string;
   tokenEnv: string;
+  supportsReleaseAssets?: boolean;
   parse: (source: string) => Repository | undefined;
   token: (explicit: string | undefined, env: NodeJS.ProcessEnv) => string | undefined;
   commitUrl: (repository: Repository, hash: string) => string;
@@ -88,7 +96,10 @@ interface KeepChangesConfig {
     to: string;
     dry: boolean;
     commit: boolean;
+    tag: boolean;
     release: boolean;
+    bump: boolean;
+    changelog: boolean;
     author: string;
     tagPrefix: string;
     draft: boolean;
@@ -101,7 +112,10 @@ declare const defaultConfig: {
     to: string;
     dry: false;
     commit: false;
+    tag: false;
     release: false;
+    bump: true;
+    changelog: true;
     author: string;
     tagPrefix: string;
     draft: false;
@@ -154,4 +168,4 @@ declare function writeChangelog(path: string, changelog: string): Promise<void>;
 declare function hasRelease(changelog: string, version: string): boolean;
 declare function insertRelease(changelog: string, release: string): string;
 //#endregion
-export { type ChangelogConfig, type ChangelogConfigOverrides, type ChangelogMessages, type ChangelogSectionConfig, type Commit, type GenerateChangelogOptions, type GeneratedChangelog, type KeepChangesConfig, type ManualReleaseAction, type RawCommit, type Repository, type RepositoryAuthor, type RepositoryCommit, type RepositoryProvider, type RepositoryRelease, type RepositoryReleaseResult, defaultConfig, generateChangelog, hasRelease, insertRelease, parseCommit, parseCommits, readChangelog, resolveChangelogConfig, writeChangelog };
+export { type ChangelogConfig, type ChangelogConfigOverrides, type ChangelogMessages, type ChangelogSectionConfig, type Commit, type GenerateChangelogOptions, type GeneratedChangelog, type KeepChangesConfig, type ManualReleaseAction, type RawCommit, type Repository, type RepositoryAuthor, type RepositoryCommit, type RepositoryProvider, type RepositoryRelease, type RepositoryReleaseAsset, type RepositoryReleaseResult, defaultConfig, generateChangelog, hasRelease, insertRelease, parseCommit, parseCommits, readChangelog, resolveChangelogConfig, writeChangelog };

package/dist/index.mjs

@@ -1,2 +1,2 @@
-import { a as insertRelease, c as defaultConfig, i as hasRelease, l as resolveChangelogConfig, n as parseCommits, o as readChangelog, r as generateChangelog, s as writeChangelog, t as parseCommit } from "./commit-DBopyhs1.mjs";
+import { a as insertRelease, c as defaultConfig, i as hasRelease, l as resolveChangelogConfig, n as parseCommits, o as readChangelog, r as generateChangelog, s as writeChangelog, t as parseCommit } from "./commit-DswG6QDH.mjs";
 export { defaultConfig, generateChangelog, hasRelease, insertRelease, parseCommit, parseCommits, readChangelog, resolveChangelogConfig, writeChangelog };

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "keepchanges",
   "type": "module",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "Generate and maintain CHANGELOG.md from Conventional Commits.",
   "author": "edram",
   "license": "MIT",
@@ -36,6 +36,7 @@
     "ansis": "^4.3.1",
     "cac": "^7.0.0",
     "tinyexec": "^1.2.4",
+    "tinyglobby": "^0.2.17",
     "verkit": "^0.3.0"
   },
   "devDependencies": {