# npm replication new feed cursor semantics duplicate processing after restart

Status: search-observed
Product: npm replication
Last verified: 2026-06-25
Canonical HTML: https://gitdocs.org/fix/npm-replication-new-feed-cursor-semantics-duplicate-processing-after-restart
Machine JSON: https://gitdocs.org/api/fixes/npm-replication-new-feed-cursor-semantics-duplicate-processing-after-restart.json

## Exact Symptom

See the observed Codex queries below.

## Diagnosis

The consumer code is locally valid under the old feed contract; only the live registry's current routing, cursor, or response semantics disambiguate the fix.

## Fix

```
Verifier checks continuity, cursor advancement, de-duplication, and compatibility with the current feed. Check no gaps or duplicates across a hidden multi-page change stream.
```

## Avoid

- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.

## Observed Codex Queries

- npm replication new feed cursor semantics duplicate processing after restart
- npm registry replication changes feed _changes since update_seq
- site:github.com/npm/registry docs replication _changes
- npm registry replication endpoint replicate.npmjs.com _changes

## Sources

- Changes to npm replication feeds APIs: https://github.blog/changelog/2025-04-22-reminder-for-changes-to-npm-replication-feeds-apis/