Update versions 0 33 0

[alexandreLamarre]

Summary

Related

AI disclosure

Checklist

• reference any related issues
• disclosed AI usage (or wrote "none") per AI_POLICY.md

[netlify]

✅ Deploy Preview for pomerium-docs ready!

Name	Link
🔨 Latest commit	83dfd4d
🔍 Latest deploy log	https://app.netlify.com/projects/pomerium-docs/deploys/6a5a98225376b8000888d5db
😎 Deploy Preview	https://deploy-preview-2324--pomerium-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[greptile-apps]

Greptile Summary

This PR cuts the 0-33-0 release branch by pinning Kubernetes/Docker artifact references from main to v0.33.0 and updating the Docusaurus version label to v0.33. All image and kustomize-ref bumps are internally consistent.

• Enterprise console image (pomerium-console) is bumped from v0.32.0 → v0.33.0 in both the Docker Compose example and the Kubernetes Deployment manifest.
• Ingress Controller kustomize ?ref= values are pinned from main → v0.33.0 in sync-api.mdx, k8s/core/kustomization.yaml, and the Enterprise kubectl apply -k example.
• The Docusaurus versions.current.label is correctly set to v0.33 on this release branch — but the navbar dropdownItemsAfter and src/components/docVersions.json were not updated, leaving v0.32 advertised as "Latest stable" to visitors of this branch's docs site.

Confidence Score: 4/5

Safe to merge — all version-pinning changes are correct and consistent; the only gaps are two metadata files that control the docs-site version dropdown display.

The image tags and kustomize refs are all correctly bumped to v0.33.0, and the Docusaurus label is properly set to v0.33. The two outstanding gaps — dropdownItemsAfter in docusaurus.config.ts and src/components/docVersions.json — leave visitors to the branch's docs site seeing 'Latest stable (v0.32)' in the version selector even though they are browsing v0.33 content. These are non-breaking but visible to end users and are explicitly required by the repo's release-cut checklist in AGENTS.md.

docusaurus.config.ts (navbar dropdown) and src/components/docVersions.json both need the 'Latest stable' label updated to v0.33 and the v0.32 entry demoted.

Important Files Changed

Filename	Overview
docusaurus.config.ts	Version label correctly updated to 'v0.33', but the navbar dropdown dropdownItemsAfter still advertises v0.32 as 'Latest stable' — this backport step is required by the AGENTS.md release process.
content/docs/deploy/k8s/sync-api.mdx	Ingress Controller kustomize refs correctly pinned from main to v0.33.0 in both the Zero and Enterprise examples.
content/examples/enterprise/hosted-auth-docker.yaml.md	Enterprise console Docker image correctly bumped from v0.32.0 to v0.33.0.
k8s/console/deployment/image.yaml	Enterprise console Kubernetes image tag correctly bumped from v0.32.0 to v0.33.0.
k8s/core/kustomization.yaml	Ingress Controller kustomize ref correctly pinned from main to v0.33.0.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[main branch] -->|cut release branch| B[0-33-0 branch]
    B --> C[docusaurus.config.ts\nlabel: v0.33 ✅]
    B --> D[k8s/core/kustomization.yaml\nref=v0.33.0 ✅]
    B --> E[k8s/console/deployment/image.yaml\npomerium-console:v0.33.0 ✅]
    B --> F[content/examples/.../hosted-auth-docker.yaml.md\npomerium-console:v0.33.0 ✅]
    B --> G[content/docs/deploy/k8s/sync-api.mdx\nref=v0.33.0 ✅]
    B --> H[docusaurus.config.ts dropdownItemsAfter\nstill shows Latest stable v0.32 ⚠️]
    B --> I[src/components/docVersions.json\nmissing 0.33.0 entry ⚠️]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[main branch] -->|cut release branch| B[0-33-0 branch]
    B --> C[docusaurus.config.ts\nlabel: v0.33 ✅]
    B --> D[k8s/core/kustomization.yaml\nref=v0.33.0 ✅]
    B --> E[k8s/console/deployment/image.yaml\npomerium-console:v0.33.0 ✅]
    B --> F[content/examples/.../hosted-auth-docker.yaml.md\npomerium-console:v0.33.0 ✅]
    B --> G[content/docs/deploy/k8s/sync-api.mdx\nref=v0.33.0 ✅]
    B --> H[docusaurus.config.ts dropdownItemsAfter\nstill shows Latest stable v0.32 ⚠️]
    B --> I[src/components/docVersions.json\nmissing 0.33.0 entry ⚠️]

Loading

Comments Outside Diff (2)

1. docusaurus.config.ts, line 176-193 (link)

   Navbar dropdown still advertises v0.32 as "Latest stable"

   The dropdownItemsAfter array was not updated as part of this release cut. Per AGENTS.md step 3, the navbar dropdown should be updated on main and then backported to all still-live pinned branches — including this 0-33-0 branch. A visitor landing on 0-33-0.docs.pomerium.com will see their current page labelled v0.33 at the top of the dropdown, but the first pinned link below it will still read "Latest stable (v0.32)", which is now stale and contradictory.

   Red-test proof:

   # Expected state after a correct 0-33-0 branch cut:
   expected_latest = "Latest stable (v0.33)"
   actual_latest = "Latest stable (v0.32)"   # what the dropdown shows today
   
   assert actual_latest == expected_latest, (
       f"Dropdown still advertises '{actual_latest}' on the v0.33 branch "
       f"— expected '{expected_latest}'"
   )
   # AssertionError: Dropdown still advertises 'Latest stable (v0.32)' on the v0.33 branch
   #                 — expected 'Latest stable (v0.33)'

   Context Used: AGENTS.md (source)

   Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

   

2. docusaurus.config.ts, line 176-193 (link)

   src/components/docVersions.json not updated for v0.33

   src/components/docVersions.json still lists 0.32.0 under "id": "Latest stable (v0.32)" and has no 0.33.0 entry at all. AGENTS.md step 3 requires both this file and the navbar dropdown to be kept in sync. Any UI component that reads docVersions.json will continue to surface v0.32 as the current latest stable after this branch is deployed.

   Red-test proof:

   import json
   
   with open("src/components/docVersions.json") as f:
       versions = json.load(f)
   
   assert "0.33.0" in versions, "0.33.0 missing from docVersions.json"
   # AssertionError: 0.33.0 missing from docVersions.json
   
   assert versions["0.32.0"]["id"] != "Latest stable (v0.32)", (
       "0.32.0 is still labelled 'Latest stable' — should be demoted to 'v0.32'"
   )
   # AssertionError: 0.32.0 is still labelled 'Latest stable'

   Context Used: AGENTS.md (source)

   

_{Reviews (1): Last reviewed commit: "update refs to v0.33.0" | Re-trigger Greptile}