Skip to content

Conversation

@FichteFoll
Copy link
Member

Also support new "binary" value for packages ref to automatically use the same build tag as for the binary.

Addresses the second point of #6 that should arguably have been its own issue.

This leads to fewer lines changed when updating descriptions.
Also support new "binary" value for packages ref to automatically use
the same build tag as for the binary.
@FichteFoll FichteFoll added this to the v2.4 milestone Jan 12, 2025
@FichteFoll FichteFoll requested a review from deathaxe January 12, 2025 14:23
Copy link
Member

@deathaxe deathaxe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

We may fetch tags from Packages repo to ensure to have a valid reference, even if binary points to not yet existing tag.

Maybe better to write an action for Packages which checks the update end point and creates tags automatically :-D

@FichteFoll
Copy link
Member Author

Maybe better to write an action for Packages which checks the update end point and creates tags automatically :-D

The problem here is that we cannot simply tag the current master but need to check which version of the repo was actually included in the release. Anyway, that's for another time (and another repo).

Copy link
Member

@deathaxe deathaxe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@FichteFoll FichteFoll merged commit 583ec32 into master Jan 12, 2025
16 checks passed
@FichteFoll FichteFoll deleted the feature/latest-stable branch January 12, 2025 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants