Repository navigation

chore: update nustreamdocs #1144

	name: Build website

	on:
	push:
	branches: [ main ]
	pull_request:
	branches: [ main ]

	# Build verification only. No secrets are referenced here, so PRs from
	# forks cannot exfiltrate deploy credentials via this workflow. Deploys
	# live in deploy.yml, which is gated to trusted triggers (push to main,
	# schedule, workflow_dispatch).
	permissions:
	contents: read

	jobs:
	build:
	runs-on: ubuntu-latest
	steps:
	- name: Checkout
	uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
	with:
	fetch-depth: 0

	- name: Setup .NET
	uses: actions/setup-dotnet@a98b56852c35b8e3190ac28c8c2271da59106c68 # v6
	with:
	dotnet-version: 10.0.x

	- name: Cache fetched packages
	uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6
	with:
	path: \|
	~/.nuget/packages
	.api-cache
	build/_intermediate
	# ~/.nuget/packages: NuGet hydration cache.
	# .api-cache: fetched NuGet assemblies + their extracted lib/refs
	# trees (read by the API-doc fetcher).
	# build/_intermediate: regenerated API markdown / yml / metadata
	# configs — derived from .api-cache so they share an invalidation key.
	# Bust on any package-list or NuStreamDocs version move.
	key: ${{ runner.os }}-website-${{ hashFiles('nuget-packages.json', 'build/_build.csproj', 'Directory.Packages.props') }}

	- name: Build website
	run: ./build.sh build