docs(contributing): note npm CFS proxy for Microsoft-managed devices#638
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds contributor-facing documentation to help developers on Microsoft-managed devices successfully install npm dependencies when direct access to registry.npmjs.org is blocked, by pointing them to Central Feed Services (CFS) guidance.
Changes:
- Adds a new “npm Registry (Microsoft-managed devices)” section to clarify managed-device behavior vs. external contributors.
- Documents how to verify the current npm registry configuration and where to find CFS setup instructions.
- Notes the distinction between device-level rerouting and repo-level build pipeline onboarding.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Direct access to registry.npmjs.org is blocked on Microsoft-managed devices. Add guidance pointing contributors to the CFS proxy setup at aka.ms/CFS, while clarifying external contributors are unaffected and that repo-level CFS onboarding is handled in the build pipeline. Co-authored-by: Copilot <[email protected]> Copilot-Session: 75223766-eb7f-4146-9d06-2c4e1e22f42e
Co-authored-by: Copilot <[email protected]> Copilot-Session: 75223766-eb7f-4146-9d06-2c4e1e22f42e
corinagum
force-pushed
the
cg/npm-registry-docs
branch
from
July 10, 2026 22:23
1e118d7 to
7623e79
Compare
heyitsaamir
approved these changes
Jul 14, 2026
Merged
lilyydu
added a commit
that referenced
this pull request
Jul 16, 2026
## Release v2.0.14
Prepares the stable **2.0.14** release by merging `main` into `release`
and setting `version.json` to the stable version (removing the
`-preview.{height}` suffix).
- Previous release: `2.0.13` (published 2026-06-15)
- Only functional diff vs `main` is `version.json`:
`2.0.14-preview.{height}` → `2.0.14`
## What's in this release
### 🚀 Features
* Flatten client method chains to reduce call hops by @lilyydu in
#634
* Support resetting response streams and streaming error handling by
@lilyydu in #635
* Add `extendedMarkdown` text format value by @singhk97 in
#615
### 🐛 Fixes
* Set `replyToId` for all streaming activities by @lilyydu in
#646
* Use `artifactName` for pipelineArtifact inputs in publish pipeline by
@corinagum in #625
### ♻️ Refactors
* Move `apps` from file-based mixins to real classes by @heyitsaamir in
#633
* Split up Outbound and Inbound Activities by @heyitsaamir in
#639
* Remove `ExperimentalTeamsQuotedReplies` markers by @corinagum in
#621
### 🧪 Tests
* Add integration tests for Teams TypeScript SDK by @corinagum in
#622
### 📚 Docs & Examples
* Migrate examples to the flattened conversation API by @lilyydu in
#637
* Note npm CFS proxy for Microsoft-managed devices by @corinagum in
#638
* Update integration test runbook link to ADO wiki by @corinagum in
#624
### 🔧 Chores & Dependencies
* Bump version to 2.0.14-preview and fix pipeline release job by
@corinagum in #620
* Bump hono from 4.12.21 to 4.12.25 by @dependabot in
#623
* Bump react-router from 7.15.0 to 7.15.1 by @dependabot in
#619
* Bump vite from 6.4.2 to 6.4.3 by @dependabot in
#617
**Full Changelog**:
v2.0.13...prep-release/2.0.14
### After merge
1. Trigger the [release
pipeline](https://dev.azure.com/DomoreexpGithub/Github_Pipelines/_build?definitionId=52&_a=summary)
on `release` with **Public** publish type
2. Bump `main` → `2.0.15-preview.{height}`
3. Create the `v2.0.14` git tag + GitHub Release
Co-authored-by: Copilot <[email protected]>
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.
What
Adds an "npm Registry (Microsoft-managed devices)" section to
CONTRIBUTING.MD.Why
Direct access to
registry.npmjs.orgis now blocked on Microsoft-managed devices; npm/pnpm/yarn must resolve through the org's Central Feed Services (CFS) proxy. Contributors on managed devices hitting install failures had no guidance in-repo.Notes