8000 ci: latest-passing-build by mtfurlan · Pull Request #1869 · cpputest/cpputest · GitHub < 8000 link rel="alternate icon" class="js-site-favicon" type="image/png" href="https://github.githubassets.com/favicons/favicon.png">
[go: up one dir, main page]

Skip to content

Conversation

@mtfurlan
Copy link
Contributor
@mtfurlan mtfurlan commented Oct 3, 2025

bring back the latest-passing-build tag

addresses #1855

to see it in action before merging, see
https://github.com/mtfurlan/cpputest/releases/tag/latest-passing-build

bring back the latest-passing-build tag
@coveralls
Copy link

Coverage Status

coverage: 99.281%. remained the same
when pulling 7d83924 on mtfurlan:ci/latest-passing-build
into 1142675 on cpputest:master.

@mtfurlan
Copy link
Contributor Author
mtfurlan commented Nov 3, 2025

Something I didn't notice till just now: when you update a release, it will not update the release date.

released this Apr 23, 2020
Date: Mon Nov 22 07:40:52 UTC 2021

I don't think this is acceptable, so I guess we gotta delete and recreate the release?

@notable-equivalent
Copy link
Contributor
notable-equivalent commented Dec 19, 2025

The date was already not being updated back when this repo published the latest passing build (right now the "release date" of the latest passing build is April 2020, but the build is actually from November 2021). So given that this was already an existing problem, I think it's acceptable to still have that problem, at least for now.

EDIT: Apparently GitHub sorts releases in the feed based on the date of the tag/commit and not the "release date" of the GitHub releases itself, so I even more so feel that it's fine to leave it like this https://github.com/orgs/community/discussions/5447#discussioncomment-1555826

@mtfurlan mtfurlan marked this pull request as ready for review December 19, 2025 17:28
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

0