Skip to content

[Feature]: Automate Fern version registration on release tags with N-3 pruning #1291

Description

@pdmack

Prerequisites

  • I searched existing issues

Feature Description

Port the AICR publish workflow pattern (NVIDIA/aicr#940) to NVSentinel:

  • Trigger on release tags (v[0-9]*.[0-9]*.[0-9]*) instead of separate docs/v* tags
  • workflow_dispatch with optional tag input for manual re-publishes
  • Semver validation and tag existence checks
  • Auto-register version entries in the Fern dropdown via yq
  • Prune to Latest + 3 most recent versions (MAX_VERSIONS env var)
  • Pre-release tags (e.g. v1.6.0-rc1) trigger publish but skip registration
  • PR-based persistence: version registry changes go through normal review (after publish)
  • Pre-stamp backup so transient "Latest · vX.Y.Z" isn't persisted in the PR
  • Full MDX sanitization in frozen version checkout (escape { } <)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions