Release notes truncate the version number

[mwebber]

Describe your use-case which is not covered by existing documentation.

If you look at https://plugins.jenkins.io/json-api/releases/, the latest release says
Bump org.json:json from 2024030 to 2024122 (#62) @dependabot
Those version numbers are missing the last digit, they should be 20240303 and 20241224.
The numbers are correct in the PR (#62), but have got mangled somewhere down the line.
A minor point, but it would be nice to get it fixed.

@jonesbusy can you suggest where in the release procedure this might be going wrong?

Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.

No response

Are you interested in contributing to the documentation?

No response

[MarkEWaite]

I suspect that a pattern matcher in the converter that translates the GitHub release notes into the releases page on plugins.jenkins.io is incorrectly assuming that a sequence of 8 (or more) (hex) digits is the SHA-1 of a commit. One simple workaround is to insert a non-hex character into that sequence. Instead of 20240303 it could be 2024-03-03 or v24040303. That would be a manual edit of the GitHub release notes, but a simple edit to resolve the issue.

Another alternative would be to make the SHA-1 pattern matcher require a longer sequence of hex digits before it assumes a string is a SHA-1 reference. Unfortunately, that would then reduce other cases where the a sequence of 8 (or more) hex digits actually represent a SHA-1.