Remove git-tree-sha1 from metadata

[verseve]

It is not part of the Wflow entry in the Manifest.toml file and as a result the build fails.

Issue addressed

Fixes #479

[visr]

If we don't have the git-tree-sha1 or the commit, we only have the branch and the version number, which is not enough to identify the source of the build. This started failing since the build script moved into this repository, hence it is not in the metadata. It's no problem to remove the git-tree-sha1 but then I'd at least add the commit.

For Ribasim we add this to the README.md in the root of our build:

release = "2024.10.0-128-ge09eeb5"
commit = "https://github.com/Deltares/Ribasim/tree/e09eeb5b9a"
branch = "https://github.com/Deltares/Ribasim/tree/main"
julia_version = "1.10.5"
core_version = "2024.11.0"

With additionally in share/julia/Build.toml the TeamCity build number, in case it was built on TeamCity:

BUILD_NUMBER = "1342"
BUILD_VCS_NUMBER = "e09eeb5b9ad46b9715a3aa5ba47fc69b03b48789"

You can take what you want from https://github.com/Deltares/Ribasim/blob/4048a50367dbc4f28975b28f6c6da76cb77e3ea5/build/build.jl#L92

[verseve]

If we don't have the git-tree-sha1 or the commit, we only have the branch and the version number, which is not enough to identify the source of the build. This started failing since the build script moved into this repository, hence it is not in the metadata. It's no problem to remove the git-tree-sha1 but then I'd at least add the commit.

Thanks for the info. I think this started failing with the latest update of the Manifest.toml file: 59f5ef6#diff-4d5f121308e3da7be8f85c55dba1429a0a14f54b42c9d40eedf2d6effdcf2446L655.

Adding the commit (and aligning with Ribasim) sounds good!

[visr]

Looks good! Assuming you tested locally.