Feature Request: Enable package overwrites
See original GitHub issueDescribe the solution you’d like
An option to replace packages with matching version number would be nice. Right now, even with HardDelete
set, I still get 409 - conflict
when replacing the package. I read about the whole left-pad thing, and I understand it, but our organization’s needs are different. It would help if the UI allowed for proper package management, but I understand it is in early stages, and it is looking GREAT!
We are currently using phpNuget, which supports deletion and replacement, but we are seeing very slow activity in the development and are looking for other options.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
NuGet - disallow overwriting packages (with same name ...
My only concern is that I can publish a package with the same name and version number, thereby overwriting the existing package. This...
Read more >overwriting GeoJSON-based hosted feature service?
Solved: Hi everyone - I have a GeoJSON file that I loaded to ArcGIS Online as a hosted feature layer. The GeoJSON file...
Read more >Allow manifest.json to request a version lower than the ...
By definition, this means all project dependencies (in the project manifest.json) would actually be overrides for any package dependency.
Read more >Checking the Installation of Features, Components, Files
The label "Installed" in the log refers to the current install state of the feature or component, "Request" refers to the requested install...
Read more >Configuration Options - Renovate Docs
Configuration Options¶. This document describes all the configuration options you may use in a Renovate configuration file. Any config you define applies to ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sounds good to me!
@loic-sharma I am aware that
HardDelete
allows me to use that flow. However I am looking for in-place replacement for this reason:I might be working on setting up a package, and forget to include some meta information or some of the meta information is incorrect. Rather than having to go through the process of deleting and re-uploading, I would expect my new package upload to simply replace what is already there, provided the name and version match. Again, this functionality is already present on systems like PhpNuget, and we use it all the time. I get it that this would be problematic in a community package manager setting, but in an internal setting it is very helpful. After all, it could be an option that could be turned on or off (off by default).
I hope this helps.
Thanks!