Package generation/naming in Azure Sentinel Solution

Question

Regarding the Sentinel solution package generation and its version number, I believe I have resolved the issue, please correct me for the below 2 questions.

1/What i did was i modified the defaultPackageVersion in the package creation tool (createSolutionV3.ps1) , then generate a zip file named 3.0.1.zip, and submitted a PR for this zip file to GitHub.

2/Should this process be executed locally only rather than relying on a GitHub workflow?

Thanks in advance!

Answer 1

@LXF Thank you for reaching out to us, to answer the above-mentioned questions:

1. Yes, modifying the defaultPackageVersion in the package creation tool (createSolutionV3.ps1) and generating a zip file with the desired version number is the correct way to change the version number of the Sentinel solution package. Once you have generated the zip file, you can submit a pull request (PR) to GitHub to update the package.
2. Whether or not to execute this process locally or rely on a GitHub workflow depends on your specific requirements and preferences. If you are the only one making changes to the Sentinel solution package and you are comfortable generating the package locally and submitting a PR to GitHub, then executing the process locally may be sufficient. However, if you have multiple people working on the Sentinel solution package or you want to automate the process of generating and submitting the package, then using a GitHub workflow may be more appropriate.

Let me know if you have any further questions, feel free to post back.

Please remember to "Accept Answer" if answer helped, so that others in the community facing similar issues can easily find the solution.