Skip to content

chore(deps): normalize locked npm registry sources - #3381

Merged
M4n5ter merged 1 commit into
mainfrom
chore/normalize-npm-lock-registry
Aug 21, 2026
Merged

chore(deps): normalize locked npm registry sources#3381
M4n5ter merged 1 commit into
mainfrom
chore/normalize-npm-lock-registry

Conversation

@M4n5ter

@M4n5terM4n5ter commented Aug 21, 2026•
edited
Loading

Copy link
Copy Markdown
Member

Summary

Replace six stale Microsoft 1ES proxy resolutions with their canonical npm registry tarballs. Package names and versions remain unchanged; integrity metadata is refreshed to npm-published SHA-512 digests.

Fixes#3356

Verification

  • npx --yes npm@11.19.0 ci --ignore-scripts
  • npm query ':type(remote)' --json
  • Confirmed every HTTP(S) package resolution in package-lock.json uses registry.npmjs.org
  • git diff --check

AI use

Select exactly one:

  • No generative tool made a substantive contribution
  • Generative tooling made a substantive contribution

Tool(s) and scope: OpenAI Codex assisted the dependency-source analysis and prepared the mechanical lockfile update. The human contributor will review the change and remains responsible for it.

Checklist

  • Tests cover the change and fail without it — not applicable to a resolution-metadata-only change
  • Lint, format, typecheck and the affected suites pass locally — clean installation and lockfile checks pass; source checks are unaffected

Does this PR entail a change in behavior?

  • Yes — described under Summary above
  • No

@M4n5ter
chore(deps): normalize locked npm registry sources
9aaad74
Replace stale Microsoft 1ES proxy resolutions with the canonical npm registry tarballs while preserving the exact package versions. Refresh their integrity metadata to npm-published SHA-512 digests so clean installs no longer depend on an unrelated proxy.
Generated-by: Codex
@M4n5ter
M4n5ter marked this pull request as ready for review August 21, 2026 07:09
Astro-Han
Astro-Han approved these changes Aug 21, 2026
View reviewed changes

@Astro-HanAstro-Han left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@M4n5ter
M4n5ter merged commit 02153fb into mainAug 21, 2026
2 of 3 checks passed
@M4n5ter
M4n5ter deleted the chore/normalize-npm-lock-registry branch August 21, 2026 07:23
sosyz pushed a commit to sosyz/maka that referenced this pull request Aug 27, 2026
@M4n5ter@sosyz
chore(deps): normalize locked npm registry sources (apache#3381)
5c2e4f4
Replace stale Microsoft 1ES proxy resolutions with the canonical npm registry tarballs while preserving the exact package versions. Refresh their integrity metadata to npm-published SHA-512 digests so clean installs no longer depend on an unrelated proxy.
Generated-by: Codex
sosyz pushed a commit to sosyz/maka that referenced this pull request Aug 30, 2026
@M4n5ter@sosyz
chore(deps): normalize locked npm registry sources (apache#3381)
5c86ccb
Replace stale Microsoft 1ES proxy resolutions with the canonical npm registry tarballs while preserving the exact package versions. Refresh their integrity metadata to npm-published SHA-512 digests so clean installs no longer depend on an unrelated proxy.
Generated-by: Codex
sosyz pushed a commit to sosyz/maka that referenced this pull request Aug 30, 2026
@M4n5ter@sosyz
chore(deps): normalize locked npm registry sources (apache#3381)
b1e3eea
Replace stale Microsoft 1ES proxy resolutions with the canonical npm registry tarballs while preserving the exact package versions. Refresh their integrity metadata to npm-published SHA-512 digests so clean installs no longer depend on an unrelated proxy.
Generated-by: Codex
sosyz pushed a commit to sosyz/maka that referenced this pull request Aug 30, 2026
@M4n5ter@sosyz
chore(deps): normalize locked npm registry sources (apache#3381)
881be43
Replace stale Microsoft 1ES proxy resolutions with the canonical npm registry tarballs while preserving the exact package versions. Refresh their integrity metadata to npm-published SHA-512 digests so clean installs no longer depend on an unrelated proxy.
Generated-by: Codex
@sosyzsosyz mentioned this pull request Aug 30, 2026
Merged
6 tasks
YayoiNanoka pushed a commit that referenced this pull request Aug 30, 2026
@sosyz@claude@M4n5ter
fix(desktop): show the Codex device sign-in code on connection-detail…
2cb1044
… re-login (#3358)
* fix(desktop): show the Codex device sign-in code on connection-detail re-login
The connection detail sheet's re-login notice drives the same
browser-assisted OAuth flow as the provider catalog panel, but never
rendered the flow's stateHint. For Codex that hint is the 9-digit device
user code the authorization page requires — the verification URL does not
embed it — so a re-login started from the notice could never be completed.
- OAuthLoginService gains showsDeviceCode: true for Codex, false for xAI,
whose page needs no manual code (mirrors the catalog panel's !isXai
guard). The mapping stays in use-connection-detail so the legacy AppShell
closure gains no file and no dependency.
- OAuthReloginNotice appends the sign-in code to the banner description
while authorization is pending, reusing the catalog's deviceCode copy.
Fixes#3357
Generated-by: Claude Code (Fable 5)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* chore(deps): normalize locked npm registry sources (#3381)
Replace stale Microsoft 1ES proxy resolutions with the canonical npm registry tarballs while preserving the exact package versions. Refresh their integrity metadata to npm-published SHA-512 digests so clean installs no longer depend on an unrelated proxy.
Generated-by: Codex
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Wang <m4n5terrr@gmail.com>
saltand pushed a commit to saltand/maka-agent that referenced this pull request Aug 31, 2026
@sosyz@claude
@M4n5ter@saltand
fix(desktop): show the Codex device sign-in code on connection-detail…
dbadda5
… re-login (apache#3358)
* fix(desktop): show the Codex device sign-in code on connection-detail re-login
The connection detail sheet's re-login notice drives the same
browser-assisted OAuth flow as the provider catalog panel, but never
rendered the flow's stateHint. For Codex that hint is the 9-digit device
user code the authorization page requires — the verification URL does not
embed it — so a re-login started from the notice could never be completed.
- OAuthLoginService gains showsDeviceCode: true for Codex, false for xAI,
whose page needs no manual code (mirrors the catalog panel's !isXai
guard). The mapping stays in use-connection-detail so the legacy AppShell
closure gains no file and no dependency.
- OAuthReloginNotice appends the sign-in code to the banner description
while authorization is pending, reusing the catalog's deviceCode copy.
Fixesapache#3357
Generated-by: Claude Code (Fable 5)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* chore(deps): normalize locked npm registry sources (apache#3381)
Replace stale Microsoft 1ES proxy resolutions with the canonical npm registry tarballs while preserving the exact package versions. Refresh their integrity metadata to npm-published SHA-512 digests so clean installs no longer depend on an unrelated proxy.
Generated-by: Codex
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Wang <m4n5terrr@gmail.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Astro-HanAstro-HanAstro-Han approved these changes
@hqhq1025hqhq1025Awaiting requested review from hqhq1025
@likun666661likun666661Awaiting requested review from likun666661

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

npm ci fails with EALLOWREMOTE: six package-lock.json entries resolve to ms-feed-*.pkgs.visualstudio.com instead of registry.npmjs.org

2 participants

@M4n5ter@Astro-Han