feat: Update to 5.0.0

[nschonni]

#2983 didn't include the update to the package.json, so the tag likely needs to be fixed too

[xzyfer]

I'll do this with the npm publish. The tag doesn't matter because publish pushes a tarball to the registry.

…

On Wed, 28 Oct 2020, 9:16 am Nick Schonning, ***@***.***> wrote: #2983 <#2983> didn't include the update to the package.json, so the tag likely needs to be fixed too ------------------------------ You can view, comment on, or merge this pull request online at: #3012 Commit Summary - feat: Update to 5.0.0 File Changes - *M* package.json <https://github.com/sass/node-sass/pull/3012/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519> (2) Patch Links: - https://github.com/sass/node-sass/pull/3012.patch - https://github.com/sass/node-sass/pull/3012.diff — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3012>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAENSWEKNODYGOB665ZRXTLSM5BCHANCNFSM4TBPHYVQ> .

[nschonni]

OK, do you just want the binaries on the Release page even if the commit is off by one?

[xzyfer]

Yeah as long as the binaries are on the release we're good. We only care that the release tag and non version are the same. The commits don't matter.

…

On Wed, 28 Oct 2020, 9:21 am Nick Schonning, ***@***.***> wrote: OK, do you just want the binaries on the Release page even if the commit is off by one? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3012 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAENSWE4V24KENOZF3BKQ7DSM5BXPANCNFSM4TBPHYVQ> .

[nschonni]

OK, I'm uploading them now, so I'll close this off and ping you on the other PR once it's done