NPM package deprecation

[leon-vg]

Select Topic Area

Product Feedback

Body

At our company, we use GitHub packages as our primary internal packages repository for NPM packages.

In the lifecycle of a package, it is important to be able to signal that a package has been deprecated. NPM has the npm deprecate command, but this does not seem to work with GitHub packages. See this Stack Overflow question for an example.

It would be great if this ability would be supported by GitHub packages!

[liam1uphealth]

Massive +1 here. I am fairly confused by the omissions of un-publishing or deprecating a component. Are we expected to just leave versions of components with bugs live? Or delete a repository every single time a bug is introduced in a certain version and recreate the library?

[tmadej]

+1. This would be very useful in a lot of scenarios and critical in both:

• larger private enterprise teams, or
• an open source package with a lot of consumers across many versions

I see that you mentioned there are no guarantees. When can we expect this to be prioritized on the roadmap or at least discussed to be considered?

[ettaboyle]

Thanks for the original post @leon-vg and additional comment @markscamilleri 👋🏻

This community is managed by GitHub employees, but there is no SLA or guarantee each post will get a response from a community manager or product leader.

As this discussion provided product feedback or a feature request we encourage you to review the "Making Suggestions" guidelines in the repo readme including: "Once you kick off a discussion, the GitHub product team will evaluate the feedback but will not be able to respond to every submission."

That being said, I was to emphasize that we appreciate your feedback and your valuable input. We want to be transparent about our current priorities. You can gain insights into the projects we’re currently focusing on for the upcoming year by checking our public roadmap. While smaller fixes may not always be explicitly listed, they often get addressed when related work is in progress.

Regarding your specific request, it’s important to note that it’s not actively being worked on at the moment. However, this doesn’t mean we won’t consider it in the future; it’s simply not on our development roadmap right now.
We’d like to emphasize that as a valued GitHub user, your feedback in this Discussion space, along with appropriate tags and examples, plays a crucial role in shaping the development of GitHub. While we can’t guarantee immediate action on every piece of feedback, please rest assured that we are attentive to your suggestions and continuously strive to enhance the GitHub experience.
While we do review all incoming feedback unfortunately due to the volume of feedback, we may not be able to respond to each one individually at this time. However, we strongly encourage you to continue providing your valuable input as it greatly helps us prioritize and improve GitHub.

Your contributions are instrumental in making GitHub better for all users. Thank you for taking the time to share your thoughts with us, even if the particular request is not currently in active development. Your input is truly valuable and contributes to the continuous improvement of GitHub.

Thank you for contributing and continuing to support other users in the GitHub Community Discussions.

[markscamilleri]

Stumbled across this while trying to solve this same issue. I'm genuinely surprised how there hasn't been traction on this yet ☹️

[liam1uphealth]

Same, this seems like essential functionality for components