Skip to content

chore: regenerate soc-optimization-unified docs for v3.10.1#918

Merged
scottbrumley merged 1 commit into
mainfrom
chore/regen-soc-opt-docs
May 27, 2026
Merged

chore: regenerate soc-optimization-unified docs for v3.10.1#918
scottbrumley merged 1 commit into
mainfrom
chore/regen-soc-opt-docs

Conversation

@scottbrumley
Copy link
Copy Markdown
Contributor

What does this content do?

Docs-only post-release catchup. After soc-optimization-unified was bumped to v3.10.1 by #916's auto-bump (commit 14469da — "per-(lifecycle, category) dedup wiring"), the on-main pack_metadata and pack_catalog.json show 3.10.1 but docs/soc-optimization-unified/overview.md still rendered 3.10.0. This regen syncs the overview.

Content type

  • Docs only (regenerated via tools/prep_docs.py)

Target pack

N/A — change is in the repo-level docs/. The doc describes soc-optimization-unified but the pack itself is not modified.

What changed

  • docs/soc-optimization-unified/overview.md: Version field 3.10.03.10.1, release URL likewise.
  • Nothing under Packs/ — so the post-merge release pipeline correctly skips bump/build/catalog for this PR.

Why now

Blocking check_contribution's prep_docs --check gate on every subsequent local validation — same pattern as #917 for nist-ir. Tiny PR to clear it before the soc-opt .py PR.

Post-release docs catchup. `soc-optimization-unified` was bumped from
v3.10.0 → v3.10.1 by the #916 auto-bump (commit 14469da, per-(lifecycle,
category) dedup wiring), but `docs/soc-optimization-unified/overview.md`
on main wasn't regenerated. This regen syncs the overview to the on-main
pack_metadata / pack_catalog (3.10.1). Docs-only — no pack content changed.

Labels: version:patch
@scottbrumley scottbrumley merged commit cd48e4c into main May 27, 2026
14 checks passed
@scottbrumley scottbrumley deleted the chore/regen-soc-opt-docs branch May 27, 2026 20:46
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.

2 participants