chore(release): 3.3.0

[github-actions]

simple-release-tools

3.3.0 (2026-07-14)

Features

• core,github-action,github: support custom changelog preamble (#187) (7ee2d19)

Bug Fixes

• core: always resolve the getProjects cache (fb94518)
• deps: update dependency argue-cli to v3 (#184) (329e3ef)
• deps: update dependency starlight-llms-txt to ^0.11.0 (#181) (98e43fe)

@simple-release/core

3.3.0 (2026-07-14)

Features

• support custom changelog preamble (#187) (7ee2d19)

Bug Fixes

• always resolve the getProjects cache (fb94518)

@simple-release/github

3.3.0 (2026-07-14)

Features

• support custom changelog preamble (#187) (7ee2d19)

@simple-release/github-action

3.3.0 (2026-07-14)

Features

• support custom changelog preamble (#187) (7ee2d19)

simple-github-release

3.3.0 (2026-07-14)

Bug Fixes

• update dependency argue-cli to v3 (#184) (329e3ef)

---

This PR was generated with simple-release.

📄 Cheatsheet

You can configure the bot's behavior through a pull request comment using the !simple-release/set-options command.

Command Format

!simple-release/set-options

```json
{
  "bump": {},
  "publish": {}
}
```

Useful Parameters

Bump

Parameter	Type	Description
version	string	Force set specific version
as	'major' | 'minor' | 'patch' | 'prerelease'	Release type
prerelease	string	Pre-release identifier (e.g., "alpha", "beta")
firstRelease	boolean	Whether this is the first release
skip	boolean	Skip version bump
byProject	Record<string, object>	Per-project bump options for monorepos

Publish

Parameter	Type	Description
skip	boolean	Skip publishing
access	'public' | 'restricted'	Package access level
tag	string	Tag for npm publication

Usage Examples

Force specific version

!simple-release/set-options

```json
{
  "bump": {
    "version": "2.0.0"
  }
}
```

Force major bump

!simple-release/set-options

```json
{
  "bump": {
    "as": "major"
  }
}
```

Create alpha pre-release

!simple-release/set-options

```json
{
  "bump": {
    "prerelease": "alpha"
  }
}
```

Publish with specific access and tag

!simple-release/set-options

```json
{
  "bump": {
    "prerelease": "beta"
  },
  "publish": {
    "access": "public",
    "tag": "beta"
  }
}
```

Custom Changelog Preamble

You can add custom markdown to the top of the changelog (right after the version header) using the !simple-release/set-preamble command. The markdown after the command line becomes the preamble.

!simple-release/set-preamble

## What's new?

- The website was completely redesigned
- The new API gives you awesome possibilities

In a monorepo, pass the full package name after the command to target a single package's changelog. Wrap the name in backticks so GitHub keeps it as text instead of a mention:

!simple-release/set-preamble `@your-org/core`

## Core changes

- New plugin system

Use one comment per package, plus one without a name for the whole release.

Access Restrictions

The commands can only be used by users with permissions:

• repository owner
• organization member
• collaborator

Notes

• The last comment with !simple-release/set-options command takes priority
• The last !simple-release/set-preamble comment per package takes priority
• JSON must be valid, otherwise the set-options command will be ignored
• Parameters apply only to the current release execution
• The commands can be updated by editing the comment or adding a new one

[coveralls]

Coverage Report for CI Build 29338609805

Coverage remained the same at 63.087%

Details

• Coverage remained the same as the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	1045
Covered Lines:	718
Line Coverage:	68.71%
Relevant Branches:	594
Covered Branches:	316
Branch Coverage:	53.2%
Branches in Coverage %:	Yes
Coverage Strength:	10.77 hits per line

---

💛 - Coveralls