Replies: 1 comment 2 replies
-
|
Hey @monishcm We are saying a huge drop of incoming events. Is that an expected change due to the optimizations you are making? |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
You should not see any change till 29th May as the old APIs will continue till then. This could well be an operational issue, and you can always ping our support if it is really a problem. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the quick response. We are investigating and will contact support if we believe it's an issue. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Overview
As part of our ongoing improvements, we are making changes to our replication API services. This is to ensure availability and performance of our feeds. Moving forward, only a limited set of API endpoints will be supported. Additionally, requests to
skimdb.npmjs.comwill now be redirected toreplicate.npmjs.comvia a301 Moved Permanentlyresponse. All other endpoints will be deprecated and return a404 Not Foundresponse.To facilitate a seamless transition, the new endpoints will be available starting
Tuesday, March 18, 2025 (12:00 UTC), operating in parallel with the existing endpoints. The existing endpoints will be fully deprecated onThursday, May 29, 2025 (12:00 UTC). During the transition period, you may access the new endpoints by including thenpm-replication-opt-inheader with the valuetruein your requests (wherein they will be ignored thereafter)Supported Endpoints
Going forward, the following API endpoints will be supported (with some limitations):
GET https://replicate.npmjs.com/registry/_changesGET/POST https://replicate.npmjs.com/registry/_all_docsHEAD/GET https://replicate.npmjs.com/Changes and Limitations
Each supported endpoint will now have a limited set of supported parameters. Requests using unsupported parameters will not function as expected.
_changesEndpointThe
_changesendpoint will continue to function for paginating through package changes. The following parameters will be supported:Supported Parameters
doc_idsdescendinglast-event-id(andLast-Event-IDheader)limitsinceDeprecated Parameters
The following parameters will no longer be supported:
conflictsfeedfilterheartbeatinclude_docsattachmentsatt_encoding_infostyletimeoutviewseq_intervalBehavioral Changes
doc_idswill now behave as iffilter=_doc_idsis also supplied.feedwill behave as ifnormalwas passed.stylewill behave as ifmain_onlywas passed._all_docsEndpointThe
_all_docsendpoint will continue to support bothGETandPOSTmethods for paginating through packages in the registry.Supported Parameters
descendingendkey,end_key,endkey_docid,end_key_doc_idstartkey,start_key,startkey_docid,start_key_doc_idinclusive_endkeykeyslimitskipsortedDeprecated Parameters
The following parameters will no longer be supported:
conflictsgroupgroup_levelinclude_docsattachmentsatt_encoding_inforeducestablestaleupdateupdate_seqRoot Endpoint (
/)The root endpoint will continue to supply the following parameters in JSON output:
db_nameenginedoc_countupdate_seqImportant Notes
include_docsDeprecation and Direct packument AccessThe
include_docsparameter will not be supported in any endpoint. Users should instead fetch package metadata directly fromhttps://registry.npmjs.org/<package-name>to ensure consistency.Note: Users should transition from fetching package metadata from
https://replicate.npmjs.com/tohttps://registry.npmjs.org/<package-name>.https://replicate.npmjs.com/will no longer be supported for fetching packuments.limitParameterThe
limitparameter will have a default value of 1000 and a maximum value of 10000 across all endpoints.Streaming Responses
Support for streaming responses via
feed=longpoll,feed=continuous, andfeed=eventsourcewill be removed. Users should implement manual pagination using sequence IDs via thesinceparameter.Migration Steps
https://replicate.npmjs.com/registry/instead ofskimdb.npmjs.com/.https://registry.npmjs.org/<package_name>instead ofinclude_docsfor retrieving package metadata.since.limitvalues in requests adhere to the new default (1000) and maximum (10000) constraints.Timelines for the migration
The newly migrated endpoints will be accessible beginning
Tuesday, March 18, 2025 (12:00 UTC). These endpoints will operate concurrently with the existing endpoints until the latter are deprecated onThursday, May 29, 2025 (12:00 UTC). To access the new endpoints, please include thenpm-replication-opt-inheader with the valuetruein your requests (the header will be ignored thereafter).Brownout Phases for Testing
A series of brownout phases will begin on
Wednesday, April 02, 2025 (12:00 UTC), and continue until the complete deprecation of the old endpoints onThursday, May 29 , 2025 (12:00 UTC). During this period, deprecated endpoints will be intermittently blocked. To avoid disruptions, you can access the new endpoints by including thenpm-replication-opt-inheader with the valuetruein your requests (untilThursday, May 29, 2025 (12:00 UTC)wherein the header will be ignored thereafter).The Brownout is phased into 3 blocks.
The planned schedule is as follows:
Phase 1:
April 2 to April 22 (21 days)- Recurring periods of2 hoursof unavailability from12:00 UTC, followed by2 hoursof availabilityPhase 2:
April 23 to May 13 (21 days)- Recurring periods of4 hoursof unavailability from12:00 UTC, followed by2 hoursof availabilityPhase 3:
May 14 to May 29 (16 days)- Recurring periods of10 hoursof unavailability from12:00 UTC, followed by2 hoursof availabilityWe strongly recommend using this transition period to test your updated replication implementations and provide feedback.
Additional Support
For more details, join the discussion in this post (literally this post 😄). This is the go-to place for questions and comments. If you have specific questions or need assistance, please reach out to our support team.
Thank you for your cooperation as we work to enhance the replication API experience!
Beta Was this translation helpful? Give feedback.
All reactions