Files
awesome-kubernetes/.github/workflows/06.deploy_final.yml
Nubenetes Bot 1dd0dab308 fix: 3 critical publisher/deploy safety issues
1. Skip page deletion and nav sync in --render-only mode
   The CI publisher always uses --render-only but the pruning phase was
   deleting pages not regenerated in a given pass (e.g. low-hit pages),
   breaking nav references and corrupting the MkDocs build.

2. Protect dimension pages from deletion in full mode
   Even in a full (non-render-only) run, pages defined in self.dimensions
   are never deleted. Truly orphaned pages (not in dimensions AND not
   generated) are the only ones pruned.

3. _sync_enterprise_navigation returns True/False
   Deletion is gated on nav sync success. If nav sync fails, deletion
   is skipped to prevent inconsistency (deleted files + stale nav).
   Also fixes the fragile re.sub(r'nav:.*') regex by using string
   indexing instead, preventing accidental truncation of extra_css etc.

4. Deploy workflow V2 sanity check
   If V2 build produces fewer than 50 HTML pages or no index.html,
   deploy falls back to V1-only instead of overwriting V1 with a
   broken V2 build.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-19 13:29:10 +02:00

93 lines
2.7 KiB
YAML

name: 06.1. Final Portal Deploy
on:
push:
branches:
- master
workflow_dispatch: {}
# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
permissions:
contents: write
pages: write
id-token: write
# Allow only one concurrent deployment
concurrency:
group: "pages-stable"
cancel-in-progress: false
jobs:
build:
name: Build Dual Versions
runs-on: ubuntu-latest
steps:
- name: Checkout master
uses: actions/checkout@v6
with:
submodules: true
- name: Setup Python
uses: actions/setup-python@v6
with:
python-version: '3.11'
cache: 'pip'
- name: Install dependencies
run: |
pip install mkdocs-material mkdocs-redirects mkdocs-minify-plugin pymdown-extensions
pip install -r requirements.txt
# 1. Build V1 to temporary staging area
- name: Build V1 Edition (Staging)
run: mkdocs build -f mkdocs.yml -d site_v1/
# 2. Build V2 Elite Edition (Staging)
- name: Build V2 Elite Edition (Staging)
run: mkdocs build -f v2-mkdocs.yml -d site_v2/
# 3. Assemble Final Site (V2 at Root with V1 Fallback, V1 Archive at /v1/)
- name: Assemble Final Site
run: |
mkdir -p site/
# Safety check: V2 must have a valid index.html and at least 50 pages
V2_PAGE_COUNT=$(find site_v2/ -name "*.html" | wc -l)
if [ "$V2_PAGE_COUNT" -lt 50 ] || [ ! -f site_v2/index.html ]; then
echo "❌ V2 build looks broken (only $V2_PAGE_COUNT HTML pages). Deploying V1 only to protect the site."
cp -r site_v1/* site/
mkdir -p site/v1/
cp -r site_v1/* site/v1/
rm -rf site_v1/ site_v2/
exit 0
fi
echo "✅ V2 build OK ($V2_PAGE_COUNT pages). Assembling dual-version site."
# Copy V1 to root as fallback for any pages not present in V2
cp -r site_v1/* site/
# Overwrite root with V2 Elite Portal (matching pages will be V2 versions)
cp -r site_v2/* site/
# Deploy full V1 Archive to subdirectory /v1/
mkdir -p site/v1/
cp -r site_v1/* site/v1/
rm -rf site_v1/ site_v2/
- name: Setup Pages
uses: actions/configure-pages@v6
- name: Upload artifact
uses: actions/upload-pages-artifact@v5
with:
path: './site'
deploy:
name: Deploy to GitHub Pages
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
runs-on: ubuntu-latest
needs: build
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v5