Preview patch release notes: 26.07.04

[validbeck]

Pull Request Description

sc-17145

What and why?

Preview for Patch release notes: 26.07.04 (#104).

Warning

This PR automatically checks out the release notes branch automated/patch-26.07.04 in .github/workflows/validate-docs-site.yaml so the preview displays the in-progress release notes (temporary ref: — remove before merge).

Release type	Patch (CMVM hotfix)
Version	26.07.04
validate-docs-site.yaml (REVERT BEFORE MERGE)	Temporary ref: automated/patch-26.07.04 on Check out release-notes repository step

How to regenerate release notes preview

After updates are pushed to the linked release-notes PR: https://github.com/validmind/release-notes/pull/104

1. Open this PR in validmind/documentation
2. Re-run Validate docs site workflow (Actions tab → Validate docs site ... in the left sidebar → Select the latest workflow run linked to this PR → Re-run all jobs)

No commits on this branch are required — that workflow already checks out release-notes branch automated/patch-26.07.04 via the temporary ref: on the Check out release-notes repository step.

How to test

Click on the live documentation previews.

CMVM

• 26.07.04 Release notes

What needs special review?

Auto-generated. Complete What needs special review? on the linked release-notes PR — not here.

1. Verify that you can see release notes in the previews above as expected and that they render without any issues.
2. Work through the merge checklist below

Merge (documentation preview)

• Verify that you can see release notes in the previews as expected and that they render without any issues
• Only when you are satisfied with the release notes, merge the linked release-notes PR to main first
• On this branch, resolve the automated CHANGES_REQUESTED review by removing the ref: line from .github/workflows/validate-docs-site.yaml (keep repository: and path:)
• Confirm Validate docs site passes again on this PR
• Merge this PR to documentation / main after the release-notes PR merges sucessfully

Dependencies, breaking changes, and deployment notes

Release-notes PR (complete review there): Patch release notes: 26.07.04 (#104) — customer-facing .qmd content and full track checklist.

Release notes

n/a (internal label — customer-facing content is in validmind/release-notes)

Checklist

• What and why
• Screenshots or videos (Frontend)
• How to test
• What needs special review
• Dependencies, breaking changes, and deployment notes
• Labels applied
• PR linked to Shortcut
• Unit tests added (Backend)
• Tested locally
• Documentation updated (if required)

[github-actions]

REMOVE ref: TO release-notes BRANCH

Important

Remove the ref: line from the Check out release-notes repository workflow step in .github/workflows/validate-docs-site.yaml before merging — the temporary ref: must not land on documentation:main.

[github-actions]

Remove this ref: line to the working release-notes branch before merge. After the linked release-notes PR merges, workflow should check out release-notes:main. (view in .github/workflows/validate-docs-site.yaml)

Suggested change

ref: automated/patch-26.07.04

[github-actions]

PR Summary

This PR enhances the GitHub Actions workflow responsible for validating the documentation site by specifying a particular branch when checking out the release-notes repository. The added line ref: automated/patch-26.07.04 ensures that the action retrieves content from the intended branch, which may be critical for aligning the documentation with the corresponding release notes.

By pinning the reference, the workflow now reduces the risk of inconsistencies by avoiding unintended changes pulled from varying branches. This change supports the stability of the docs build process by ensuring consistency in the data used during the validation process.

Test Suggestions

• Run the workflow to verify that the checkout step correctly pulls content from the 'automated/patch-26.07.04' branch.
• Simulate a scenario where the specified branch does not exist to ensure that the workflow adequately handles errors.
• Check that subsequent steps relying on the release-notes content function as expected with the newly checked out version.

[github-actions]

Validate docs site

✓ INFO: A live preview of the docs site is available — Open the preview

[github-actions]

Lighthouse check results

✓ INFO: No site pages to audit in this PR.

Commit SHA: 1567a0e