Skip to content

docs: add editorial summaries for Walrus release notes#3492

Open
reemsabawi-mystenlabs wants to merge 3 commits into
mainfrom
docs/editorial-release-note-summaries
Open

docs: add editorial summaries for Walrus release notes#3492
reemsabawi-mystenlabs wants to merge 3 commits into
mainfrom
docs/editorial-release-note-summaries

Conversation

@reemsabawi-mystenlabs

Copy link
Copy Markdown
Contributor

Description

Adds editorial-style summaries for the Walrus Platform release notes, one
markdown file per version under docs/editorial/ (66 versions, v1.10.0
through v1.50.0). Each file has title, description, and keywords
frontmatter, a network and date line, and a 1-2 sentence summary
highlighting the most important additions or fixes for that version. The
four versions with no user-facing notes are included with a short
maintenance-release summary.

Walrus Memory and Blog entries are not included in this PR and can be added
in a follow-up.

Test plan

Documentation-only change; no code affected. Verified locally that all 66
files were generated with valid frontmatter and that prose is style-compliant
(Testnet and Mainnet capitalized, no em dashes, no Latin abbreviations,
keywords present on every file). Rendered output should be confirmed in the
docs site preview.


Release notes

Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that
a user might notice and any actions they must take to implement updates. (Add release notes after the colon for each item)

  • Storage node:
  • Aggregator:
  • Publisher:
  • CLI:

reemsabawi-mystenlabs and others added 3 commits June 26, 2026 10:40
Add narrative, editorial companions to the release notes, one per
release-notes set (Walrus Platform, Walrus Memory MCP / TypeScript SDK /
Python SDK / OpenClaw, and Blog), plus an index README.

Style: no em or en dashes, keywords frontmatter on every file, Testnet and
Mainnet capitalized. Derived entirely from release-notes.mdx.
@github-actions

Copy link
Copy Markdown
Contributor
PR Preview Action v1.8.1

QR code for preview link

🚀 View preview at
https://MystenLabs.github.io/walrus/pr-preview/pr-3492/

Built to branch gh-pages at 2026-06-26 15:26 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

@github-actions

Copy link
Copy Markdown
Contributor

📋 afdocs check results

URL: https://MystenLabs.github.io/walrus/pr-preview/pr-3492/

Running checks on mystenlabs.github.io/walrus/pr-preview/pr-3492/...

Agent-Friendly Docs Check: https://MystenLabs.github.io/walrus/pr-preview/pr-3492/
Timestamp: 6/26/2026, 3:27:57 PM

content-discoverability
  ✗ llms-txt-exists: No llms.txt found at any candidate location (https://MystenLabs.github.io/walrus/pr-preview/pr-3492/llms.txt, https://mystenlabs.github.io/llms.txt, https://mystenlabs.github.io/docs/llms.txt)
      Learn more: https://agentdocsspec.com/spec/#llms-txt-exists
  ○ llms-txt-valid: Skipped: dependency check did not pass
  ○ llms-txt-size: Skipped: dependency check did not pass
  ○ llms-txt-links-resolve: Skipped: dependency check did not pass
  ○ llms-txt-links-markdown: Skipped: dependency check did not pass
  ✗ llms-txt-directive-html: Could not test any pages; 1 failed to fetch
      Learn more: https://agentdocsspec.com/spec/#llms-txt-directive-html
  ✗ llms-txt-directive-md: Could not fetch markdown for any of 1 pages; 1 had no markdown version
      Learn more: https://agentdocsspec.com/spec/#llms-txt-directive-md

markdown-availability
  ✗ markdown-url-support: No pages support .md URLs (0/1 tested)
      Learn more: https://agentdocsspec.com/spec/#markdown-url-support
  ✗ content-negotiation: Server ignores Accept: text/markdown header (0/1 pages return markdown)
      Learn more: https://agentdocsspec.com/spec/#content-negotiation

page-size
  ✓ rendering-strategy: All 1 pages contain server-rendered content
  ○ page-size-markdown: Skipped: dependency check did not pass
  ✓ page-size-html: All 1 pages under 50K chars (median 16K HTML → 916 markdown (94% boilerplate))
  ⚠ content-start-position: 1 of 1 pages have content starting at 10–50% (worst 49%)
      Learn more: https://agentdocsspec.com/spec/#content-start-position

content-structure
  ✓ tabbed-content-serialization: No tabbed content detected across 1 pages
  ✓ section-header-quality: No tabbed content found; header quality check not applicable
  ○ markdown-code-fence-validity: Site does not serve markdown content; nothing to analyze

url-stability
  ✓ http-status-codes: All 1 pages return proper error codes for bad URLs
  ✓ redirect-behavior: No redirects detected across 1 pages

observability
  ○ llms-txt-coverage: Skipped: dependency check did not pass
  ○ markdown-content-parity: Skipped: dependency check did not pass
  ✓ cache-header-hygiene: All 1 endpoints have appropriate cache headers

authentication
  ✓ auth-gate-detection: All 1 pages are publicly accessible
  ○ auth-alternative-access: All docs pages are publicly accessible; no alternative access paths needed

Summary
  8 passed, 1 warnings, 5 failed, 9 skipped (23 total)

Full spec: https://agentdocsspec.com/spec/

jessiemongeon1 added a commit that referenced this pull request Jun 26, 2026
Pull 59 editorial summary files from PR #3492 and integrate them
into the release notes generator. Each Walrus platform release now
shows a human-written editorial summary as a blockquote above the
raw GitHub release body.

Editorial files live in docs/editorial/walrus-v*.md with frontmatter
and a concise summary paragraph. The script matches them by version
number and prepends the summary (with the network/date line stripped
since it's already rendered by the script).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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