Script for producing release version #99411

New Issue

Sybren A. Stüvel · 2022-07-04T15:23:46+02:00

Sybren A. Stüvel commented

2022-07-04 15:23:46 +02:00

It should be possible to create a release X.Y such that:

the version reported by the application is X.Y,
the version in the OpenAPI-generated files is X.Y, and
building the Git tag vX.Y results in the release binary.

This should be scripted so that producing a new release can be done with a single command.

This likely requires some changes in the way the OpenAPI generators get the version number. At this moment they use the output of git describe --tags, but that's insufficient if the files need to get a not-yet-tagged version number.

It should be possible to create a release `X.Y` such that: - the version reported by the application is `X.Y`, - the version in the OpenAPI-generated files is `X.Y`, and - building the Git tag `vX.Y` results in the release binary. This should be scripted so that producing a new release can be done with a single command. This likely requires some changes in the way the OpenAPI generators get the version number. At this moment they use the output of `git describe --tags`, but that's insufficient if the files need to get a not-yet-tagged version number.

Sybren A. Stüvel commented

2022-07-04 15:23:46 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'