Deploy release notes 26.06

[validbeck]

Pull Request Description

What and why?

• docs: Models > Records — Reporting, Monitoring, Attestation #1359
• Preview for 26.06 release notes + make get-source #1353

How to test

What needs special review?

Dependencies, breaking changes, and deployment notes

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)
• Environment variable additions/changes documented (if required)

[github-actions]

PR Summary

This PR introduces two significant changes:

1. GitHub Workflow Enhancements:

   • Updated the deployment scripts in the GitHub Actions workflows to add a cache-control header (no-cache, max-age=0, must-revalidate) to the AWS S3 sync commands. This will ensure that stale content is not served and forces clients to retrieve the latest versions after deployment.
   • Minor changes to AWS endpoint configuration in one of the notebooks have been updated from a localhost URL to a production URL, which helps in connecting to the correct API endpoint.

2. Documentation and Terminology Updates:

   • Several markdown files and guide documents have been modified to replace generic "model" terminology with "record" (or a combination of "record (model)") where appropriate. This includes attestation guides, monitoring documents, reporting templates, training modules, and other learning resources.
   • The changes improve clarity and consistency across the documentation, ensuring that references to inventory, artifacts, attestations, and workflows correctly reflect the underlying model/record data.
   • Text for UI elements (e.g., register model pages, inventory fields) is updated to match this revised terminology.

Overall, the PR enhances the caching behavior during production deployment and aligns the documentation with updated business terminology, which should reduce potential confusion for users.

Test Suggestions

• Run the GitHub workflows in a staging environment to verify that the cache-control header is applied in the S3 sync commands and that CloudFront invalidation is triggered properly.
• Manually test deployment of documentation to ensure that excluded directories are still correctly omitted and that no caching issues occur in browsers.
• Review several pages of the attestation, monitoring, and reporting guides to ensure that all instances of the outdated terminology are updated consistently.
• Test notebooks that initialize API connections by confirming they now point to the production endpoint and use the updated credential placeholders.

[github-actions]

Validate docs site

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