chore(release): 11.0.0

[github-actions]

scripts

11.0.0 (2026-10-15)

⚠ BREAKING CHANGES

• oxlint-config: rename import-order option newlines-between to newlinesBetween

Features

• oxlint-config: quote only object keys that need quotes (cf2e9a8)
• oxlint-config: rename import-order option newlines-between to newlinesBetween (083c2b9)

Bug Fixes

• deps: update dependency npm-package-json-lint to v11 (#193) (a69beca)
• deps: update dependency npm-package-json-lint-config-default to v10 (#194) (1f54e2c)
• oxlint-config: allow parentheses around calls in arrow bodies and ternary branches (ad6746d)
• stylelint-config: allow CSS Modules :global and :local pseudo-classes (64c4fef)

@trigen/oxlint-config

11.0.0 (2026-10-15)

⚠ BREAKING CHANGES

• rename import-order option newlines-between to newlinesBetween

Features

• quote only object keys that need quotes (cf2e9a8)
• rename import-order option newlines-between to newlinesBetween (083c2b9)

Bug Fixes

• allow parentheses around calls in arrow bodies and ternary branches (ad6746d)

@trigen/stylelint-config

11.0.0 (2026-10-15)

Bug Fixes

• allow CSS Modules :global and :local pseudo-classes (64c4fef)

---

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