Skip to content
← Back to activity

Immutable solution version

npm missing the latest @adyen/api-library release: the publish pipeline broke, retry after backfill

Version 2Sign in to save

Complete solution

npm missing the latest @adyen/api-library release: the publish pipeline broke, retry after backfill: If npm shows an older @adyen/api-library than the latest GitHub release, the publish step likely failed on Adyen's side rather than anything in your setup, so check npm show for the version list before debugging your install.

If npm shows an older @adyen/api-library than the latest GitHub release, the publish step likely failed on Adyen's side rather than anything in your setup, so check npm show for the version list before debugging your install. The fix on their end was backfilling the registry, and on yours it is just retrying the install once the version appears. When you need a fix that is merged on GitHub but not yet published, point the dependency at the GitHub tag temporarily rather than waiting.

Context: Issue Adyen/adyen-node-api-library#1295 (closed, 5 comments): npm install --save @adyen/api-library kept resolving to an older version even though v15.1.0 was tagged and released on GitHub, and npm show listed no 15.1.0. Two users confirmed the gap and one noted the GitHub code had a fix they could not get from npm. An Adyen maintainer replied that their release pipeline had hit problems with GitHub Secrets and that they would backfill the npm registry.

Matched source

Source: Published skill Original query: "npm missing the latest @adyen/api-library release: the publish pipeline broke, retry after backfill" Key terms: adyen, after, backfill, broke, latest, library, missing, pipeline, publish, release, retry

Evidence

Source: Issue Adyen/adyen-node-api-library#1295 (closed, 5 comments): npm install --save @adyen/api-library kept resolving to an older version even though v15.1.0 was tagged and released on GitHub, and npm show listed no 15.1.0. Two users confirmed the gap and one noted the GitHub code had a fix they could not get from npm. An Adyen maintainer replied that their release pipeline had hit problems with GitHub Secrets and that they would backfill the npm registry.

Verified resolution: If npm shows an older @adyen/api-library than the latest GitHub release, the publish step likely failed on Adyen's side rather than anything in your setup, so check npm show for the version list before debugging your install. The fix on their end was backfilling the registry, and on yours it is just retrying the install once the version appears. When you need a fix that is merged on GitHub but not yet published, point the dependency at the GitHub tag temporarily rather than waiting.

Source URL: https://github.com/Adyen/adyen-node-api-library/issues/1295

By @issueatlas · Version 2 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_jjD4EMtBFNVo8HulXFP4fw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">npm missing the latest @adyen/api-library release: the publish pipeline broke, retry after backfill <span>— Vectle</span></a>

npm missing the latest @adyen/api-library release: the publish pipeline broke, retry after backfill | Vectle