Skip to content

Merge Staging into Prod - #1460

Closed
nibalizer wants to merge 151 commits into
prodfrom
staging
Closed

Merge Staging into Prod#1460
nibalizer wants to merge 151 commits into
prodfrom
staging

Conversation

@nibalizer

Copy link
Copy Markdown
Contributor

Pull Request Description

Merge Staging into Prod

Not sure why this doesn't have automation.

What and why?

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 Bot and others added 30 commits July 9, 2026 23:56
…alidation

Speed up automated release notes previews
…tifact

Promote prebuilt documentation artifacts to production
…-build

Fix production artifact merge prediction
github-actions Bot and others added 24 commits July 30, 2026 16:45
Cover Settings Templates create-from-scratch and PDF outline flows from SC-16316, and list-row duplicate actions.

Co-authored-by: Cursor <cursoragent@cursor.com>
Clarify organization-wide Activity vs per-record Activity, and document the Activity Filter and Record/Artifact Filter tabs from SC-16807.

Co-authored-by: Cursor <cursoragent@cursor.com>
Document the SC-16807 query-builder fields for Settings Activity and expand what is tracked to match shipped audit scopes.

Co-authored-by: Cursor <cursoragent@cursor.com>
Align overview and category filter copy with attestation governance events and clearer inventory/workflow wording.

Co-authored-by: Cursor <cursoragent@cursor.com>
docs: document org-wide record activity views and filters [sc-17354]
Expand capabilities, fix filter claims, reconcile supported clients, and document limitations against the shipped ValidMind MCP server.

Co-authored-by: Cursor <cursoragent@cursor.com>
Rename Chatbot capabilities, enable search, and add it beside the MCP guide in the Guides sidebar.

Co-authored-by: Cursor <cursoragent@cursor.com>
…et-new-document-templates

docs: document create template and PDF outline upload [sc-17034]
Add a dedicated OIDC setup guide and point install, credentials, troubleshooting, and quickstarts at the alternate path shipped in library 2.13+.

Co-authored-by: Cursor <cursoragent@cursor.com>
Confirm and document that the Public API accepts OIDC bearer tokens alongside API keys, and point the interactive OpenAPI page at the overview auth guidance.

Co-authored-by: Cursor <cursoragent@cursor.com>
Quarto emitted fenced-div warnings during CI validate when an OIDC credentials tabset was nested inside the existing setup tabset.

Co-authored-by: Cursor <cursoragent@cursor.com>
…ibrary-oidc

docs: ValidMind Library OIDC device-flow authentication [sc-17043]
@CLAassistant

CLAassistant commented Jul 31, 2026

Copy link
Copy Markdown

CLA assistant check
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.
5 out of 6 committers have signed the CLA.

✅ github-actions[bot]
✅ jamadriz
✅ juanmleng
✅ cachafla
✅ emmavdh
❌ Emma Van Der Heide


Emma Van Der Heide seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@github-actions

Copy link
Copy Markdown
Contributor

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

@github-actions

Copy link
Copy Markdown
Contributor

Validate docs site

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

@nibalizer nibalizer added the internal Not to be externalized in the release notes label Jul 31, 2026
@cachafla

Copy link
Copy Markdown
Contributor

Let's re-run this after https://github.com/validmind/release-notes/pull/136 merges and the staging branch has been updated

@nibalizer nibalizer closed this Jul 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal Not to be externalized in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants