local-app: Make the version string more CalVer compliant
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe
I want to maintain my own builds of the Local Companion app to more arches for Linux users (hint: linux/386 and linux/arm), but the issue is the official builds aren't CalVer compliant, though I need to do some guesswork on getting the version string from its --version command.
Describe the behaviour you'd like
Make the version string for the Local Companion to be SemVer compliant, not necessarily follow self-hosted release schedule. Optionally also provide an API for retriving new versions.
Describe alternatives you've considered
While I can technically scrape the binary version from the official builds through some shell script magic, it would be a bit of a nightmare.
Additional context
Originally asked in Discord about setting the Dversion flag for building Local Companion from source with Leeway.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Local Companion implementation behind the --version command and the build configuration that uses the Dversion flag. Clarify whether the required output is CalVer or SemVer, whether version retrieval is in scope, and verify that the resulting version output and Linux builds meet the agreed requirements.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100