Skip to content

Adding blog for platform release channel#543

Open
tulikac wants to merge 1 commit into
masterfrom
platform-release-channel
Open

Adding blog for platform release channel#543
tulikac wants to merge 1 commit into
masterfrom
platform-release-channel

Conversation

@tulikac
Copy link
Copy Markdown
Collaborator

@tulikac tulikac commented May 6, 2026

Summary

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 6, 2026

Preview link: https://antares-blog-staging-pr-543.azurewebsites.net

  • Your changes have been deployed to the preview site. The preview site will update as you add more commits to this branch.
  • The preview site shows any future-dated articles. If you are publishing a future-dated article, it will not show on the production site until the file's specified date.
  • The preview link is shareable, but will be deleted when this pull request is merged or closed.

This is an automated message.

@tulikac tulikac requested a review from btardif May 6, 2026 11:51
Comment on lines +26 to +30
| Channel | Behavior | Recommended for |
| ------------ | -------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| **Latest** | Uses the latest patch versions rolled out on App Service | Apps where staying current with security and platform updates is the top priority |
| **Standard** | Default setting. Runs one App Service patch rollout behind Latest | Most production apps that want a balance of stability and currency |
| **Extended** | Runs further behind Latest, giving more time before adopting newer patches | Apps that need additional validation time before moving to newer patches |
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@tulikac see if there is an opportunity to align with screenshot


The release channels move forward with each runtime patch rollout.

When a new patch is rolled out to **Latest**, the **Standard** channel moves to the patch version that was previously on **Latest**. **Extended** stays further behind to provide more validation time.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

we don't wait unitl there is a new version before moving latest to standard

| ---------- | --------------: | -----: | -------: | -------: |
| DOTNETCORE | 10 | 10.0.7 | 10.0.4 | 10.0.2 |

When the next .NET 10 patch rollout happens, **Standard** will move to **10.0.7**, while **Latest** will move to the newly rolled-out patch version.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

same here

Comment on lines +48 to +50
When the next .NET 10 patch rollout happens, **Standard** will move to **10.0.7**, while **Latest** will move to the newly rolled-out patch version.

For some stacks, you may currently see the same patch version for both **Standard** and **Extended**. We are working through another rollout for these stacks, and the channel versions will be updated as that rollout progresses.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

this needs re-work

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants