Skip to content

docs: prepare beta 6.4.010 publication - #300

Merged
RensTillmann merged 2 commits into
gitbookfrom
docs/6.4.010-release-1a7e9ad8
Oct 21, 2026
Merged

RensTillmann merged 2 commits into
gitbookfrom
docs/6.4.010-release-1a7e9ad8

Conversation

@RensTillmann

@RensTillmann RensTillmann commented Oct 20, 2026 •

Copy link
Copy Markdown
Owner

Summary

gitbook-docs/
├── changelog-beta.md            # 6.4.010 release notes
├── downloads.md                 # beta release link
├── changelog.md                  # current beta index; channel intro without usage share
├── README.md                     # beta homepage version
└── developers/beta-version.md    # beta download version and accurate staging advice

Targets gitbook, because these are publication documentation changes only. Stable 6.3.323 pointers are unchanged. Neither Wordfence draft is modified.

Evidence

  • Before: the active beta pointers advertise 6.4.009.
    After: all five prepared surfaces consistently reference 6.4.010; the only remaining 6.4.009 occurrence in this worktree is its historical beta changelog entry.
  • Local Chromium documentation preview exercised at 1280, 390 and 320 CSS pixels: no horizontal overflow; all ten release-note items render. The actual GitBook revision was also exercised: home → beta instructions → beta changelog → Downloads → changelog index, preserving the revision context and stable 6.3.323 while showing beta 6.4.010. After the usage-share removal, the current revision's changelog shows the new intro with no usage share and no overflow at 390 px. Desktop and mobile screenshots are preserved locally. Canonical production is unchanged; future release/download targets were inspected, not claimed live or downloaded.
  • Removed the unverified assertion that this new beta was already tested by a small set of users; guidance now recommends backup, staging where possible and checking actual forms.
  • Removed the published Stable usage share ("~95% of users") from the changelog intro and tightened its wording. A search of every GitBook page found no other user, site or install share; remaining percentages describe product features or examples.
  • Corresponding source release is draft release: prepare 6.4.010 beta regression fixes #299. Full qualification evidence belongs to that source/artifact handoff, not an assumption from this documentation diff.

Merge Danger

Door: two-way

Keep draft until the owner approves the qualified ZIP and the beta release/downloads are live. Merge afterwards, then verify the public documentation and download targets. Reverting restores the prior beta pointers.

Blast Radius: documentation

Premature merge would advertise an unpublished version or stale download. This PR does not publish a plugin, change updater routing or send email.

@RensTillmann
RensTillmann marked this pull request as ready for review October 21, 2026 18:08
@RensTillmann
RensTillmann merged commit ad919f7 into gitbook Oct 21, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant