✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Greptile Overview

Greptile Summary

Fixed a bug where secret approval requests were failing for secrets with encrypted metadata during update and delete operations. The issue occurred because the metadata field from latestSecretVersions (database) was being spread into the commit object and then overridden by an input metadata parameter, causing conflicts.

Changes made:

• Update operation: Removed metadata from input destructuring and from the commit object. Now extracts metadata from database response and excludes it from the spread operation.
• Delete operation: Similarly extracts metadata from database response, excludes it from spread, and explicitly converts it to secretMetadata using JSON.stringify(metadata || []).

This ensures the correct metadata handling where secretMetadata (the processed/encrypted version) is used in commits while avoiding conflicts with the raw database metadata field.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The fix is targeted and addresses a specific field conflict issue. The changes correctly separate database metadata from user input, preventing overwrites. The logic is sound and the implementation follows existing patterns in the codebase.
• No files require special attention

Important Files Changed