release: v0.11.0 — grammar refactor + structural refactor + 8 fixes #67

2026-04-21T10:16:31+02:00

umpire274 commented

2026-04-21 10:16:31 +02:00

(Migrated from github.com)

Promotes v0.11.0-alpha2 plus the fixes landed on
v0.11.0-alpha2-fix_codex (issues #55, #56, #59, #60, #61, #62, #64, the last green fix commit and this release — this commit updates version metadata and documentation only.

Version metadata:

Cargo.toml: 0.11.0-alpha2 → 0.11.0
Cargo.lock: bs_scoring entry 0.11.0-alpha2 → 0.11.0

Documentation:

CHANGELOG.md: new v0.11.0 entry at the top aggregating alpha1 + alpha2 + fixes, preserving the earlier per-release entries as history.
README.md: header bumped; "What's New in v0.11.0" rewritten to describe the milestone as a consolidated whole instead of listing the alphas separately; new v0.11.0 row at the top of Recent Versions and Features-by-Version; Scorer Commands wording updated; footer bumped.
SCORING_GUIDE.md: header and section 14 bumped, removed reference to v0.11.0-alpha2 as the anchor version.
STRUCTURE.md: header, "introduced in v0.11.0:" wording, and the "Command pipeline (v0.11.0)" subsection title all bumped.
RELEASE.md: every example (git tag, git push, GitHub Release URL, etc.) now targets v0.11.0; footer updated to "Current 0.11.0 / Previous 0.11.0-alpha2"; version-bumping checklist reworded for future stable releases.

Promotes v0.11.0-alpha2 plus the fixes landed on v0.11.0-alpha2-fix_codex (issues #55, #56, #59, #60, #61, #62, #64, the last green fix commit and this release — this commit updates version metadata and documentation only. Version metadata: - Cargo.toml: 0.11.0-alpha2 → 0.11.0 - Cargo.lock: bs_scoring entry 0.11.0-alpha2 → 0.11.0 Documentation: - CHANGELOG.md: new v0.11.0 entry at the top aggregating alpha1 + alpha2 + fixes, preserving the earlier per-release entries as history. - README.md: header bumped; "What's New in v0.11.0" rewritten to describe the milestone as a consolidated whole instead of listing the alphas separately; new v0.11.0 row at the top of Recent Versions and Features-by-Version; Scorer Commands wording updated; footer bumped. - SCORING_GUIDE.md: header and section 14 bumped, removed reference to v0.11.0-alpha2 as the anchor version. - STRUCTURE.md: header, "introduced in v0.11.0:" wording, and the "Command pipeline (v0.11.0)" subsection title all bumped. - RELEASE.md: every example (`git tag`, `git push`, GitHub Release URL, etc.) now targets v0.11.0; footer updated to "Current 0.11.0 / Previous 0.11.0-alpha2"; version-bumping checklist reworded for future stable releases.

chatgpt-codex-connector[bot] (Migrated from github.com) reviewed

2026-04-21 10:17:48 +02:00

chatgpt-codex-connector[bot] (Migrated from github.com) left a comment

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dc0f16b962

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

### 💡 Codex Review Here are some automated review suggestions for this pull request. **Reviewed commit:** `dc0f16b962` <details> <summary>ℹ️ About Codex in GitHub</summary> [Your team has set up Codex to review pull requests in this repo](https://chatgpt.com/codex/cloud/settings/general). Reviews are triggered when you - Open a pull request for review - Mark a draft as ready - Comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". </details>

Cargo.toml

					
				@ -2,3 +2,3 @@

				name = "bs_scoring"

				version = "0.11.0-alpha2"

				version = "0.11.0"

				edition = "2024"

Update lockfile after version bump

Changing Cargo.toml to 0.11.0 without updating Cargo.lock leaves the workspace in an unreproducible state: the root package entry in Cargo.lock is still 0.11.0-alpha2, and cargo check --locked fails with “the lock file needs to be updated.” This will break any CI/release workflow that enforces --locked, so the lockfile should be regenerated and committed alongside this version change.

Useful? React with 👍 / 👎.

**![P1 Badge](https://img.shields.io/badge/P1-orange?style=flat) Update lockfile after version bump** Changing `Cargo.toml` to `0.11.0` without updating `Cargo.lock` leaves the workspace in an unreproducible state: the root package entry in `Cargo.lock` is still `0.11.0-alpha2`, and `cargo check --locked` fails with “the lock file needs to be updated.” This will break any CI/release workflow that enforces `--locked`, so the lockfile should be regenerated and committed alongside this version change. Useful? React with 👍 / 👎.

Sign in to join this conversation.

No reviewers