Skip to content

demisto-sdk-release 1.38.18 #42661

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
yedidyacohenpalo merged 3 commits into from
Jan 20, 2026
Merged

demisto-sdk-release 1.38.18 #42661

yedidyacohenpalo merged 3 commits into from
Jan 20, 2026

Conversation

@content-bot
Copy link
Contributor

@content-bot content-bot commented Jan 14, 2026 •
edited
Loading

Feature

  • Update BC115 validation to support default supportedModules handling. #5122
  • Adds a new validation (BA129) that ensures commands/scripts declare the appropriate compliantpolicies when using arguments associated with specific compliance standards (defined in compliant_policies.json). #5168
  • Improved handling private repositories. #5185

Internal

  • Added AgentixAgent to test tools. #5143
  • Delete Link PR to Jira github actions #5191
  • Added support for the fromversion and toversion fields for Agentix items. #5180
  • Updated Agentix items default marketplaces to platform only. #5180

@yedidyacohenpalo yedidyacohenpalo added the ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines label Jan 14, 2026
@yedidyacohenpalo yedidyacohenpalo added the ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. label Jan 14, 2026
@content-bot content-bot removed the ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. label Jan 14, 2026
@content-bot
Copy link
Contributor Author

content-bot commented Jan 14, 2026

🤖 Content AI Reviewer: Analysis started. Please wait for results...

@content-bot
Copy link
Contributor Author

content-bot commented Jan 14, 2026

Validate summary
The following errors were reported as warnings: RM108, GR109.
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? ✅

@yedidyacohenpalo yedidyacohenpalo merged commit 8291971 into master Jan 20, 2026
41 of 44 checks passed
@yedidyacohenpalo yedidyacohenpalo deleted the 1.38.18 branch January 20, 2026 18:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yedidyacohenpalo yedidyacohenpalo yedidyacohenpalo approved these changes

@YuvHayun YuvHayun Awaiting requested review from YuvHayun YuvHayun is a code owner

Assignees

No one assigned

Labels

docs-approved ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines skip-ai-review

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@content-bot @yedidyacohenpalo @tcarmeli1