[chrisjsewell]

Release sphinx-design 0.8.0.

• sphinx_design/__init__.py: __version__ = "0.8.0" (the only place the version is kept; pyproject.toml reads it dynamically).
• CHANGELOG.md: the 0.8.0 entry, written from the 48 PRs merged since v0.7.0, replacing the ## Unreleased section; the 0.7.0 heading date is fixed (2025-01-19 to 2026-01-19).

The entry is dated 2026-11-10: re-date to the tag day if this merges later.

Checks run on this branch

• pytest: 441 passed, 1 skipped (Python 3.13, Sphinx 9.2.0, docutils 0.22.4, myst-parser 5.1.0); the same against MyST-Parser master with docutils 0.23; 441 passed, 1 skipped on Sphinx 7.2.6 (the declared floor, which the CI matrix does not test); testing-no-myst: 317 passed, 125 skipped.
• pre-commit run --all-files: clean.
• sphinx-build -nW --keep-going for html and man: clean; latex: clean apart from the missing local ImageMagick, which CI installs.
• python -m build and twine check --strict dist/*: passed; the build job's tag guard, run locally with GITHUB_REF_NAME=v0.8.0, matches the built 0.8.0 wheel and sdist.

Release checklist

• The PyPI trusted publisher for sphinx-design is registered for executablebooks/sphinx-design, workflow ci.yml, environment pypi (confirmed 2026-11-09).
  The pypi environment exists: gh api repos/executablebooks/sphinx-design/environments shows pypi with one protection rule, a custom deployment policy v* (type tag), and no required reviewer (add one if you want an approval click per release).
• Re-date the ## 0.8.0 - 2026-11-10 heading to the tag day if this merges on a later day.
• Squash-merge with the title and message below, then tag the squash commit: git tag v0.8.0 <sha> && git push origin v0.8.0.
• The publish job is green (the build job's tag guard checks v0.8.0 against the built wheel and sdist). If it fails, fix the configuration and re-run the job; never re-tag.
• Provenance returns 200: https://pypi.org/integrity/sphinx-design/0.8.0/sphinx_design-0.8.0-py3-none-any.whl/provenance (this is the first trusted-publishing upload).
• Then revoke the old PyPI token and delete the PYPI_KEY secret (no longer referenced by ci.yml).
• Draft the GitHub Release for v0.8.0 from this changelog section.
• Read the Docs builds the tag, and stable moves to 0.8.0 (stable is already active).
• conda-forge (conda-forge/sphinx-design-feedstock): run dep sphinx >=7,<10 becomes sphinx >=7.2,<10; host flit-core >=3.4,<4 becomes <5; the test requirements gain tinycss2 and rcssmin (now in the testing extra) and pytest may widen to <10.
• Post-release follow-ups: refresh the five theme demo branches (git_rebase_theme_branches.sh); update the roadmap issue 🧭 Roadmap: backlog triage, modernization, card syntax redesign & new components #265; add a "Releasing" section to AGENTS.md and reword its "Update CHANGELOG.md" line to say the changelog is written at release.

Squash commit

Title: 🚀 RELEASE: v0.8.0 (#317)

Bump the version to 0.8.0 and write the 0.8.0 changelog entry from the PRs merged since v0.7.0,
replacing the Unreleased section. Fix the 0.7.0 heading date (2025-01-19 to 2026-01-19).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.01%. Comparing base (cb9828f) to head (2484a7a).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #317   +/-   ##
=======================================
  Coverage   94.01%   94.01%           
=======================================
  Files          16       16           
  Lines        1787     1787           
=======================================
  Hits         1680     1680           
  Misses        107      107           

Flag	Coverage Δ
pytests	94.01% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.