ci(release): any non-fix merge releases the 0.x "major"

Requiring conventional feat:/fix: prefixes silently stopped every release
after v0.49.0 — the repo's de-facto commit style is bare area prefixes
("pdf: …", "wasm: …"), so bump_version.sh found nothing release-worthy in
~100 merged commits and every master merge ended in "nothing to release".

Invert the rule: a range whose commits are all fix:/perf:/revert: cuts a
patch; anything else bumps the middle number (0.49.0 -> 0.50.0). Docs/CI-
only merges still release nothing — release.sh's source-change gate already
requires a publishable crate's source in the diff. The automatic
semver-major path ("type!:" / BREAKING CHANGE) is gone entirely: v1.0.0 is
a hand-cut milestone via the force_version dispatch input, promised for the
repo's 100th GitHub star. release.sh's comments and skip messages are
re-worded to match, and CLAUDE.md documents the rule for future sessions
(prefix bug fixes fix(scope):, don't worry about the rest).

Merging this branch therefore auto-releases v0.50.0 with the whole backlog
since v0.49.0.

Signed-off-by: artiz <artem.kustikov@gmail.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EY5KAiquN4YpVf2PXEQkVT

Author: artiz

CLAUDE.md

@@ -8,6 +8,15 @@ validated for byte-for-byte conformance against upstream Python docling.
 
 - **Every commit must be signed off by the author.** End each commit message
   with `Signed-off-by: name <email>`.
+- **Releases are automatic on merge; only the `fix:` prefix matters.** CI
+  (`scripts/ci/bump_version.sh`): a merge whose commits are all
+  `fix:`/`perf:`/`revert:` cuts a patch (0.49.0 → 0.49.1); **any other
+  commit** — whatever its prefix — bumps the 0.x "major" (0.49.0 → 0.50.0).
+  So prefix bug fixes `fix(scope): …` and don't worry about the rest.
+  Docs/CI-only merges still release nothing (release.sh only fires when a
+  publishable crate's source changed). No automatic semver-major: v1.0.0 is
+  cut by hand (`force_version` dispatch input) when the repo hits its 100-star
+  milestone.
 - Claude Web: **Never open pull requests on `artiz/docling.rs`.** Push a `claude/<topic>`
   branch and hand back a compare link
   (`https://github.com/docling-project/docling.rs/compare/master...artiz:docling.rs:<branch>?expand=1`);

scripts/ci/bump_version.sh

@@ -1,13 +1,22 @@
 #!/usr/bin/env bash
 #
-# Decide the next workspace version from the conventional-commit messages since
-# the last release tag, and print it to stdout. Prints NOTHING (exit 0) when no
-# release-worthy commit is found, so the caller can skip the release.
+# Decide the next workspace version from the commit messages since the last
+# release tag, and print it to stdout. Prints NOTHING (exit 0) when the range
+# is empty, so the caller can skip the release.
 #
-#   <type>!: …  or  "BREAKING CHANGE" in the body  -> major
-#   feat: …                                        -> minor
-#   fix:/perf:/revert: …                           -> patch
-#   docs/chore/ci/refactor/test/style/build/…      -> no release
+#   only fix:/perf:/revert: commits in the range   -> patch
+#   anything else                                  -> minor (the 0.x "major")
+#
+# Releases deliberately do NOT depend on conventional-commit prefixes: the
+# repo's de-facto style is bare area prefixes ("pdf: …", "wasm: …"), and
+# requiring feat:/fix: silently stopped every release after v0.49.0. Any
+# non-fix merge now bumps 0.49 -> 0.50; a docs/CI-only merge still releases
+# nothing because release.sh's source-change gate sees no publishable crate
+# source in the diff.
+#
+# There is intentionally NO automatic semver-major: v1.0.0 is a milestone the
+# maintainer cuts by hand (FORCE_VERSION=1.0.0 via the CI dispatch input) —
+# "когда 100 звёзд дадут". Until then everything stays 0.x.
 #
 # Pure: reads git history + the root Cargo.toml; writes nothing.
 # Usage: scripts/ci/bump_version.sh
@@ -23,27 +32,20 @@ else
   range="HEAD" # no release tag yet: consider the whole history
 fi
 
-# Subject + body of every non-merge commit in range.
-log="$(git log "$range" --no-merges --format='%s%n%b')"
+# Subjects decide the bump.
+subjects="$(git log "$range" --no-merges --format='%s')"
 
 bump=""
-if grep -qE '^[a-z]+(\([^)]*\))?!:' <<<"$log" || grep -q 'BREAKING CHANGE' <<<"$log"; then
-  bump="major"
-elif grep -qE '^feat(\([^)]*\))?:' <<<"$log"; then
+if grep -vE '^(fix|perf|revert)(\([^)]*\))?:' <<<"$subjects" | grep -q '[^[:space:]]'; then
   bump="minor"
-elif grep -qE '^(fix|perf|revert)(\([^)]*\))?:' <<<"$log"; then
+elif grep -q '[^[:space:]]' <<<"$subjects"; then
   bump="patch"
 fi
 
 [[ -z "$bump" ]] && exit 0
 
 IFS=. read -r major minor patch <<<"$current"
 case "$bump" in
-major)
-  major=$((major + 1))
-  minor=0
-  patch=0
-  ;;
 minor)
   minor=$((minor + 1))
   patch=0

scripts/ci/release.sh

@@ -1,11 +1,13 @@
 #!/usr/bin/env bash
 #
 # Master-only release step (run by .github/workflows/ci.yml after the lint/test
-# gates pass). Computes the next version from conventional commits; if there is
-# one, it bumps the workspace version, commits + tags it, pushes to master,
-# publishes the changed crates, and assembles the GitHub Release notes (a commit
-# list since the previous tag) for the workflow to publish. A clean no-op when no
-# release-worthy commit landed since the last tag.
+# gates pass). Computes the next version from the commits since the last tag
+# (scripts/ci/bump_version.sh: fix:/perf:/revert:-only range -> patch, anything
+# else -> the 0.x "major"; no automatic 1.0.0); if there is one, it bumps the
+# workspace version, commits + tags it, pushes to master, publishes the changed
+# crates, and assembles the GitHub Release notes (a commit list since the
+# previous tag) for the workflow to publish. A clean no-op when nothing landed
+# since the last tag.
 #
 # The release commit is pushed with RELEASE_PAT (an admin token, so it satisfies
 # the master branch ruleset) and carries `[skip ci]`, so it does not re-trigger CI.
@@ -20,16 +22,17 @@ cd "$(dirname "$0")/../.."
 
 new="${FORCE_VERSION:-$(scripts/ci/bump_version.sh)}"
 if [[ -z "$new" ]]; then
-  echo "No release-worthy commits since the last tag — nothing to release."
+  echo "No commits since the last tag — nothing to release."
   exit 0
 fi
 [[ -n "${FORCE_VERSION:-}" ]] && echo ">> forced release of v$new"
 
-# A release-worthy *message* is not enough: only cut a new crates.io version when
-# a *publishable* crate's actual source changed since the last tag. This stops a
-# docs / CI / Python-binding-only change (e.g. `feat(docs): …`, `feat(docling-py): …`)
-# from minting and publishing a new version of every crate with no code change.
-# FORCE_VERSION bypasses the gate (a deliberate manual (re)publish).
+# Commits alone are not enough: only cut a new crates.io version when a
+# *publishable* crate's actual source changed since the last tag. This is what
+# stops a docs / CI / demo / Python-binding-only merge (now that every non-fix
+# commit is release-worthy) from minting and publishing a new version of every
+# crate with no code change. FORCE_VERSION bypasses the gate (a deliberate
+# manual (re)publish).
 if [[ -z "${FORCE_VERSION:-}" ]]; then
   gate_prev_tag="$(git tag --list 'v*' --sort=-version:refname | head -n1)"
   gate_range="${gate_prev_tag:+$gate_prev_tag..}HEAD"
@@ -42,7 +45,7 @@ if [[ -z "${FORCE_VERSION:-}" ]]; then
     gate_paths+=("crates/$c/src" "crates/$c/Cargo.toml" "crates/$c/build.rs")
   done
   if [[ -z "$(git diff --name-only "$gate_range" -- "${gate_paths[@]}")" ]]; then
-    echo "Release-worthy commit found, but no publishable crate source changed" \
+    echo "Commits since the last tag, but no publishable crate source changed" \
       "since ${gate_prev_tag:-the start of history} — skipping release."
     exit 0
   fi