Skip to content
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.

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

Fixing Dragos PublisherId based on partner center submission #11706

Merged
merged 2 commits into from
Jan 24, 2025

Conversation

dragosinc-sentinel
Copy link
Contributor

Required items, please complete

Change(s):

  • Updating the Dragos Publisher ID to match our ID in Microsoft Partner Center.

Reason for Change(s):

  • Earlier this week, we merged our first release of the Dragos Sentinel Solution (see Initial Release of Dragos Sentinel Solution #11582). After the PR was approved and merged, we submitted the release through Microsoft Partner Center. Unfortunately, our submission was rejected as the publisher ID in Github was not correct.
  • We also corrected the publish dates to better reflect the publish dates based on the actual PR approval times.
  • We have not released version 3.0.0 through Partner Center so requesting a minor update based on submission feedback.

Version Updated:

  • No. See above.

Testing Completed:

Checked that the validations are passing and have addressed any issues that are present:

  • Yes

@dragosinc-sentinel dragosinc-sentinel requested review from a team as code owners January 23, 2025 22:52
@dragosinc-sentinel
Copy link
Contributor Author

@v-shukore and @v-prasadboke please review this minor change as our Microsoft Partner Center submission was rejected with a minor issue. Thanks!

@v-atulyadav v-atulyadav added the Solution Solution specialty review needed label Jan 24, 2025
@v-atulyadav v-atulyadav merged commit 4f9bc9d into Azure:master Jan 24, 2025
31 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Solution Solution specialty review needed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants