Skip to content

Align documentation with current release state - #50

Merged
jbeda merged 1 commit into
mainfrom
docs/release-readiness
Sep 24, 2026
Merged

jbeda merged 1 commit into
mainfrom
docs/release-readiness

Conversation

@jbeda

@jbeda jbeda commented Sep 24, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add a project-adapted technical-writing skill with recorded provenance
  • audit and align public documentation with current lint, imports, vendoring, Action, and local-development behavior
  • add Action documentation updates to the post-release checklist

Validation

  • task check
  • cd website && npm run typecheck && npm run build

Review

Docs-only independent editorial review found two minor issues. Both were fixed and the delta review was clean.

Known boundary

This does not resolve #41. Production documentation still represents main while the released Action default remains v0.4.0; the guides now state that feature-availability boundary accurately.

@jbeda
jbeda marked this pull request as ready for review September 24, 2026 04:51
@jbeda
jbeda force-pushed the docs/release-readiness branch 3 times, most recently from 523b6e6 to 669c970 Compare September 24, 2026 06:49
Signed-off-by: Joe Beda <joe@stacklok.com>
@jbeda
jbeda force-pushed the docs/release-readiness branch from 669c970 to e83bfe1 Compare September 24, 2026 15:19
@jbeda
jbeda merged commit 3fe96d7 into main Sep 24, 2026
2 checks passed
@jbeda
jbeda deleted the docs/release-readiness branch September 24, 2026 15:26
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.

Docs: modelith.sh publishes from main, so it documents features no release has

1 participant