Loading workspace insights... Statistics interval
7 days30 daysLatest CI Pipeline Executions
89e616bc fix(core): degrade cooldown-blocked dist-tags within their own channel
Under an active package-manager minimum-release-age policy, resolving a
too-new dist-tag during nx migrate could land on a nonsensical version.
`nx migrate next` degraded to an internal `pr.*` build or an ancient
release candidate, and the npm path diverged from what npm itself
resolves. Each package-manager emulation had its own tag-degrade logic,
and npm's admitted same-line prereleases from other channels.
Dist-tag degrade is now a single rule shared by npm, pnpm, yarn, and bun:
when the resolved tag target is too new, pick the newest compliant version
at or below it that is either stable or in the target's own prerelease
channel. A stable tag falls back to the latest compliant stable; a
prerelease tag keeps a compliant same-line version when one exists and
otherwise drops to stable, never crossing into an internal `pr` build or
an older release line.
Removes the now-dead per-PM degrade code (pnpm's deprecation tie-break,
yarn's walk-down, bun's channel filter, the latestTagDegrade axis) and the
tests that pinned the old version-specific behavior. Also isolates the npm
policy-reader specs from the host's real ~/.npmrc. 89e616bc fix(core): degrade cooldown-blocked dist-tags within their own channel
Under an active package-manager minimum-release-age policy, resolving a
too-new dist-tag during nx migrate could land on a nonsensical version.
`nx migrate next` degraded to an internal `pr.*` build or an ancient
release candidate, and the npm path diverged from what npm itself
resolves. Each package-manager emulation had its own tag-degrade logic,
and npm's admitted same-line prereleases from other channels.
Dist-tag degrade is now a single rule shared by npm, pnpm, yarn, and bun:
when the resolved tag target is too new, pick the newest compliant version
at or below it that is either stable or in the target's own prerelease
channel. A stable tag falls back to the latest compliant stable; a
prerelease tag keeps a compliant same-line version when one exists and
otherwise drops to stable, never crossing into an internal `pr` build or
an older release line.
Removes the now-dead per-PM degrade code (pnpm's deprecation tie-break,
yarn's walk-down, bun's channel filter, the latestTagDegrade axis) and the
tests that pinned the old version-specific behavior. Also isolates the npm
policy-reader specs from the host's real ~/.npmrc. 89e616bc fix(core): degrade cooldown-blocked dist-tags within their own channel
Under an active package-manager minimum-release-age policy, resolving a
too-new dist-tag during nx migrate could land on a nonsensical version.
`nx migrate next` degraded to an internal `pr.*` build or an ancient
release candidate, and the npm path diverged from what npm itself
resolves. Each package-manager emulation had its own tag-degrade logic,
and npm's admitted same-line prereleases from other channels.
Dist-tag degrade is now a single rule shared by npm, pnpm, yarn, and bun:
when the resolved tag target is too new, pick the newest compliant version
at or below it that is either stable or in the target's own prerelease
channel. A stable tag falls back to the latest compliant stable; a
prerelease tag keeps a compliant same-line version when one exists and
otherwise drops to stable, never crossing into an internal `pr` build or
an older release line.
Removes the now-dead per-PM degrade code (pnpm's deprecation tie-break,
yarn's walk-down, bun's channel filter, the latestTagDegrade axis) and the
tests that pinned the old version-specific behavior. Also isolates the npm
policy-reader specs from the host's real ~/.npmrc. 78e252d2 fix(core): degrade cooldown-blocked dist-tags within their own channel
Under an active package-manager minimum-release-age policy, resolving a
too-new dist-tag during nx migrate could land on a nonsensical version.
`nx migrate next` degraded to an internal `pr.*` build or an ancient
release candidate, and the npm path diverged from what npm itself
resolves. Each package-manager emulation had its own tag-degrade logic,
and npm's admitted same-line prereleases from other channels.
Dist-tag degrade is now a single rule shared by npm, pnpm, yarn, and bun:
when the resolved tag target is too new, pick the newest compliant version
at or below it that is either stable or in the target's own prerelease
channel. A stable tag falls back to the latest compliant stable; a
prerelease tag keeps a compliant same-line version when one exists and
otherwise drops to stable, never crossing into an internal `pr` build or
an older release line.
Removes the now-dead per-PM degrade code (pnpm's deprecation tie-break,
yarn's walk-down, bun's channel filter, the latestTagDegrade axis) and the
tests that pinned the old version-specific behavior. Also isolates the npm
policy-reader specs from the host's real ~/.npmrc. 5004d81b fix(core): degrade cooldown-blocked dist-tags within their own channel
Under an active package-manager minimum-release-age policy, resolving a
too-new dist-tag during nx migrate could land on a nonsensical version.
`nx migrate next` degraded to an internal `pr.*` build or an ancient
release candidate, and the npm path diverged from what npm itself
resolves. Each package-manager emulation had its own tag-degrade logic,
and npm's admitted same-line prereleases from other channels.
Dist-tag degrade is now a single rule shared by npm, pnpm, yarn, and bun:
when the resolved tag target is too new, pick the newest compliant version
at or below it that is either stable or in the target's own prerelease
channel. A stable tag falls back to the latest compliant stable; a
prerelease tag keeps a compliant same-line version when one exists and
otherwise drops to stable, never crossing into an internal `pr` build or
an older release line.
Removes the now-dead per-PM degrade code (pnpm's deprecation tie-break,
yarn's walk-down, bun's channel filter, the latestTagDegrade axis) and the
tests that pinned the old version-specific behavior. Also isolates the npm
policy-reader specs from the host's real ~/.npmrc.