@verdaccio/e2e-ui@2.7.0

Minor Changes

• 661fe1f: Second wave of feature-gated coverage, closing the e2e gaps left by the verdaccio/verdaccio#6210 bug batch:

  • publishPackage task accepts a manifest override merged into the generated package.json, enabling fixtures with the manifest shapes real packuments carry (string repository, funding arrays, contributors without email, …)
  • manifestRenderingTests — repository rendered as a browsable https link (git:// rewrite), funding array, bugs url, sidebar gravatars and email-less contributors surviving dedupe
  • sessionTests — an expired token in localStorage boots the UI logged out (default on) and is purged from storage (probe)
  • detailTests gains a stale-state probe: the versions tab must show the current package after SPA navigation
  • failureModeTests gains search-5xx (error instead of "no results found") and failed-tarball-download (error snackbar instead of silence) probes
  • settingsTests gains a dayjs-locale probe: relative dates must follow the selected language

  Probes default false (they need the #6210 fixes); everything else runs against released lines. Validated green against published verdaccio@6 with defaults and 19/19 with every probe enabled against a #6210 master build.

• 661fe1f: second wave of coverage: session token lifecycle suite (expired stored token boots logged out, optional purge probe), manifest-rendering suite (string/array repository, funding, bugs and email-less contributors), publishPackage task accepts manifest overrides, and new feature-gated probes in the detail, failure-modes and settings suites.

  Also makes the change-password wrong-old-password assertion text-agnostic: the error banner wording differs across verdaccio lines (published ui-theme shows "Failed to change password", master surfaces the server message via authErrorMessage), so it now asserts a non-empty banner rather than an exact string, while still failing on the raw "Cannot PUT" 404 that means the reset_password route was not registered.

@verdaccio/e2e-cli@3.2.1

Patch Changes

• ba3d48a: Make scenario:minimum-release-age compatible with pnpm 12:

  • pnpm 12's argument parser rejects the --frozen-lockfile=false form; the
    blocked-install phase now uses --no-frozen-lockfile, accepted by pnpm 10,
    11 and 12.
  • pnpm 12 no longer blocks new direct dependencies by default — it auto-adds
    them to minimumReleaseAgeExclude and proceeds. The scenario now sets
    minimumReleaseAgeStrict: true (ignored by pnpm 11) so the cooldown keeps
    failing with ERR_PNPM_NO_MATURE_MATCHING_VERSION as asserted.

@verdaccio/e2e-ui@2.6.0

Minor Changes

• 2e03661: Four new feature-gated test suites, born from the verdaccio/verdaccio#6210 bug batch (30 UI bugs, most of them invisible to the previous e2e coverage):

  • detailTests — version-pinned /v/<version> urls and the wire format of the UI's data requests (scoped names must stay literal @scope/name, never %40-encoded; pins the regression these suites caught in #6210). versionNotFound probe for the new 404-on-unknown-version behavior.
  • failureModeTests — a dead backend must not look like a healthy empty registry, and a 5xx on the detail page must render an error state instead of a blank page (strict assertions gated as probes until #6210 ships).
  • i18nKeyTests — raw-i18n-key detector: no page may render untranslated keys like security.addUser.title; catches the whole "namespace missing from the bundle" class.
  • signupTests — the create-user flow end to end, including the PUT /-/verdaccio/sec/signup wire contract (36-char sessionId); gated as a probe because every published ui-theme posts to a URL that only serves the SPA.

  New errors.genericError testid group, signup selector group, and feature flags detail.*, failureModes.*, i18n.*, signup.* (probes default false, everything else true). Validated green against published verdaccio@6 with defaults and against a #6210 build with all probes enabled.

@verdaccio/e2e-cli@2.10.3

Patch Changes

• 7250c67: Update Yarn modern login tests for Verdaccio without incoming Basic authentication. The login scenario now treats duplicate legacy login as unsupported and uses fresh users for publish and switch-user checks.

@verdaccio/e2e-cli@3.0.0

Major Changes

• 90165cd: Refactor the e2e CLI internals to use the Rust runner while preserving the npm package entrypoint.

@verdaccio/e2e-ui@2.4.2

Patch Changes

• a439118: Remove the non-deterministic "no results" search test from searchTests.

  Verdaccio 7+ removed the searchRemote flag (verdaccio/verdaccio#5801), so the
  Web UI search now always queries configured uplinks. When the registry proxies
  to registry.npmjs.org, npm's /-/v1/search returns fuzzy/fallback matches for
  any non-empty text, so no query reliably yields an empty result and renders the
  autocomplete's "No results found" state. This made the empty-state assertion fail
  on next-7/next-9 (it only ever passed on 6.x, where search stayed local by
  default). The search flow stays covered by the remaining input/request/clear tests
  and the published-package result tests.

@verdaccio/e2e-cli@2.10.2

Patch Changes

• 513ed8d: fix: support npm 12 in e2e-cli

  npm 12 wraps npm info <pkg> --json output in a single-element array instead of
  a bare object, which made the info, deprecate and install-multiple-deps tests read
  an undefined package name. Added a normalizeInfo helper that unwraps the array
  (backward-compatible with older npm).

  Also pin min-release-age=0 in the generated project .npmrc so npm 12's new
  release-age cooldown — if set in a developer's global ~/.npmrc — no longer rejects
  the freshly published packages the tests install.

@verdaccio/e2e-cli@2.10.1

Patch Changes

• c855e2c: Remove the star/unstar CLI e2e test

  The star test (covering both starring and unstarring a package) has been removed, along with the star/stars/unstar command capabilities from the npm and pnpm adapters and the related documentation.

@verdaccio/e2e-cli@2.10.0

Minor Changes

• 5a179ad: Add a pnpm scenario testing minimumReleaseAge with minimumReleaseAgeExclude

  A new scenario:minimum-release-age exercises pnpm's release-age cooldown (minimumReleaseAge: 10080) together with minimumReleaseAgeExclude (@verdaccio/*, verdaccio-*). It verifies that excluded packages install despite being freshly published while a non-excluded fresh package is blocked by the cooldown. The scenario is gated via a new appliesTo predicate on TestDefinition to pnpm 11.1.0+ (the cooldown is silently ignored in 11.0.x) and is skipped for other package managers.

@verdaccio/e2e-cli@2.9.0

Minor Changes

• d788be0: feat: disable hardened mode for yarn 4