🔢 Share a unified version number for manuscript-cli and manuscript-gui

[KagemniKarimu]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I have searched for existing pull requests search for existing pull requests, including closed ones.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Just recently when version was bumped, it bumped to 1.1.0 for the GUI, but remained the same for the CLI. This is because they were hard-coded in separate files in their respective project directories. Since there are no divergent versions as we're using a monorepository, there should really only be one version number. What do we think about creating a config or build file which stores that information in a single place?

Quoted from #78

The point is that centralized version control is needed to prevent the projects from deviating from each other upon release. Since they both use manuscript-core this should be relatively straight forward.
One recommendation is to use the Makefile as the single source of truth that both Rust and Go projects pull from as articulated in #83.

2. Could you assist us with this feature?

• I am interested in contributing to this feature.

[Liquidwe]

Hi @KagemniKarimu , the makefile has been merged into the main branch, users can build the latest cli and gui code by default, my suggestion is to unify the tag, even if only one of them is updated in a certain tag, it is convenient for management.