CLI should get the package version from CI #260

New issue

Open

opened 2025-07-09 11:35:16 +01:00 by Vylpes · 1 comment

Vylpes commented

2025-07-09 11:35:16 +01:00

Owner

So that it can be automated

Vylpes added the

type

change

label 2025-07-09 11:35:34 +01:00

Vylpes added this to the 2.5.0 milestone 2025-07-19 14:29:01 +01:00

Vylpes self-assigned this 2025-07-19 14:34:46 +01:00

Vylpes started working 2025-07-19 14:34:47 +01:00

Vylpes added this to the 2.4 Sprint 5 project 2025-07-19 14:34:52 +01:00

Vylpes commented

2025-07-19 14:53:53 +01:00

Author

Owner

Just had a look and its not as simple as I initially thought, with the way that the CLI package uses a hardcoded string for the version and the packaging package I'm unsure.

I can't have it in the version in an external file as this file would then need to be alongside the binary. I also can't use an environment variable as this is at runtime.

Perhaps I can have the CI environment override a variable in a js script before compiling?

Just had a look and its not as simple as I initially thought, with the way that the CLI package uses a hardcoded string for the version and the packaging package I'm unsure. I can't have it in the version in an external file as this file would then need to be alongside the binary. I also can't use an environment variable as this is at runtime. Perhaps I can have the CI environment override a variable in a js script before compiling?

Vylpes stopped working 2025-07-19 14:53:54 +01:00

19 minutes 7 seconds

No milestone

No project

No assignees

1 participant

Notifications

Total time spent: 19 minutes 7 seconds

Vylpes

19 minutes 7 seconds

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: RabbitLabs/random-bunny#260

No description provided.

Rows
Columns