Invalid order of NuGet dev releases

[moreal]

Background

When I looked at Libplanet's NuGet dev releases, they were not well ordered by release date.

It is because the version suffix is generated without zerofill. (20240901 with zerofill, 202491 without zerofill)

Work items

To resolve this issue, you can amend scripts/determine-versions.js file. You can see the logic to determine a version suffix at the below lines:

libplanet/scripts/determine-version.js

Lines 120 to 126 in f6cd63d

	const timestamp = await getCommitTimestamp();
	const ts = `${timestamp.getUTCFullYear()}${
	timestamp.getUTCMonth() + 1
	}${timestamp.getUTCDate()}${timestamp.getUTCHours()}${
	timestamp.getUTCMinutes() + 0
	}${timestamp.getUTCSeconds()}`;
	versionSuffix = `dev.${ts}`;

You should update the part to declare ts variable.

You can test the script easily by running the node scripts/determine-version.js command.

$ node --version
v20.4.0
$ node scripts/determine-version.js 
VersionPrefix: 5.3.0
VersionSuffix: dev.202491004320+f6cd63d
PackageVersion: 5.3.0-dev.202491004320
VersionType: dev

If you amended well, it expects to generate VersionSuffix: dev.20240910010203+xxxxxxx for the date (year: 2024, month: 9, day: 10, hour: 1, minutes: 2, seconds: 3)

[uday-rana]

Hi, I'd like to work on this.

[moreal]

@uday-rana Sure! I just assigned you to this issue.

And we're also running a hackathon right now named Modathon. We'd love for you to check it out 🙏🏻

https://nine-chronicles.dev/event/2024modathon