Skip to content

fix(build): Registry configuration mismatch yarn.lock uses pub (#34619)#34676

Merged
spbolton merged 1 commit intomainfrom
issue-34619-registry-configuration-mismatch-yarnlock-uses
Feb 18, 2026
Merged

fix(build): Registry configuration mismatch yarn.lock uses pub (#34619)#34676
spbolton merged 1 commit intomainfrom
issue-34619-registry-configuration-mismatch-yarnlock-uses

Conversation

@spbolton
Copy link
Contributor

@spbolton spbolton commented Feb 17, 2026

Description

Add core-web/.yarnrc to configure BunnyCDN as the npm registry, update yarn.lock to replace all 3,279 registry.yarnpkg.com resolved URLs with dotcms-npm.b-cdn.net so --frozen-lockfile uses CDN URLs from the lockfile, and remove the now-redundant pom.xml registry execution block that was ineffective due to --frozen-lockfile bypassing runtime registry config.

Changes

  • [List the main changes made]

Testing

  • [Describe testing approach]

Closes #34619

Issue: Registry configuration mismatch yarn.lock uses pub

This PR fixes: #34619

…4619)

Add core-web/.yarnrc to set the CDN registry as the source of truth for
all environments. Update yarn.lock to replace 3,279 registry.yarnpkg.com
resolved URLs with dotcms-npm.b-cdn.net so --frozen-lockfile uses the CDN.
Remove the now-redundant pom.xml registry execution block.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@github-actions github-actions bot added Area : CI/CD PR changes GitHub Actions/workflows Area : Frontend PR changes Angular/TypeScript frontend code labels Feb 17, 2026
@spbolton spbolton marked this pull request as ready for review February 17, 2026 16:52
@spbolton spbolton enabled auto-merge February 17, 2026 16:52
@spbolton spbolton removed the Area : CI/CD PR changes GitHub Actions/workflows label Feb 17, 2026
@spbolton spbolton added this pull request to the merge queue Feb 18, 2026
Merged via the queue into main with commit 93c5383 Feb 18, 2026
21 checks passed
@spbolton spbolton deleted the issue-34619-registry-configuration-mismatch-yarnlock-uses branch February 18, 2026 16:28
oidacra pushed a commit that referenced this pull request Feb 20, 2026
… (#34676)

Add core-web/.yarnrc to configure BunnyCDN as the npm registry, update
yarn.lock to replace all 3,279 registry.yarnpkg.com resolved URLs with
dotcms-npm.b-cdn.net so --frozen-lockfile uses CDN URLs from the
lockfile, and remove the now-redundant pom.xml registry execution block
that was ineffective due to --frozen-lockfile bypassing runtime registry
config.

- [ ] [List the main changes made]

- [ ] [Describe testing approach]

Closes #34619

**Issue:** Registry configuration mismatch yarn.lock uses pub

Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
dsolistorres pushed a commit that referenced this pull request Feb 20, 2026
… (#34676)

## Description

Add core-web/.yarnrc to configure BunnyCDN as the npm registry, update
yarn.lock to replace all 3,279 registry.yarnpkg.com resolved URLs with
dotcms-npm.b-cdn.net so --frozen-lockfile uses CDN URLs from the
lockfile, and remove the now-redundant pom.xml registry execution block
that was ineffective due to --frozen-lockfile bypassing runtime registry
config.

## Changes

- [ ] [List the main changes made]

## Testing

- [ ] [Describe testing approach]

Closes #34619

**Issue:** Registry configuration mismatch yarn.lock uses pub

Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area : Frontend PR changes Angular/TypeScript frontend code

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

Registry configuration mismatch: yarn.lock uses public registry despite CDN config

5 participants