You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I made a horrible error in the description of my recently-published package here:
Obviously, the stupider the mistake is, the harder you try to correct it, and this one is just causing insane amounts of stress when it should not, especially because there's nothing I can do about it. opm won't let me publish over an existing package to fix the typo, but publishing a patch release just to correct this would be absolutely stupid. But I can't delete and republish the package because there is an artificial 3-day delay (!!).
I wish there was a way to fix stupid mistakes like these so I don't look like a big clown to everyone who sees that package.
The text was updated successfully, but these errors were encountered:
I made a horrible error in the description of my recently-published
package here <https://opm.openresty.org/package/LoganDark/argon2/>:
[image: image]
<https://user-images.githubusercontent.com/4723091/166808527-18fa9f88-d0f5-4d1f-a371-07649b8c2adf.png>
Obviously, the stupider the mistake is, the harder you try to correct it,
and this one is just causing insane amounts of stress when it should not,
especially because there's *nothing I can do about it*. opm won't let me
publish over an existing package to fix the typo, but publishing a patch
release just to correct this would be absolutely stupid. But I can't delete
and republish the package because there is an artificial 3-day delay (!!).
I wish there was a way to fix stupid mistakes like these so I don't look
like a big clown to everyone who sees that package.
—
Reply to this email directly, view it on GitHub
<#96>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA6RHPW3XPLHT4XCEWD676LVILD4LANCNFSM5VC46PHA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
In my opinion, publishing a patch release is a good choice.
I had to justify it by lumping in a bunch of unrelated optimizations. I still hate that I have to do that to correct a typo and that 1.0.0 will always have the typo.
I made a horrible error in the description of my recently-published package here:
Obviously, the stupider the mistake is, the harder you try to correct it, and this one is just causing insane amounts of stress when it should not, especially because there's nothing I can do about it.
opm
won't let me publish over an existing package to fix the typo, but publishing a patch release just to correct this would be absolutely stupid. But I can't delete and republish the package because there is an artificial 3-day delay (!!).I wish there was a way to fix stupid mistakes like these so I don't look like a big clown to everyone who sees that package.
The text was updated successfully, but these errors were encountered: