Fix static version numbers

Question

Fix static version numbers

Opened this issue 2 years ago · 6 comments

The current brew formula uses a fixed version number for Python and the Core repo. Also, the hash needs to be dynamic depending on the core repo version.

Answer 1 · 2024-02-21T22:55:02.000Z

@FirePing32 I do not understand what is this issue about, can you explain it?

Answer 2 · 2024-02-22T06:34:36.000Z

@viferga Currently, we have to manually add commit hash every time a new version is released on metacall/core. Also, the Python version is static, which needs to be dynamic according to the user's machine to avoid build errors (like missing header files). The release version of the core repo is also statically defined in the formula.

Answer 3 · 2024-03-27T05:59:52.000Z

@FirePing32 If i am getting it right, cant we just create a main trigger at the meta call core repo and when the tests.yml is passed it will trigger the build in all other repos as we want??

Answer 4 · 2024-03-27T07:17:10.000Z

@shaggyyy2002 That is the plan as of now.

Answer 5 · 2024-03-27T08:18:34.000Z

@FirePing32 I have a GSoC proposal, mind if you could review it? This issue can be solved under the same
Core CI with Distributable's project

Answer 6 · 2024-03-27T08:22:03.000Z

@shaggyyy2002 I am planning to contribute as a contributor myself, but if you want to share it, you can.