Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(ci): update release tag detection logic #32467

Merged
merged 1 commit into from
Sep 25, 2024

Conversation

esolitos
Copy link
Contributor

@esolitos esolitos commented Sep 25, 2024

What

Update the logic used to detect the previous release tag in the CI workflow.

Why

Previously, the workflow was using the first release tag, but this could lead to incorrect results, if for example the "Language Server" was released.

The updated code now retrieves all the release tags and selects the most recent one that matches the pattern.

Additional info

The previous change (PR #32433) was tested in another repo, but that repo only had 1 type of releases, so this was not seen.

The changes in this commit update the logic used to detect the previous release tag in the CI workflow. Previously, the workflow was using the first release tag that matched the version pattern, but this could lead to incorrect results if there were multiple release tags that matched the pattern. The updated code now retrieves all the release tags that match the pattern and selects the most recent one, ensuring that the correct previous tag is used for comparison.
@esolitos esolitos requested review from aressem and bjormel September 25, 2024 08:08
@esolitos esolitos self-assigned this Sep 25, 2024
@esolitos esolitos marked this pull request as ready for review September 25, 2024 08:08
@esolitos esolitos merged commit 54a09ec into master Sep 25, 2024
6 checks passed
@esolitos esolitos deleted the update-previous-tag-fetching branch September 25, 2024 08:16
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.

2 participants