SOCRadar Alerts solution v3.0.1

[Radargoger]

Version bump to 3.0.1. Fixes a Content Hub install error caused by a utcNow expression in a nested template parameter default. No logic changes — version strings only.

[Radargoger]

v-maheshbh (@v-maheshbh) This is a follow-up to #13858 — a small version bump to 3.0.1 that fixes a Content Hub install error caused by a utcNow expression in a nested template default. Only version strings changed; playbook logic is identical. Could you please review when you have a chance? Thank you!

[v-maheshbh (v-maheshbh)]

Hi Radargoger

Kindly ensure that the existing ZIP file is not deleted as part of this change. and I do not see any changes related to utcNow() in this PR.

Thanks!

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Bumps the SOCRadar solution version to 3.0.1 and updates release notes to reflect the new release.

Changes:

• Added 3.0.1 entry to SOCRadar release notes
• Updated solution version strings from 3.0.0 to 3.0.1 in the main template and solution metadata

Reviewed changes

Copilot reviewed 3 out of 5 changed files in this pull request and generated 1 comment.

File	Description
Solutions/SOCRadar/ReleaseNotes.md	Adds a 3.0.1 release note entry describing the reported deployment fix.
Solutions/SOCRadar/Package/mainTemplate.json	Updates _solutionVersion and properties.version to 3.0.1.
Solutions/SOCRadar/Data/Solution_SOCRadar.json	Updates the solution metadata Version to 3.0.1.

[Radargoger]

Hi Radargoger

Kindly ensure that the existing ZIP file is not deleted as part of this change. and I do not see any changes related to utcNow() in this PR.

Thanks!

Thanks for the review!

The existing 3.0.0.zip has been restored in the latest commit, so no package is removed — both 3.0.0.zip and 3.0.1.zip are now present.
Regarding utcNow: the template-level fix is already part of the merged solution (#13858) — in mainTemplate.json the inner playbook templates reference parameters('triggerStartTime') and there is no utcNow in any inner parameter default. This PR is therefore a version bump (3.0.0 → 3.0.1) to align the GitHub solution version with the package being resubmitted for certification, as required by the version-match rule. No template/logic change is expected in this diff.

[Radargoger]

Thanks for the review!

• The existing 3.0.0.zip has been restored in the latest commits, so no package is removed — both 3.0.0.zip and 3.0.1.zip are now present in the Package folder.
• Regarding utcNow: the template-level fix is already part of the merged solution (SOCRadar: Add SOCRadar Solution V1.0.0 #13858) — in mainTemplate.json the inner playbook templates reference parameters('triggerStartTime') and there is no utcNow in any inner parameter default. This PR is therefore a version bump (3.0.0 → 3.0.1) to align the GitHub solution version with the package being resubmitted for certification, as required by the version-match rule. No template/logic change is expected in this diff. I have also updated the 3.0.1 release note to reflect this.

[Radargoger]

Thank you for your support! v-maheshbh (@v-maheshbh) we updated based on your feedback!!

[v-maheshbh (v-maheshbh)]

Hi Radargoger

Kindly update your branch with the latest changes from the master branch.

thanks!

[Radargoger]

Hi v-maheshbh (@v-maheshbh) ,

I've merged the latest changes from master into the branch. It's now up to date with no conflicts. Please take another look when you get a chance. Thank you for support! Thanks in advance!

[v-maheshbh (v-maheshbh)]

Hi Radargoger

Have you published the previous version in Partner Center? If so, were there any rejections during the certification process? If yes, could you please share the rejection details with us?
Could you please confirm which version is currently live in Partner Center?

Thanks!

[Radargoger]

Hi v-maheshbh (@v-maheshbh)
Yes, we submitted to Partner Center and it was rejected (policy 300.4.1.1), saying the certified package (3.0.1) differs from GitHub (3.0.0) and to keep 3.0.0.
However, 3.0.1 is the correct version. We identified an issue in 3.0.0 (possibly related to when I added the app to Azure Center before the PR was merged), and 3.0.1 contains the fix. That's why this PR updates the version. Reverting to 3.0.0 would reintroduce the bug.
Currently in Partner Center: the plan shows as "Published" with 3.0.1.zip uploaded, but Certification is "Errored" due to the mismatch. I think it's because this PR isn't merged to master yet, so certification still sees 3.0.0.
Could you help get 3.0.1 certified? Let me know if anything is needed on our side.
Thanks!
Burak

[v-maheshbh (v-maheshbh)]

Hi v-maheshbh (@v-maheshbh) Yes, we submitted to Partner Center and it was rejected (policy 300.4.1.1), saying the certified package (3.0.1) differs from GitHub (3.0.0) and to keep 3.0.0. However, 3.0.1 is the correct version. We identified an issue in 3.0.0 (possibly related to when I added the app to Azure Center before the PR was merged), and 3.0.1 contains the fix. That's why this PR updates the version. Reverting to 3.0.0 would reintroduce the bug. Currently in Partner Center: the plan shows as "Published" with 3.0.1.zip uploaded, but Certification is "Errored" due to the mismatch. I think it's because this PR isn't merged to master yet, so certification still sees 3.0.0. Could you help get 3.0.1 certified? Let me know if anything is needed on our side. Thanks! Burak

Hi Radargoger

The last merged PR #13858 introduced version 3.0.0, which ideally should be the version published in Partner Center. Could you please clarify why 3.0.1 was published instead? The version bump to 3.0.1 in this PR does not appear to be correct based on the previous release.

thanks!

[Radargoger]

Hi v-maheshbh (@v-maheshbh) ,
There are actually two different 3.0.0 packages. The 3.0.0 in GitHub master (from #13858) is correct: in mainTemplate.json the inner playbook templates use parameters('triggerStartTime') and no inner parameter default contains utcNow. The 3.0.0 I uploaded to Partner Center earlier, before #13858 was merged, is an older build that still has the nested utcNow issue and fails at install. When I said "3.0.0 has the bug," I was referring to that older Partner Center package, not the master one. Partner Center does not allow republishing over the same version number, so I had to upload the corrected content as 3.0.1. The content is identical to master 3.0.0; only the version label differs, which is why this diff shows version strings only. If you merge this PR, master becomes 3.0.1 and matches the 3.0.1 already in Partner Center, which clears the 300.4.1.1 mismatch and certifies the fixed package. I can share the install error repro for the old package if useful. Thanks in advance.
Best Regards.
Burak