Skip to content

Document the LiterateCS runtime workaround - #126

Merged
belgaard merged 1 commit into
masterfrom
document-literatecs-runtime-note
Aug 29, 2026
Merged

belgaard merged 1 commit into
masterfrom
document-literatecs-runtime-note

Conversation

@belgaard

Copy link
Copy Markdown
Owner

Adds a section to RELEASE.md covering docs/ regeneration: LiterateCS 2.0.46 targets .NET 6.0, so it needs DOTNET_ROLL_FORWARD=LatestMajor to run on a machine that only has newer SDKs installed. Also notes not to pass -u/--updatetoc, which overwrites the hand-curated TOC.yml with every discovered source file.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The change is documentation-only, consistent with the repository’s existing LiterateCS configuration, and does not introduce functional or operational risk.

Pull request overview

This PR documents how to regenerate the repository’s docs/ GitHub Pages output using LiterateCS, including a runtime roll-forward workaround and a caution about avoiding automatic TOC regeneration.

Changes:

  • Add a “Regenerating docs/” section to RELEASE.md.
  • Document setting DOTNET_ROLL_FORWARD=LatestMajor for running LiterateCS targeting .NET 6 on newer runtimes.
  • Warn against using -u/--updatetoc to avoid overwriting the curated TOC.yml.
File summaries
File Description
RELEASE.md Adds release-process documentation for regenerating docs/ with LiterateCS, including environment/workflow caveats.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@belgaard
belgaard merged commit 276f561 into master Aug 29, 2026
2 checks passed
@belgaard
belgaard deleted the document-literatecs-runtime-note branch August 29, 2026 16:08
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