Expected Behavior

After a minor release, docs.feast.dev should default to documentation for the latest stable Feast version. The release process should create the maintenance branch and verify that the corresponding GitBook space is published and selected as the default.

Current Behavior

Feast 0.65.0 was released on July 20, 2026, but docs.feast.dev still defaults to v0.64-branch. The repository has no v0.65-branch, and the GitBook collection has no v0.65 space. The current release.yml workflow publishes the release and updates stable, but the maintenance branch and GitBook steps remain manual post-release tasks.

This report is intentionally about the durable release-process gap rather than only publishing v0.65. A newer release may supersede v0.65 before the issue is addressed, but the same failure can recur for every minor release.

Steps to reproduce

1. Open https://docs.feast.dev/ and inspect the selected documentation version.
2. Compare it with the latest release at https://github.com/feast-dev/feast/releases.
3. Inspect the upstream maintenance branches and GitBook version selector.

Specifications

• Latest stable release: v0.65.0
• Public documentation default: v0.64-branch
• Missing maintenance branch: v0.65-branch
• Subsystem: release automation and documentation publishing

Possible Solution

Extend the minor-release workflow to create the versioned maintenance branch automatically. Add a post-release check that confirms the matching GitBook space exists, is published, and is the default documentation version. If GitBook publication must remain manual, the workflow should fail or emit a clear actionable alert until those steps are complete.

The acceptance condition should be version-independent: the public documentation default matches the latest stable minor release after every release.