A small suggestion for the Release Notes

[577]

Since the release title already includes the version and timestamp, it might be unnecessary to repeat this information in the release body, especially since the two timestamps do not match.

Simply delete these two lines.

ungoogled-chromium-macos/.github/scripts/github_generate_release_note.sh

Lines 17 to 18 in 4853bf0

	printf '## Ungoogled-Chromium %s\n' "$_release_tag_version" | tee -a ./github_release_note.md
	printf '\n' | tee -a ./github_release_note.md

[Cubik65536]

Yeah it is an unexpected problem to have it mismatched (I introduced this bug and haven't found it) and I do plan to remove these in the next update.

My plan is to just remove entirely the epoch timestamp from the release (from tag, title, and body), and also just use the chromium_version + ungoogled_revision (in this case, just the 121.0.6167.85-1.1) for both the tag and the release title, so that it behaves in the same way as the other repos in the org. (As mentioned here a bit (sort of))

Any opinions on this? /cc @networkException @PF4Public

[networkException]

yep, I'm definitely in favor of removing the timestamp. I'm not entirely sure if they were added because CI was unstable or frequent rebuilds were needed, though

[Cubik65536]

yep, I'm definitely in favor of removing the timestamp. I'm not entirely sure if they were added because CI was unstable or frequent rebuilds were needed, though

For now, we shouldn't need to rerun CIs unless we're changing the CI script and just want to test it. And I don't see any cases where there will be rebuilds (with the old script, it's possible that multiple releases will be created, it won't happen again).

I will make this change in the next update then.

[claudiodekker]

yep, I'm definitely in favor of removing the timestamp. I'm not entirely sure if they were added because CI was unstable or frequent rebuilds were needed, though

They were added in #92, perhaps @kramred has any recollection of it if they're around?