docs: update RELEASING.md for custom version format

Clarify that Release-As: should be used to specify versions
due to the custom version format (X.Y.Z-alpha.N.P).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>

Author: dbrattli

RELEASING.md

@@ -2,63 +2,62 @@
 
 This document describes the release process for Fable.Python and how to keep versions in sync with Fable.
 
-## Version Synchronization with Fable
+## Version Format
 
-Fable.Python versions should stay in sync with Fable. For example, if Fable releases `5.0.0-alpha.21`, Fable.Python should release `5.0.0-alpha.21.0`.
+Fable.Python uses the version format `X.Y.Z-alpha.N.P` where:
 
-## Release Process
-
-This project uses [release-please](https://github.com/googleapis/release-please) to automate releases. Release-please creates and maintains a release PR that updates automatically as commits are merged to main.
+- `X.Y.Z-alpha.N` matches the Fable version (e.g., `5.0.0-alpha.21`)
+- `P` is the patch version for Fable.Python releases (0, 1, 2, etc.)
 
-The configuration uses `"versioning": "always-bump-patch"` which means every release only increments the patch version (e.g., `5.0.0-alpha.21.0` → `5.0.0-alpha.21.1` → `5.0.0-alpha.21.2`).
+Example: `5.0.0-alpha.21.0`, `5.0.0-alpha.21.1`, `5.0.0-alpha.21.2`
 
-### Standard Release (Patch Bump)
-
-For normal bug fixes and improvements:
+## Release Process
 
-1. Merge PRs with conventional commit messages (`fix:`, `feat:`, `chore:`, etc.)
-2. Release-please automatically creates/updates a release PR
-3. Merge the release-please PR when ready
-4. The GitHub Action will create a release and tag
+This project uses [release-please](https://github.com/googleapis/release-please) to automate releases. Release-please creates and maintains a release PR that updates automatically as commits are merged to main.
 
-The patch version increments automatically regardless of commit type.
+**Important:** Due to the custom version format, use `Release-As:` to specify the version.
 
-### Syncing with a New Fable Version
+### Setting the Version
 
-When Fable releases a new version (e.g., `5.0.0-alpha.21`), use the `Release-As` footer to override the version:
+Add `Release-As:` in the commit message or PR description:
 
 #### In the commit message
 
 ```text
-chore: sync with Fable 5.0.0-alpha.21
+feat: add new feature
 
-Release-As: 5.0.0-alpha.21.0
+Release-As: 5.0.0-alpha.21.1
 ```
 
 #### In the PR description
 
 Add this line anywhere in the PR body:
 
 ```text
-Release-As: 5.0.0-alpha.21.0
+Release-As: 5.0.0-alpha.21.1
 ```
 
-Release-please will use the specified version instead of bumping the patch.
+Release-please will use the specified version for the release.
 
-### Hotfix Releases
+### Syncing with a New Fable Version
 
-After syncing with a Fable version, subsequent patches are automatic:
+When Fable releases a new version (e.g., `5.0.0-alpha.22`):
 
-- `5.0.0-alpha.21.0` (initial sync with Fable)
-- `5.0.0-alpha.21.1` (first hotfix)
-- `5.0.0-alpha.21.2` (second hotfix)
-- etc.
+1. Update the codebase to work with the new Fable version
+2. Use `Release-As: 5.0.0-alpha.22.0` in the commit or PR
+3. Merge the release-please PR
 
-This clearly shows the relationship to the base Fable version and sorts correctly in package managers.
+### Version History Example
+
+- `5.0.0-alpha.21.0` (initial sync with Fable 5.0.0-alpha.21)
+- `5.0.0-alpha.21.1` (first patch)
+- `5.0.0-alpha.21.2` (second patch)
+- `5.0.0-alpha.22.0` (sync with Fable 5.0.0-alpha.22)
+- `5.0.0-alpha.22.1` (first patch for alpha.22)
 
 ## Configuration Files
 
-- `release-please-config.json` - Release-please configuration (release type, versioning strategy)
+- `release-please-config.json` - Release-please configuration (release type, tag format)
 - `.release-please-manifest.json` - Tracks the current released version
 
 ## Conventional Commits
@@ -68,5 +67,3 @@ This project uses [conventional commits](https://www.conventionalcommits.org/):
 - `feat:` - New features
 - `fix:` - Bug fixes
 - `chore:`, `docs:`, `style:`, `refactor:`, `test:` - Other changes
-
-With `"versioning": "always-bump-patch"`, all commit types result in a patch bump only.