Centralize Version Management via metadata.py for Docker and CI/CD

[skools-here]

Description

1. metadata.py now serves as the single source of version (version)
2. Updated all Dockerfiles to dynamically read the version from metadata.py during CI/CD builds.
   3)pyproject.toml already reads from metadata.py; no changes needed there.

This PR fixes #3294

Notes for Reviewers

Signed commits

• Yes, I signed my commits.

[sgoggins]

lGTM

[MoralCode]

Great start! Could you also include an update to the README to remove the (at least two) references to the specific current version number (and potentially link to the /releases/latest pageof the github releases tab where needed instead)?

Also if i remember correctly, there was a change discussed on slack to update the documentation about the release process as well.

Overall this looks like it definitely helps reduce the number of things to change each release though!

[MoralCode]

is this file used anywhere?

[sgoggins]

I think that is answered in the previous comment, which also explains the purpose of that line.

[MoralCode]

This file contains a lot of formatting changes that arent directly related to the purpose of this PR.

Could you be using any particular tools that are attempting to reformat things?

[sgoggins]

Looking at the doc file, it does appear there is probably some IDE doing automatic reformatting.

[MoralCode]

@skools-here can you rebase/squash commits and make sure all commits are signed-off?

[MoralCode]

@skools-here it seems like your rebase accidentally pulled in an extra commit from main thats unrelated

[skools-here]

yes I have fixed it now I don't how that happened though.

[MoralCode]

yes I have fixed it now I don't how that happened though.

it looks like you just created a new commit that un-does the changes, which is going to cause git to effectively roll those changes back when this merges.

I wish there was a better tool than git that didn't make it so easy to do this kind of thing.

Could you rebase your PR on top of main (again) but only include the three commits you intend to keep? If it helps, I tend to think of operations like this more like a "hard reset your branch to main and then cherry pick the commits you want". Also happy to talk on the CHAOSS slack if you want more specific/detailed guidance!

[skools-here]

@MoralCode Ah, got it — I see what happened now 😅 I’ll rebase my branch onto main and cherry-pick only the three commits related to centralized version management. Thanks for catching that!
I’ll clean it up and push again soon .If I run into any hiccups, I’ll reach out to you on CHAOSS Slack for a help. I also think that there can be better tools than git.

[MoralCode]

almost there! To avoid the need for that final merge commit from main into this branch, you'll likely need to update your fork's main branch so it matches this repo (if you visit your fork in the github UI it should give you a "sync fork" button). Then if you rebase it should set this branch up to be based on the latest version of main, not just the latest at the time you made your fork

[skools-here]

@MoralCode Thanks a lot for helping me out I was really wondering how to resolve this problem !

[MoralCode]

LGTM!

[sgoggins]

LGTM. Not loving the random formatting in Restructured Text, but the CI is working now ... :)

[skools-here]

@sgoggins ngl even I don't know what's that formatting problem :(( . ig it's my editor problem. But hopefully this pr fixed that version management issue !