Skip to content

Update metadata.json #24862

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

Merged
merged 1 commit into from
Jan 24, 2025
Merged

Update metadata.json #24862

merged 1 commit into from
Jan 24, 2025

Conversation

jshigetomi
Copy link
Collaborator

@jshigetomi jshigetomi commented Jan 23, 2025

PR Summary

This pull request updates the release tags in the tools/metadata.json file to reflect the latest versions.

Changes to release tags:

  • Updated StableReleaseTag from "v7.4.6" to "v7.5.0".
  • Updated ReleaseTag from "v7.4.6" to "v7.5.0".
  • Updated LTSReleaseTag from ["v7.2.24", "v7.4.6"] to ["v7.4.7"].

PR Context

PR Checklist

@jshigetomi
Copy link
Collaborator Author

/azp run PowerShell-CI-macos, PowerShell-CI-Linux, PowerShell-CI-Windows, PowerShell-Windows-Packaging-CI, PowerShell-CI-static-analysis, PSResourceGet ACR

Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@jshigetomi jshigetomi marked this pull request as ready for review January 24, 2025 18:24
"PreviewReleaseTag": "v7.6.0-preview.2",
"ServicingReleaseTag": "v7.0.13",
"ReleaseTag": "v7.4.6",
"LTSReleaseTag" : ["v7.2.24", "v7.4.6"],
"ReleaseTag": "v7.5.0",
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

People are using this parameter. Should it be the latest stable release like this 7.5.0?

@TravisEz13 TravisEz13 merged commit 85fcb72 into master Jan 24, 2025
34 checks passed
@TravisEz13 TravisEz13 deleted the metadata branch January 24, 2025 19:16
Copy link
Contributor

microsoft-github-policy-service bot commented Jan 24, 2025

📣 Hey @jshigetomi, how did we do? We would love to hear your feedback with the link below! 🗣️

🔗 https://aka.ms/PSRepoFeedback

@TravisEz13 TravisEz13 added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants