chore: improve release notes process

[marc0olo]

I noticed that we have a problem with displaying the changes correctly for each recipe on releases and vibed a bit with Claude to fix it.

should work for all recipes.

[raymondk]

This is automatically pushing a $RECIPE-latest tag
When the tag is pushed doesn't that throw off the pipeline for latest because it is going to compare to whatever the highest version tag is (which will likely be the same) and not generate the proper release notes?

[marc0olo]

I am not entirely sure what your concern is, so let me address both possibilities:

1. if you're worried about the -latest release having empty/wrong release notes:

   • you're right - the original code would compare rust-v5.0.0..rust-latest which are the same commit, resulting in empty release notes.
   • I fixed this now by finding the versioned tag on the same commit (rust-v5.0.0), then comparing against its predecessor (rust-v4.0.0..rust-v5.0.0). now both releases should get the same correct release notes.

2. if you're worried about -latest tags interfering with versioned releases:

   • this should already be safe - the previous tag search uses the pattern ${RECIPE}-v*, which only matches versioned tags like rust-v5.0.0 and never matches rust-latest.

these are the scenarios that should be covered now:

Scenario	PREV_TAG	COMPARE_TAG	Result
1. Push rust-v4.0.0	rust-v3.0.0	rust-v4.0.0	Changelog ✓
2. rust-latest triggered (same commit as rust-v4.0.0)	rust-v3.0.0	rust-v4.0.0	Changelog ✓
3. Push newrecipe-v1.0.0 (first ever version)	(empty)	newrecipe-v1.0.0	Initial release ✓
4. newrecipe-latest triggered (same commit as v1.0.0)	(empty)	newrecipe-v1.0.0	Initial release ✓
5. Push newrecipe-latest without versioned tag	-	-	Fails ✓

let me know if you had a different concern in mind.