Skip to content

demisto-sdk-release 1.39.8 - #45639

Merged
BEAdi merged 1 commit into
masterfrom
1.39.8
Aug 25, 2026
Merged

demisto-sdk-release 1.39.8#45639
BEAdi merged 1 commit into
masterfrom
1.39.8

Conversation

@content-bot

@content-bot content-bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Fix

  • Fixed an issue where the pack-level [pack] section of .pack-ignore was not honored for validators listed in ALWAYS_RUN_ON_ERROR_CODE. ValidateManager.filter_validation_results now consults both the content item's per-file ignored_errors and the pack's pack_level_ignored_errors. #5503

Internal

  • Added CO116, CO130, and CO171 to the list of ignorable ConnectUs validators, refined CO130 diagnostics and CO171 serializer awareness, and fixed a should_run preflight over-suppression where per-handler .connector-ignore entries silenced whole-connector validation runs. #5505

@content-bot

Copy link
Copy Markdown
Contributor Author

🤖 AI-Powered Code Review Available

You can leverage AI-powered code review to assist with this PR!

Available Commands:

  • @marketplace-ai-reviewer start review - Initiate a full AI code review
  • @marketplace-ai-reviewer re-review - Incremental review for new commits

@content-bot

Copy link
Copy Markdown
Contributor Author

Validate summary
The following errors were thrown as a part of this pr: .
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.

Verdict: PR can be force merged from validate perspective? ✅

@rshunim rshunim added ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. labels Aug 24, 2026
@marketplace-ai-reviewer marketplace-ai-reviewer removed the ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. label Aug 24, 2026
@marketplace-ai-reviewer

Copy link
Copy Markdown
Contributor

🤖 Analysis started. Please wait for results...

@marketplace-ai-reviewer

Copy link
Copy Markdown
Contributor
🤖 AI Review Disclaimer

This review was generated by an AI-powered tool and may contain inaccuracies. Please be advised, and we extend our sincere apologies for any inconvenience this may cause.

@marketplace-ai-reviewer marketplace-ai-reviewer 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.

Thank you for your contribution! No issues found. Great work! 👍

@rshunim, @content-bot please review and approve the results generated by the AI Reviewer by responding 👍 on this comment.

@content-bot

Copy link
Copy Markdown
Contributor Author

🔍 AI Triage Report Available

An automated triage report has been generated for this pipeline.

Status: failed
Report ID: 50da7ab195834c23

📋 Triage Report
💡 Resolutions are available in the full report.

⚠️ AI-generated triage. Validate before acting.

@rshunim rshunim added the ForceMerge Forcing the merge of the PR despite the build status label Aug 25, 2026
@rshunim

rshunim commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

ForceMerge is needed due to:

ContentClientApiModule_test.py:12: in
import respx
E ModuleNotFoundError: No module named 'respx'

on-call issue

@BEAdi
BEAdi merged commit 231bef2 into master Aug 25, 2026
71 of 77 checks passed
@BEAdi
BEAdi deleted the 1.39.8 branch August 25, 2026 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-approved ForceMerge Forcing the merge of the PR despite the build status ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants