Skip to content

fix(release): redact deploy keys, check operation-backed tools in the saved-credential contract, and drop SDK copy - #9864

Merged
waleedlatif1 merged 1 commit into
stagingfrom
fix/release-audit-cleanups
Nov 11, 2026
Merged

waleedlatif1 merged 1 commit into
stagingfrom
fix/release-audit-cleanups

Conversation

@waleedlatif1

@waleedlatif1 waleedlatif1 commented Nov 10, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Release-audit cleanups that no other follow-up PR covers. Trimmed to avoid overlap: Firecrawl depth and CONTRIBUTING landed in #9860; normalized account ids and compare-data wording are in #9859; Mistral Max Images is in #9863; proxy/NO_PROXY docs are in #9865.

  • Redaction: deployKey (Convex) is now a sensitive key, so its value is redacted in persisted logs and console output. A bare secretKey stays unredacted on purpose: Infisical returns each secret's name in that field
  • Saved-credential contract: operation-backed tools were exempt from the host-steering check, so a future tool adding an unmapped host param would pass CI. Destination-named params on operation-backed tools now count as steering (AWS families are still skipped by the caller); the four current tools whose matching params are request data (startUrl, serverId, audioUrl, customDomain) are listed with the reason — each was checked to send its token only to the vendor's fixed API host
  • Logfire: documented why region is mapped alongside host on the saved credential
  • SDK leftovers: landing nav no longer advertises SDKs; CI.md planner wording says "Standalone package"

Type of Change

  • Bug fix

Testing

  • New cases in lib/core/security/redaction.test.ts and scripts/saved-credential-contract.test.ts; each guard was reverted and its test went red
  • bunx vitest run lib/core/security/redaction.test.ts scripts/saved-credential-contract.test.ts plus every test touching secretKey/deployKey (1,020 tests) — all pass
  • check-block-registry.ts origin/staging (saved-credential contract passes), check:comment-hygiene
  • lint:check + type-check via the pre-push hook; full check:audits and bun run test left to CI

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing (new tests pass the test-audit authoring gate)
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

@vercel

vercel Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
docs Ready Ready Preview Nov 10, 2026 11:51pm UTC

Request Review

@greptile-apps

greptile-apps Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] No new blocking issue was established, and no numbered previous finding was supplied for scoring.

Summary

The PR expands credential redaction and adds destination checks for operation-backed tools.

  • Secret-key fields now get redacted from shared output.
  • The saved-credential check now checks destination-like inputs on operation-backed tools.
  • Docs now name the CLI and clarify package and Logfire wording.

Previous-thread context: waleedlatif1 acknowledged the Infisical naming issue and rejected renaming secretKey because saved workflows reference it. They reported removing the pattern, but the reviewed head still contains it. The supplied thread is unnumbered, so it receives no previousFindings entry and is not reposted.

Review checks used source inspection; no tests or browser checks were run.

Reviews (4) · Last reviewed commit: "fix(release): redact secret-key fields, ..." · Reviewed by Greptile

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 16 files

Reply with feedback, questions, or to request a fix.

Turn on auto-fix | Re-trigger cubic

Comment thread apps/sim/tools/firecrawl/crawl.ts Resolved
Comment thread .github/CONTRIBUTING.md Resolved
Comment thread .github/CI.md Resolved
@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@greptile

@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@cubic-dev-ai review this PR

@cubic-dev-ai

cubic-dev-ai Bot commented Nov 10, 2026

Copy link
Copy Markdown
Contributor

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 16 files

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

Turn on auto-fix | Re-trigger cubic

…in the saved-credential contract, and drop SDK copy
@waleedlatif1
waleedlatif1 force-pushed the fix/release-audit-cleanups branch from 729b37f to 104face Compare November 10, 2026 23:47
@waleedlatif1 waleedlatif1 changed the title fix(release): Firecrawl start-relative depth, secret-key redaction, operation-backed credential contract, and audit cleanups fix(release): redact secret-key fields, check operation-backed tools in the saved-credential contract, and drop SDK copy Nov 10, 2026
@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@greptile

@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@cubic-dev-ai review this PR

@cubic-dev-ai

cubic-dev-ai Bot commented Nov 10, 2026

Copy link
Copy Markdown
Contributor

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 7 files

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

Turn on auto-fix | Re-trigger cubic

Comment thread apps/sim/lib/core/security/redaction.ts Resolved
@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@greptile

@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@cubic-dev-ai review this PR

@cubic-dev-ai

cubic-dev-ai Bot commented Nov 10, 2026

Copy link
Copy Markdown
Contributor

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 7 files

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

Turn on auto-fix | Re-trigger cubic

@waleedlatif1 waleedlatif1 changed the title fix(release): redact secret-key fields, check operation-backed tools in the saved-credential contract, and drop SDK copy fix(release): redact deploy keys, check operation-backed tools in the saved-credential contract, and drop SDK copy Nov 10, 2026
@waleedlatif1
waleedlatif1 merged commit 15cf51d into staging Nov 11, 2026
86 checks passed
waleedlatif1 added a commit that referenced this pull request Nov 11, 2026
…k crawl depth as unset (#9857)

* fix(release): measure Firecrawl crawl depth from the start URL and reuse only full-access delegation keys

* fix(release): leave Firecrawl crawl depth to #9864

* fix(firecrawl): treat a blank crawl maxDepth as unset

* test(release): prove delegation refuses read-only keys and type a blank crawl depth
@waleedlatif1
waleedlatif1 deleted the fix/release-audit-cleanups branch November 11, 2026 00:28
@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

Correction: the follow-up commit that dropped the bare secretKey pattern (the Infisical thread above) failed to push and was not in this squash-merge, so staging still redacts secretKey. The fix is restored in a new PR against staging.

This branch was successfully deployed

1 active deployment
Preview — 104face6 Deployed Nov 10, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant