Repository navigation
Move Application Insights CDN preview publishing from beta to next - #2793
Open
Hector Hernandez (hectorhdzg) wants to merge 6 commits into
Open
Hector Hernandez (hectorhdzg) wants to merge 6 commits into
Hector Hernandez (hectorhdzg) wants to merge 6 commits into
Conversation
Route release candidates and beta-version artifacts to next, reject beta activation, and preserve production paths and legacy listing. Add offline routing regression coverage and migrate the live CDN monitor. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The version-listing script omits beta configurations and aliases published under the test prefix in the next container.
1 open issue
What changed in this PR
Moves the Application Insights SDK’s writable preview CDN channel from beta to next across six publishing families, while preserving production destinations and legacy beta artifacts.
Changes:
- Routes releases to
nextand production, routes prereleases only tonext, and rejects beta-channel activation. - Preserves beta configuration test prefixes and aliases, and moves the live CDN monitor to
next. - Adds offline routing regression tests to CI and updates deployment documentation.
| File | Description |
|---|---|
| tools/config/scripts/setAzActiveCdnVersion.ps1 | Restricts activation channels and selects beta test aliases. |
| tools/config/scripts/publishAzReleaseToCdn.ps1 | Publishes beta test configurations to next. |
| tools/config/README.md | Documents configuration endpoints and test aliases. |
| tools/chrome-debug-extension/scripts/setAzActiveCdnVersion.ps1 | Rejects beta-channel activation. |
| tools/chrome-debug-extension/scripts/publishAzReleaseToCdn.ps1 | Routes preview artifacts to next/tools. |
| README.md | Updates CDN promotion and canary guidance. |
| extensions/applicationinsights-perfmarkmeasure-js/scripts/setAzActiveCdnVersion.ps1 | Restricts preview activation to next. |
| extensions/applicationinsights-perfmarkmeasure-js/scripts/publishAzReleaseToCdn.ps1 | Routes preview artifacts to next/ext. |
| extensions/applicationinsights-debugplugin-js/scripts/setAzActiveCdnVersion.ps1 | Restricts preview activation to next. |
| extensions/applicationinsights-debugplugin-js/scripts/publishAzReleaseToCdn.ps1 | Routes preview artifacts to next/ext. |
| extensions/applicationinsights-clickanalytics-js/scripts/setAzActiveCdnVersion.ps1 | Restricts preview activation to next. |
| extensions/applicationinsights-clickanalytics-js/scripts/publishAzReleaseToCdn.ps1 | Routes preview artifacts to next/ext. |
| common/publish/Tests/CdnPublishing.tests.ps1 | Adds offline routing, activation, and channel checks. |
| AISKU/Tests/Unit/src/applicationinsights.e2e.tests.ts | Points the live CDN monitor at next. |
| AISKU/scripts/setAzActiveCdnVersion.ps1 | Restricts Web SDK preview activation to next. |
| AISKU/scripts/README.md | Documents routing, regression tests, and rollout requirements. |
| AISKU/scripts/publishAzReleaseToCdn.ps1 | Publishes Web SDK previews only to next. |
| .github/workflows/ci.yml | Runs the offline CDN regression tests. |
Review effort: Balanced
Drop beta release inputs, npm tag generation, CDN routing and listing options, and beta CI branch triggers. Validate supported release types before publishing or activation, including npm packaging and latest-tag promotion. Keep deployed CDN files and historical release records unchanged. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Restore the pre-cleanup beta Git-branch filters for CI and CodeQL while retaining CDN migration, release-type retirement, and the added regression CI steps. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Restore npm prerelease tags, version generation and unrelated release guidance while retaining CDN routing and its regression coverage. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Describe next-only preview publishing and retired beta CDN options without changing npm versions or tags. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Jackson Weber (JacksonWeber)
approved these changes
Nov 4, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Use
nextas the writable preview CDN channel instead ofbeta.nextand their existing production destinations. Publish release candidates and beta prerelease artifacts only tonext, retaining-betaversion names and npm tags.ai_test.config.*prefix for beta configuration artifacts and activate those test aliases innext, without changing release configuration aliases.betatonext. The documentation site's SDK and config already usenext.Validation
next/ai.3.gbl.min.jsendpoint returns HTTP 200 with a nonempty body and the expected content-type and SDK metadata headers.npm run lint-fixcould not complete locally: dependency restoration fails because the repository-pinnedpnpm@10.34.5is unavailable from the configured registry. No dependency or version manifests were changed.Rollout
Use freshly built release artifacts: deployment pipelines execute the publishing and activation scripts bundled in the artifacts, so older artifacts can still write to beta.
Related shared Application Insights/1DS deployment pipeline change: https://msazure.visualstudio.com/One/_git/1DS.JavaScript/pullrequest/17088929