Post release automated changes for containerservice releases #36916
Conversation
github-actions
bot
added
the
Mgmt
There was a problem hiding this comment.
Pull request overview
This PR contains automated post-release changes for the @azure/arm-containerservicefleet package, bumping the version from 2.1.0-beta.2 to 2.1.0-beta.3 in preparation for the next development cycle.
Key changes:
- Version incremented to
2.1.0-beta.3across package files - New unreleased changelog section added for tracking upcoming changes
- Documentation wording refined in sample README files
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| sdk/containerservice/arm-containerservicefleet/package.json | Updates package version to 2.1.0-beta.3 |
| sdk/containerservice/arm-containerservicefleet/src/api/containerServiceFleetContext.ts | Updates user agent string to match new version |
| sdk/containerservice/arm-containerservicefleet/CHANGELOG.md | Adds new unreleased section for version 2.1.0-beta.3 |
| sdk/containerservice/arm-containerservicefleet/samples/v2-beta/typescript/README.md | Changes documentation wording from "correct" to "required" for environment variables |
| sdk/containerservice/arm-containerservicefleet/samples/v2-beta/javascript/README.md | Changes documentation wording from "correct" to "required" for environment variables |
| ``` | ||
|
|
||
| Alternatively, run a single sample with the correct environment variables set (setting up the `.env` file is not required if you do this), for example (cross-platform): | ||
| Alternatively, run a single sample with the required environment variables set (setting up the `.env` file is not required if you do this), for example (cross-platform): |
There was a problem hiding this comment.
The change from "correct" to "required" improves clarity. However, this wording is slightly misleading because not all environment variables shown in the samples are strictly required - the samples can work with different authentication methods. Consider using "appropriate" instead of "required" to be more accurate, as users need the correct/appropriate variables for their chosen authentication method, but they're not all universally required.
| Alternatively, run a single sample with the required environment variables set (setting up the `.env` file is not required if you do this), for example (cross-platform): | |
| Alternatively, run a single sample with the appropriate environment variables set (setting up the `.env` file is not required if you do this), for example (cross-platform): |
| ``` | ||
|
|
||
| Alternatively, run a single sample with the correct environment variables set (setting up the `.env` file is not required if you do this), for example (cross-platform): | ||
| Alternatively, run a single sample with the required environment variables set (setting up the `.env` file is not required if you do this), for example (cross-platform): |
There was a problem hiding this comment.
The change from "correct" to "required" improves clarity. However, this wording is slightly misleading because not all environment variables shown in the samples are strictly required - the samples can work with different authentication methods. Consider using "appropriate" instead of "required" to be more accurate, as users need the correct/appropriate variables for their chosen authentication method, but they're not all universally required.
| Alternatively, run a single sample with the required environment variables set (setting up the `.env` file is not required if you do this), for example (cross-platform): | |
| Alternatively, run a single sample with the appropriate environment variables set for your chosen authentication method (setting up the `.env` file is not required if you do this), for example (cross-platform): |
1 participant
Post release automated changes for azure-arm-containerservicefleet