Update TrendMicroVisionOneV3.yml

[tpi007]

update new version of pytmv1

Contributing to Cortex XSOAR Content

Make sure to register your contribution by filling the contribution registration form

The Pull Request will be reviewed only after the contribution registration form is filled.

Status

• In Progress
• Ready
• In Hold - (Reason for hold)

Related Issues

fixes: link to the issue

Description

A few sentences describing the overall goals of the pull request's commits.

Must have

• Tests
• Documentation

[CLAassistant]

All committers have signed the CLA.

[content-bot]

Thank you for your contribution. Your generosity and caring are unrivaled! Make sure to register your contribution by filling the Contribution Registration form, so our content wizard @merit-maita will know the proposed changes are ready to be reviewed.
For your convenience, here is a link to the contributions SLAs document.

[content-bot]

Hi @tpi007, thanks for contributing to the XSOAR marketplace. To receive credit for your generous contribution please follow this link.

[merit-maita]

thank you for your contribution
please make sure to fill the contribution form
in addition to that, updating the yml or py file requires adding Release note, so please do with the note that says:

• Updated the Docker image to demisto/pytmv1:0.9.2.4398531.

[tpi007]

Updated the Docker image to demisto/pytmv1:0.9.2.4398531.

[merit-maita]

Updated the Docker image to demisto/pytmv1:0.9.2.4398531.

sorry i might've not explained it well, Release note is a file created in the pack itself (in the Release notes folder) where the changes of the new version is documented, to create this file run the command:
demisto-sdk update-release-notes -i Packs/TrendMicroVisionOne/Integrations/TrendMicroVisionOneV3
then go to the new created file and add the note i sent you.

[tpi007]

Hi @merit-maita
I have add release notes 4_2_8.md file

[merit-maita]

@tpi007 the version needs to be raised in the pack_metadata file as well, to the same version created for the rn file.

[tpi007]

@merit-maita I also updated pack_metadata file

[content-bot]

For the Reviewer: Trigger build request has been accepted for this contribution PR.

[content-bot]

For the Reviewer: Successfully created a pipeline in GitLab with url: https://gitlab.xdr.pan.local/xdr/cortex-content/content/-/pipelines/4447195

[tpi007]

Hi @merit-maita
Thanks for your help, but I still find that 3 failing checks in the following:
failing checks
docs-approved label verification / check_label_job (pull_request)
docs-approved label verification / check_label_job (pull_request)Failing after 1m
Required
Partner-Approved label verification / check_label_job (pull_request)
Partner-Approved label verification / check_label_job (pull_request)Failing after 1m
Required
pre-commit / pre-commit / pre-commit (pull_request)
pre-commit / pre-commit / pre-commit (pull_request)Failing after 4m

would U please help check why there are failing, how can i do to by pass these checking.

Thanks

[merit-maita]

Hi @merit-maita Thanks for your help, but I still find that 3 failing checks in the following: failing checks docs-approved label verification / check_label_job (pull_request) docs-approved label verification / check_label_job (pull_request)Failing after 1m Required Partner-Approved label verification / check_label_job (pull_request) Partner-Approved label verification / check_label_job (pull_request)Failing after 1m Required pre-commit / pre-commit / pre-commit (pull_request) pre-commit / pre-commit / pre-commit (pull_request)Failing after 4m

would U please help check why there are failing, how can i do to by pass these checking.

Thanks

im going to handle these failures, it's all good

[github-actions]

Thank you for your contribution. Your external PR has been merged and the changes are now included in an internal PR for further review. The internal PR will be merged to the master branch within 3 business days.