Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to expire a pre-release package #5856

Closed
anangaur opened this issue Sep 6, 2017 · 5 comments
Closed

Ability to expire a pre-release package #5856

anangaur opened this issue Sep 6, 2017 · 5 comments
Assignees
Labels
Resolution:Duplicate This issue appears to be a Duplicate of another issue Type:Feature

Comments

@anangaur
Copy link
Member

anangaur commented Sep 6, 2017

Many times authors release beta packages for testing waters but they do not want users to continue working with these packages.

There should be a mechanism to put an expiry date on the beta packages after which NuGet restores should start warning users.

@anangaur anangaur self-assigned this Sep 6, 2017
@xavierdecoster
Copy link
Member

Could this be part of the Package Deprecation spec? We have an issue tracking that feature: #2867

@anangaur
Copy link
Member Author

anangaur commented Sep 7, 2017

#2867 looks similar. However, #2867 lets you deprecate a package at any point in time. This proposal is to have a time-bomb attached with the nupkg so that even the cached version would have the expiry and NuGet CLIs can warn once it expires.

@maartenba
Copy link
Contributor

Who knows, maybe I want to auto-update my v2 version when I publish v3 next Tuesday. (Or: perhaps they are indeed the same feature, with an enhanced scope in the current issue?)

@nkolev92
Copy link
Member

This seems like a high-cost low benefit thing tbh. Worth having a triage discussion over.

@anangaur
Copy link
Member Author

anangaur commented Nov 9, 2017

Closing this as duplicate of #2867

@anangaur anangaur closed this as completed Nov 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution:Duplicate This issue appears to be a Duplicate of another issue Type:Feature
Projects
None yet
Development

No branches or pull requests

4 participants