Add inactive VuMark credentials to secrets#3013
Merged
adamtheturtle merged 3 commits intomainfrom Feb 23, 2026
Merged
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
INACTIVE_VUMARK_*credentials from a newly created inactive VuMark databaseadmin/add_inactive_vumark_secrets.pyfor updating secrets in the future with new inactive VuMark databasesChanges
secrets.tar.gpg: Updated archive containing ci_secrets with new INACTIVE_VUMARK fieldsadmin/add_inactive_vumark_secrets.py: New script that creates an inactive VuMark database and updates all existing secrets filesThis implements the infrastructure for the shared inactive VuMark database referenced in commit 74d386d.
Note
Low Risk
The provided diff contains only a deletion marker (
+++ /dev/null) without a filename or content, so the actual change cannot be verified; based on what’s shown, it’s a low-risk no-op or single-file deletion.Overview
The supplied
full_diffdoes not include any file paths or content changes—only a+++ /dev/nullline—so the PR’s actual modifications can’t be determined from the diff.Based strictly on what’s shown, the change is either a no-op diff capture issue or a single file deletion with no further context.
Written by Cursor Bugbot for commit 4e1274f. This will update automatically on new commits. Configure here.