Skip to content

chore(instrumentation-restify)!: remove package restify - #3658

Open
fiyinfoluwa001 wants to merge 1 commit into
open-telemetry:mainfrom
fiyinfoluwa001:drop-instrumentation-restify
Open

chore(instrumentation-restify)!: remove package restify#3658
fiyinfoluwa001 wants to merge 1 commit into
open-telemetry:mainfrom
fiyinfoluwa001:drop-instrumentation-restify

Conversation

@fiyinfoluwa001

Copy link
Copy Markdown

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?

restify is no longer maintained (last release was in 2023), and restify@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

  • Deletes the packages/instrumentation-restify package entirely
  • Removes it from auto-instrumentations-node (dependency, import, map entry, README)
  • Removes it from release-please-config.json and .release-please-manifest.json
  • Removes it from .github/component-label-map.yml and .github/component_owners.yml

Closes : open-telemetry/opentelemetry-js#6875

@trentm

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
@fiyinfoluwa001
fiyinfoluwa001 requested review from a team as code owners August 6, 2026 12:20
@github-actions github-actions Bot added pkg:instrumentation-restify pkg:auto-instrumentations-node pkg-status:unmaintained This package is unmaintained. Only bugfixes may be acceped until a new owner has been found. labels Aug 6, 2026
@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Welcome, contributor! Thank you for your contribution to opentelemetry-js-contrib.

Important reminders:

  • Read our Contributing Guidelines.
  • Sign the CLA if you haven't already.
  • Follow the OpenTelemetry Generative AI policy: disclose any AI use in your contribution, and communicate (PR descriptions, review replies) in your own words rather than AI-generated text.
  • Give reviewers at least a few days before pinging them for feedback.
  • If you need help with general setup, development process, or contributor etiquette, ask in #opentelemetry-new-contributors.

@opentelemetry-pr-dashboard

opentelemetry-pr-dashboard Bot commented Aug 6, 2026

Copy link
Copy Markdown

Pull request dashboard status

Waiting 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):

  • Top-level threads: 1
Status above doesn't look right?
  • Just replied or pushed? Anything around or after the refresh time above may not be picked up yet — give it a few minutes.
  • Should this be with reviewers? Comment /dashboard route:reviewers to route it to them.
  • Anything wrong — including the routing? Report it with what you expected; it helps us improve the dashboard.

@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

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.
Are you familiar with this package? Consider becoming a component owner.

@aryamohanan

Copy link
Copy Markdown
Contributor

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 main and include it in the v3 release? Just curious to understand the plan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pkg:auto-instrumentations-node pkg:instrumentation-restify pkg-status:unmaintained:autoclose-scheduled pkg-status:unmaintained This package is unmaintained. Only bugfixes may be acceped until a new owner has been found.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

drop instrumentation-restify in SDK 3.0

6 participants