{"action":"created","issue":{"url":"https://api.github.com/repos/npm/npm/issues/7016","repository_url":"https://api.github.com/repos/npm/npm","labels_url":"https://api.github.com/repos/npm/npm/issues/7016/labels{/name}","comments_url":"https://api.github.com/repos/npm/npm/issues/7016/comments","events_url":"https://api.github.com/repos/npm/npm/issues/7016/events","html_url":"https://github.com/npm/npm/issues/7016","id":52877238,"number":7016,"title":"Update package README without publishing a new patch version?","user":{"login":"UltCombo","id":2090712,"avatar_url":"https://avatars.githubusercontent.com/u/2090712?v=3","gravatar_id":"","url":"https://api.github.com/users/UltCombo","html_url":"https://github.com/UltCombo","followers_url":"https://api.github.com/users/UltCombo/followers","following_url":"https://api.github.com/users/UltCombo/following{/other_user}","gists_url":"https://api.github.com/users/UltCombo/gists{/gist_id}","starred_url":"https://api.github.com/users/UltCombo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/UltCombo/subscriptions","organizations_url":"https://api.github.com/users/UltCombo/orgs","repos_url":"https://api.github.com/users/UltCombo/repos","events_url":"https://api.github.com/users/UltCombo/events{/privacy}","received_events_url":"https://api.github.com/users/UltCombo/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/npm/npm/labels/feature-request","name":"feature-request","color":"98DCFF"},{"url":"https://api.github.com/repos/npm/npm/labels/registry","name":"registry","color":"871646"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":22,"created_at":"2014-12-26T02:05:38Z","updated_at":"2016-05-11T18:18:37Z","closed_at":"2016-01-29T06:24:38Z","body":"I recall reading somewhere (possibly in the npm blog) that it was now possible to edit a package's readme data without publishing a new version, but I can't seem to find any web interface or CLI command to do so.\r\n\r\nIs it at all possible (without `npm publish --force`), or did I misunderstand something?"},"comment":{"url":"https://api.github.com/repos/npm/npm/issues/comments/218544808","html_url":"https://github.com/npm/npm/issues/7016#issuecomment-218544808","issue_url":"https://api.github.com/repos/npm/npm/issues/7016","id":218544808,"user":{"login":"leonaves","id":1926652,"avatar_url":"https://avatars.githubusercontent.com/u/1926652?v=3","gravatar_id":"","url":"https://api.github.com/users/leonaves","html_url":"https://github.com/leonaves","followers_url":"https://api.github.com/users/leonaves/followers","following_url":"https://api.github.com/users/leonaves/following{/other_user}","gists_url":"https://api.github.com/users/leonaves/gists{/gist_id}","starred_url":"https://api.github.com/users/leonaves/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/leonaves/subscriptions","organizations_url":"https://api.github.com/users/leonaves/orgs","repos_url":"https://api.github.com/users/leonaves/repos","events_url":"https://api.github.com/users/leonaves/events{/privacy}","received_events_url":"https://api.github.com/users/leonaves/received_events","type":"User","site_admin":false},"created_at":"2016-05-11T18:18:37Z","updated_at":"2016-05-11T18:18:37Z","body":"Philosophically, I don't see a problem with simply updating the patch number, however, I think it's probably detrimental to npm as a whole to not have a command like this, because it subconsciously dissuades people from publishing README changes to npm. Sure, you can say to those looking for a way to do this \"Just patch the version number it's not a big deal\", but most people probably aren't looking for a way to do this, they will update their README, push it to github, and think \"Oh I should probably change it on npm, how do I do that?\", have a quick google, realise there's no command and just say \"Ah, I'll worry about it later.\" And then npm users miss out on what was perhaps a clarifying change to an example section of code, or a fix that made a sentence less confusing.\r\n\r\nThe cognitive effort to patch, push and publish is not high enough that those wanting this solution should be annoyed that it isn't there, but it is high enough that it will subconsciously dissuade people from doing it, much like full page splash adverts that are proven to make people leave websites immediately. You can argue with someone \"You only have to look at it for 2 seconds and you can skip\", but you can only make that argument if they have that discussion with you, most won't; most will simply leave your website and never view your content..\r\n\r\nSo yes, I am for something like this being included, even if it is a lot of effort to implement, and even if the workaround is minor; it will encourage updates like this more regularly, making the npm site a better place, I don't see how you could really be against it."}}