Skip to content

Pull Pylance with Pyright 1.1.412 - #11639

Open
Bill Schnurr (bschnurr) wants to merge 1 commit into
mainfrom
pull-pylance-with-pyright-1.1.412-20260814-194602
Open

Pull Pylance with Pyright 1.1.412#11639
Bill Schnurr (bschnurr) wants to merge 1 commit into
mainfrom
pull-pylance-with-pyright-1.1.412-20260814-194602

Conversation

@bschnurr

Copy link
Copy Markdown
Member

No description provided.

@rchiodo

Rich Chiodo (rchiodo) commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

🔒 Automated review in progress — Rich Chiodo (@rchiodo) is auto-reviewing this PR.

displayName: pnpm install
inputs:
script: npm run install:all
script: pnpm run install:all

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Warning · Non-blocking recommendation

Azure invokes ambient pnpm despite package.json pinning pnpm@10.12.2, unlike GitHub's explicit setup. Activate the pinned package manager after Node setup in both build and release pipelines.

working-directory: ${{ inputs.working-directory }}
env:
NPM_CONFIG_REGISTRY: https://registry.npmjs.org/
run: pnpm run install:all

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Warning · Non-blocking recommendation

This action accepts arbitrary working-directory values but runs pnpm run install:all, which only works where that script exists; the CFS action runs pnpm install directly. Use the same install command or narrow the advertised directory contract.

@rchiodo Rich Chiodo (rchiodo) left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Approved via Review Center.

@rchiodo Rich Chiodo (rchiodo) added the review-auto:approved Automated review: no blocking findings (approval posted). label Aug 14, 2026
working-directory: ${{ inputs.working-directory }}
env:
NPM_CONFIG_REGISTRY: https://registry.npmjs.org/
run: pnpm run install:all

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Warning · Non-blocking recommendation

The public-registry path runs pnpm run install:all, while the CFS path runs pnpm install; package-scoped working directories without an install:all script therefore have a different contract and may break fork builds. Use the same frozen-lockfile install command in both paths, varying only authentication and registry configuration.

@rchiodo Rich Chiodo (rchiodo) left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Approved via Review Center.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Approved via Review Center.

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

Labels

review-auto:approved Automated review: no blocking findings (approval posted).

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants