Non-semver Fluent Bit release

[stevehipwell]

Bug Report

Describe the bug

The last fluent bit release, v4.2.3.1, isn't a valid SemVer which may cause issues throughout the ecosystem.

Expected behavior

Fluent Bit releases should use SemVer.

[stevehipwell]

CC @edsiper @patrick-stephens

[patrick-stephens]

Not sure as it's also not marked as latest release, looks like the only change is from @cosmo0920 for Windows containers: v4.2.3...v4.2.3.1

The CI actually failed because it is non-semver on release as well: https://github.com/fluent/fluent-bit/actions/runs/22210908082/job/64245568332

[stevehipwell]

I saw that it'd failed, I'm not sure why the automation creates a release until everything is green. If you need a release trigger it should be a tag as releases "should" be immutable.

[cosmo0920]

Not sure as it's also not marked as latest release, looks like the only change is from @cosmo0920 for Windows containers: v4.2.3...v4.2.3.1

The CI actually failed because it is non-semver on release as well: https://github.com/fluent/fluent-bit/actions/runs/22210908082/job/64245568332

This is just for confirming Windows container building release. It's not intended to create/change another release of 4.2 series.

[stevehipwell]

@cosmo0920 why create a release, the public API for Fluent Bit, for it then?

[stevehipwell]

And if you absolutely needed a release why not use a valid SemVer pattern such as v4.2.3-win.0?

[edsiper]

I suggested to just add a .1 at the end, will take note on this and use -something next time if needed