chore(release): 3.3.1

[github-actions]

simple-release-tools

3.3.1 (2026-09-05)

Bug Fixes

• core: make as: prerelease produce a prerelease on stable versions (#194) (aebb485)
• deps: update dependency @astrojs/starlight to ^0.42.0 (#192) (4dd989f)
• github: drop publish options and fix preamble heading level in the pull request cheatsheet (#195) (b753abb)

@simple-release/core

3.3.1 (2026-09-05)

Bug Fixes

• make as: prerelease produce a prerelease on stable versions (#194) (aebb485)

@simple-release/github

3.3.1 (2026-09-05)

Bug Fixes

• drop publish options and fix preamble heading level in the pull request cheatsheet (#195) (b753abb)

---

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": {}
}
```

Useful Parameters

The options shape the pull request generation, so the bump ones matter here. Release-time options like publish belong in the config file.

Parameter	Type	Description
version	string	Force set specific version
as	'major' | 'minor' | 'patch' | 'prerelease'	Release type. prerelease keeps the type derived from the commits and makes the version a prerelease
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

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"
  }
}
```

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. Start its headings at ### — the level of the generated changelog sections like ### Features.

!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 33973883395

Coverage remained the same at 69.769%

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:	1046
Covered Lines:	725
Line Coverage:	69.31%
Relevant Branches:	211
Covered Branches:	152
Branch Coverage:	72.04%
Branches in Coverage %:	Yes
Coverage Strength:	11.05 hits per line

---

💛 - Coveralls