Prod deploy 2026 Jun 1

[validbeck]

Pull Request Description

What and why?

Pushing the folllowing PRs to prod:

• docs: New record/artifact details/fields editing & field highlighting #1357
• Fix VM API reference to use app.prod.validmind.ai #1360

How to test

Check the live preview when it posts and confirm the expected changes are in correctly.

What needs special review?

n/a

Dependencies, breaking changes, and deployment notes

na/

Release notes

n/a

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)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
2 out of 3 committers have signed the CLA.

✅ github-actions[bot]
✅ validbeck
❌ jamadriz
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
2 out of 3 committers have signed the CLA.

✅ validbeck
✅ github-actions[bot]
❌ jamadriz
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

PR Summary

This PR overhauls documentation and Makefile references concerning artifact management and inventory workflows. Key changes include:

1. API endpoint updates: The Makefile now fetches the VM API Swagger spec from a new base URL (changed from api.prod.validmind.ai to app.prod.validmind.ai). This ensures consistency with current production endpoints.

2. Documentation updates: Multiple markdown files have been updated to replace legacy references to "Add and manage artifacts" with new pages like "Log artifacts" and "Update artifacts". For example, links in FAQ, quickstart guides, sidebar configuration, artifact overview, and release notes have been updated accordingly.

3. Navigation and layout improvements: Sidebars, tabs, and content ordering across inventory and artifact pages have been revised. The information on how to edit fields on records, change layout configurations, and manage interdependencies have been reorganized for better clarity and ease-of-use.

4. Workflows enhancements: Instructions for accessing and managing workflows (both on record and artifact pages) have been modified from referencing landing page sections to dedicated tabs. This improves the user experience by clarifying where to look for workflow-related information and actions.

5. Minor style additions: New CSS classes (e.g., .teal and .grey) have been added to support the refined design of highlighted elements in various documentation pages.

Overall, these changes aim to provide users with an updated, clearer, and more consistent experience when managing artifacts and inventory, aligning documentation with recent product updates.

Test Suggestions

• Render the documentation site and verify that all updated links (e.g., Log artifacts, Update artifacts) navigate to the intended pages.
• Test the API endpoint in the Makefile to confirm that the new URL responds correctly and returns the expected Swagger spec.
• Review inventory and artifact pages to ensure that tab labels (e.g., Workflows, Overview, Inventory Fields) function as expected.
• Check new CSS styling to confirm that highlighted elements display in the correct colors and visual hierarchy.
• Perform a full regression test on workflows to ensure navigation changes (clicking on tabs rather than searching for sections) do not break functionality.

[github-actions]

Validate docs site

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