-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Kusto C# SDK For Managment- 2024-04-13 #47564
base: main
Are you sure you want to change the base?
Kusto C# SDK For Managment- 2024-04-13 #47564
Conversation
API change check APIView has identified API level changes in this PR and created following API reviews. |
@@ -1,5 +1,18 @@ | |||
# Release History | |||
|
|||
## 1.6.0 (2025-01-16) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, I got this error for this date:
"Build log #L44
Invalid date [ 2025-01-16 ]. The date for the changelog being released must be the latest in the file."
Can you help me with this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@guyhirPublic You need to remove ## 1.6.0-beta.1 (Unreleased)
below
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should I keep the content or remove it all? @archerzz
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should I keep the content or remove it all? @archerzz
Since 1.6.0-beta.1
is never released, you need to check the contents and merge them into 1.6.0
if necessary.
@microsoft-github-policy-service agree company="Microsoft" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your account lacks the required public membership to the Azure GitHub organization needed for an internal contributor. Please review the Azure SDK onboarding documentation and use the associated Teams channel for support.
- Azure SDK onboarding (Microsoft internal)
- Azure SDK onboarding assistance (Microsoft internal)
You can verify the state of your account by running the Validate-AzsdkCodeOwner script from the Azure SDK tools repository.
Please also be sure to add yourself to CODEOWNERS for this library, if you will be maintaining it going forward.
@@ -1,5 +1,18 @@ | |||
# Release History | |||
|
|||
## 1.6.0 (2025-01-16) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@guyhirPublic You need to remove ## 1.6.0-beta.1 (Unreleased)
below
sdk/kusto/Azure.ResourceManager.Kusto/src/Generated/Models/CalloutPolicyToRemove.cs
Show resolved
Hide resolved
sdk/kusto/Azure.ResourceManager.Kusto/src/Generated/Models/FollowerDatabaseDefinitionGet.cs
Outdated
Show resolved
Hide resolved
sdk/kusto/Azure.ResourceManager.Kusto/src/Generated/Models/FollowerDatabaseDefinitionGet.cs
Outdated
Show resolved
Hide resolved
sdk/kusto/Azure.ResourceManager.Kusto/src/Generated/Models/OutboundAccess.cs
Outdated
Show resolved
Hide resolved
sdk/kusto/Azure.ResourceManager.Kusto/src/Generated/Models/ScriptLevel.cs
Outdated
Show resolved
Hide resolved
sdk/kusto/Azure.ResourceManager.Kusto/src/Generated/Models/ZoneStatus.cs
Outdated
Show resolved
Hide resolved
@guyhirPublic There are some cspell errors. Please check https://dev.azure.com/azure-sdk/public/_build/results?buildId=4413923&view=logs&j=b70e5e73-bbb6-5567-0939-8415943fadb9&t=2102385d-609d-5572-64d2-932661c7902f&l=140
|
Pls make sure not to release the new package before the 16th of January 2025
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.