Is there a way to find out which git commit corresponds with a given maven release of kotest? We’re...

# kotest

[xenomachina]

Is there a way to find out which git commit corresponds with a given maven release of kotest?

We’re using 4.6.2, which seems to be the latest version on maven central, but the last tag on github seems to be v4.6.0 (also, git describe says 3.3.0-RC2-2145-g5e9758a42).

[Big Chungus]

Commit hash should be in pom.xml on maven central

[xenomachina]

Do you mean here? I don’t see anything that looks like a commit hash.

[Big Chungus]

Ah yes. It should be under scm.tag. However that's not mandatory for publishing and looks like devs chose not to include that data.

[Big Chungus]

Maybe have a look at their ci to see which job (if any) released it?

[xenomachina]

How would I see the CI jobs that published to maven central?

I’ve seen other projects use a git tag for every release, which is very convenient. It seems even kotest was doing this in the past, at least sometimes.

A benefit to using the git tag is also that if you somehow end up on an outdated maven artifact (as happened to us back when kotest changed its name) it’s relatively easy to compare the version in git to the one you’re pulling from maven and see the discrepancy.

[Big Chungus]

Check if they use gh actions or something like that

[xenomachina]

Thanks. I found a few “release_*” workflows, but from looking at the last few I’m not seeing anything that looks like “4.6.2".

[sam]

We should make it tag automatically on release. Please make an issue on GH for that.

[Big Chungus]

Or just use gh releases to trigger your workflows (it tags automatically)

[sam]

That seems useful but sometimes I have to replay the workflows. I'll check it.

[Big Chungus]

You can move the tag if some hotfix is needed and rerun your workflows again

[Big Chungus]

Gh release is linked to a tag and follows it nicely

[sam]

Ok i can check that out