Uh oh!
There was an error while loading. Please reload this page.
added audit check and fix for assets in pending or quarantined state - #323
Merged
Conversation
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
Consider reviewing these vulnerabilities when fixes become available. |
naman-contentstack
approved these changes
Aug 4, 2026
Uh oh!
There was an error while loading. Please reload this page.
netrajpatel added a commit
that referenced
this pull request
Aug 5, 2026
Brings in the 27 commits development gained after the previous merge (PR #217 Asset-Scanning-v1, #322, #323 and others), clearing the conflict that was blocking PR #243 and preventing GitHub Actions from producing a merge ref. Only .talismanrc conflicted. Resolved to the checksum for the merged pnpm-lock.yaml (95ad8483..., confirmed via `talisman --checksum`) and moved `version` back to the top level, where talisman expects it — development's side had it indented under the fileignoreconfig entry. Verified before push: - `pnpm install --frozen-lockfile` passes (the auto-merged lockfile is self-consistent; this is the check that caught the broken lockfile in PR #324 and the dropped `open` dependency in the previous merge) - dependency sweep against both merge parents: nothing lost - undeclared-import sweep unchanged from baseline: no new hybrids - test suites for all six packages this merge touched: contentstack-audit 160 passing contentstack-export 485 passing contentstack-external-migrate 42 passing contentstack-import 1736 passing contentstack-query-export 139 passing contentstack-bulk-publish (no test script) Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
naman-contentstack pushed a commit
that referenced
this pull request
Aug 7, 2026
Brings in the 27 commits development gained after the previous merge (PR #217 Asset-Scanning-v1, #322, #323 and others), clearing the conflict that was blocking PR #243 and preventing GitHub Actions from producing a merge ref. Only .talismanrc conflicted. Resolved to the checksum for the merged pnpm-lock.yaml (95ad8483..., confirmed via `talisman --checksum`) and moved `version` back to the top level, where talisman expects it — development's side had it indented under the fileignoreconfig entry. Verified before push: - `pnpm install --frozen-lockfile` passes (the auto-merged lockfile is self-consistent; this is the check that caught the broken lockfile in PR #324 and the dropped `open` dependency in the previous merge) - dependency sweep against both merge parents: nothing lost - undeclared-import sweep unchanged from baseline: no new hybrids - test suites for all six packages this merge touched: contentstack-audit 160 passing contentstack-export 485 passing contentstack-external-migrate 42 passing contentstack-import 1736 passing contentstack-query-export 139 passing contentstack-bulk-publish (no test script) Co-Authored-By: Claude Opus 5 (1M context) <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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.