Skip to content

Release develop docs updates to main - #238

Merged
ihsraham merged 12 commits into
mainfrom
develop
Aug 18, 2026
Merged

Release develop docs updates to main#238
ihsraham merged 12 commits into
mainfrom
develop

Conversation

@ihsraham

@ihsraham ihsraham commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Summary

Promote the current develop documentation set to main.

Deliverables going to main

  • #233: Document August WDK releases
    • Documents seven August WDK releases and updates the affected API, configuration, lifecycle, and transaction guidance.
    • Retires the duplicate All Modules and Community Modules pages, redirects them to Building Blocks, and preserves the downstream feed and LLM contracts.
  • #235: Refresh documentation dependencies
    • Updates Next.js, Mermaid, PostCSS, Sharp, DOMPurify, fast-uri, and Nano ID.
    • Regenerates the npm 10 lockfile, preserves nested Zod 3.25.76, and declares npm 10.9.7 for automated updates.
    • Supersedes #225, #226, #227, #231, #232, and #234.
  • #217: Document 0x Swidge module
    • Adds install, usage, configuration, API, runtime, and safety guidance for @0x/wdk-protocol-swidge-0x@0.1.0.
    • Integrates the module into navigation, catalogs, changelog, search, and LLM artifacts.
  • #240: Improve agent-readable documentation output
    • Adds a structured llms.txt with direct Markdown links and serializes article content before repeated navigation.
    • Enforces exact HTML/Markdown/llms.txt route parity and article-first source order while preserving accessible desktop and mobile navigation.

Validation

  • Current develop head 6d74f19 passed Quality Gates.
  • A merge-tree simulation completed without conflicts.
  • Promotion PR quality and security checks remain required before merge.

Follow-up

@socket-security

socket-security Bot commented Aug 17, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednext@​16.2.12 ⏵ 16.3.061 -210090 +19970
Updatedpostcss@​8.5.18 ⏵ 8.5.26100 +1100 +282 +194100
Updatedkatex@​0.16.27 ⏵ 0.16.4792 +1100100 +198 +4100
Updatedmermaid@​11.15.0 ⏵ 11.16.198 +1100 +6100 +196100

View full report

@socket-security

socket-security Bot commented Aug 17, 2026

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn Medium
Dynamic code execution: npm @img/sharp-wasm32

Eval Type: Function

Location: Package overview

From: package-lock.jsonnpm/next@16.3.0npm/@img/sharp-wasm32@0.35.3

ℹ Read more on: This package | This alert | What is dynamic code execution?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@img/sharp-wasm32@0.35.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@kinsta

kinsta Bot commented Aug 18, 2026

Copy link
Copy Markdown

Preview deployments for wdk-docs prod ⚡️

Status Branch preview Commit preview
✅ Ready Visit preview Visit preview

Commit: b35f3e4c7e1a5ef23f59224441c059ff6dbd387a

Deployment ID: d8c9355d-2827-439a-89a6-3abf6c04532a

Static site name: wdk-docs-prod-pbpbt

@ihsraham
ihsraham merged commit e707434 into main Aug 18, 2026
7 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.

3 participants