pulsar/.github
DeeDeeG c58bc5f14e CI: Fix tag Linux binaries are uploaded to for Rolling
The Rolling binary upload script gets the version from
package.json in the repository files, not from the binary
itself. So, we need to set this value in the repository's
package.json file, regardless of what version the binary itself has.

The version string in package.json is used by the Rolling upload script
to decide what the tag name will be when creating a new Rolling release.
We want timestamped version strings so they are unique,
and older releases are not overwritten/clobbered/won't have conflicts
(whichever would have happened, not worth finding out).
Besides that this restores the convention we had been uploading
the Rolling release tags with so far.

Set a version timestamp just before building the binaries, like on
the other two platforms. Add this to the outputs of the "build" job
if on Linux. Then read this output in the "test and upload, Linux" job.
Now we have synced timestamps again (as much as we did before building
Linux binaries in a Debian 10 Docker container, anyway).

The script could be updated to check the binary itself,
but this way is easier.
2024-01-30 00:00:10 -05:00
..
workflows CI: Fix tag Linux binaries are uploaded to for Rolling 2024-01-30 00:00:10 -05:00
lock.yml 🔥 Use organization level templates 2019-06-13 14:31:17 -07:00
move.yml Enable move-issues bot 2018-04-20 15:45:38 -07:00
no-response.yml Set probot/no-response days-until-close to 28 days 2018-09-28 10:30:42 -04:00
pull.yml pull bot: mergeUnstable: true 2020-09-11 10:21:30 -05:00
renovate.json Add ignorePaths to renovate config 2023-08-27 00:02:35 -07:00
stale.yml Add indentation to force YAML to leave certain lines the way they are 2017-10-07 12:59:59 -07:00