Skip to content

Conversation

@Francisco-Gamino
Copy link
Contributor

Description

These PR fixes the following issues:

Changelog

  • Updated API client to latest commit for version 2023-12-01
  • Refreshed stack definitions
  • Enforced runtime EOL policy: block expired, warn if within 6 months
  • Updated tests

Mandatory Checklist

  • SHOULD update ChangeLog.md file(s) appropriately
    • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
      • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
    • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
  • SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
  • SHOULD have proper test coverage for changes in pull request.
  • SHOULD NOT adjust version of module manually in pull request

@azure-client-tools-bot-prd
Copy link

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

@Francisco-Gamino
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link
Contributor

Commenter does not have sufficient privileges for PR 27726 in repo Azure/azure-powershell

@wyunchi-ms
Copy link
Contributor

/azp run azure-powershell - powershell-core

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Member

@isra-fel isra-fel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Francisco, we've simplified our dev process so all the changes now go into main branch, the generation branch is obsolete.

@wyunchi-ms wyunchi-ms added the Legacy based on legacy branch (main/generation branch) prior to non-generation migration label May 13, 2025
@github-actions
Copy link

To improve dev experience and reduce maintenance efforts, we are deprecating branch: generation now. Azure-PowerShell modules generated by autorest.powershell no longer target branch generation, and will be targeting directly to main instead.

Please find migration guide and document below:

@Francisco-Gamino
Copy link
Contributor Author

This PR is replaced by #27745.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Legacy based on legacy branch (main/generation branch) prior to non-generation migration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants