https://api.margo.sh/motd.json doesn't know about v20.03.01 release

[dmitshur]

This is a very minor issue that I'd like to report. The MOTD message is showing up telling me that a new GoSublime release is available, but in reality I have a more recent release.

Fetching https://api.margo.sh/motd.json right now:

{
	"Message": "★★ New GoSublime Release ★ https://margo.sh/cl/20.2.1 ★★",
	"Error": "",
	"ANN": {
		"Tag": {
			"Y": 20,
			"M": 2,
			"D": 1,
			"N": 1
		},
		"Content": "\nThis release focuses on fixing a performance issue due to a failure to resetting all cached data prematurely.\n- Cache some files in memory to avoid re-reading from disk every time.\n- The `\u0026nodejs.PackageScripts{}` reducer now uses `yarn` instead of `npm` if the `yarn.lock` file is present."
	},
	"Tag": "20.02.01-1"
}

According to https://github.com/DisposaBoy/GoSublime/releases, the latest release is v20.03.01, released 6 days ago.

This causes the "new release" message to continuously show up, despite me having a newer version installed:

[dmitshur]

The current logic in motd.go is to show the announcement whenever the installed GoSublime version doesn't match what's reported by the motd.json endpoint:

GoSublime/src/margo.sh/mg/motd.go

Lines 189 to 190 in 96954d1

	case res.Tag != ctag:
	act.msg = res.Message

That means it displays the message when the installed GoSublime version is either newer or older.

[DisposaBoy]

Thanks for spotting that!
The motd.json should now be fixed. I'll fix the tag check soon.

[dmitshur]

Thank you @DisposaBoy!