-
Notifications
You must be signed in to change notification settings - Fork 387
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
Release Notes Versioning #2406
Comments
Thanks for bringing this to our attention. We will investigate it further and update you shortly. |
@Mattheww65 I've reached out to the team who generates the release notes. I'll follow-up once I hear back from them. |
On the topic of breaking changes please include a note with the planned date for when a breaking change is scheduled to happen. |
@vandre it is difficult for us to announce a release date for breaking changes much ahead of time. For example, major releases usually align with events like Microsoft //Build and we are not allowed to communicate about those dates before it is publicly announced. |
Hi @Mattheww65 , we have updated our ChangeLog generation tool. It will carry the module version in the next release. |
@Mattheww65, the individual module version information has been added to the release notes as of Az PowerShell version 9.4.0. |
The release notes page is great, but a couple of suggestions:
We do not install the full az. module, just the component parts we need ie. az.accounts . It would be really useful to list the version of those parts in the release notes, rather than just the version number of the overarching az. module.
For example, currently we are updating az.Accounts from 2.7.4 to 2.10.4. I'm having to use dates to work out the changes that have been made and tally that up with the az. module version numbers
Breaking changes are great to list, but some kind of filter that would highlight those would be really useful
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: