chore(instrumentation-restify)!: remove package restify - #3658
chore(instrumentation-restify)!: remove package restify#3658fiyinfoluwa001 wants to merge 1 commit into
Conversation
restify is no longer maintained (last release 2023) and restify@11 does not work with Node.js 24+. Removes the package and all references to it in auto-instrumentations-node and repo config files. Closes open-telemetry/opentelemetry-js#6875
|
Welcome, contributor! Thank you for your contribution to opentelemetry-js-contrib. Important reminders:
|
Pull request dashboard statusWaiting on the author · refreshed 2026-08-13 20:47 UTC Respond to 1 review item (e.g. link a commit, explain why not, ask a follow-up):
Status above doesn't look right?
|
|
This package does not have an assigned component owner and is considered unmaintained. As such this package is in feature-freeze and this PR will be closed with 14 days unless a new owner or a sponsor (a member of @open-telemetry/javascript-approvers) for the feature is found. It is the responsibility of the author to find a sponsor for this feature. |
|
This change intended for SDK v3? If so, how are we planning to handle the merge? Are we going to create a separate v3 branch, or merge this into |
Title
Restify is no longer maintained (last release 2023) and restify@11 does not work with Node.js 24+.
Which problem is this PR solving?
restifyis no longer maintained (last release was in 2023), andrestify@11(the latest major) does not work with Node.js 24+. Continuing to ship and maintain this instrumentation is not sustainable.This is part of the SDK 3.0 cleanup tracked in open-telemetry/opentelemetry-js#6875.
Short description of the changes
packages/instrumentation-restifypackage entirelyauto-instrumentations-node(dependency, import, map entry, README)release-please-config.jsonand.release-please-manifest.json.github/component-label-map.ymland.github/component_owners.ymlCloses : open-telemetry/opentelemetry-js#6875
@trentm