@hydai @q82419 Please take a look
Thanks!

Have you verified that the build is working after bumping the version?

@hydai I verified this locally by deleting the build directory, reconfiguring, and rebuilding, and the build completes successfully with the updated BitNet commit.
I also checked the CI logs and the previous error:
"fatal: invalid reference: 404980e"
is no longer present
CI Jobs: https://github.com/vishal2005025/WasmEdge/pull/3/checks

@hydai I verified this locally by deleting the build directory, reconfiguring, and rebuilding, and the build completes successfully with the updated BitNet commit. I also checked the CI logs and the previous error: "fatal: invalid reference: 404980e" is no longer present CI Jobs: https://github.com/vishal2005025/WasmEdge/pull/3/checks

Hi, CI checks are still failing on ubuntu https://github.com/vishal2005025/WasmEdge/actions/runs/21863594641/job/63099345148?pr=3

@Divyansh200102 The original CI failure was caused by BitNet failing to fetch due to an invalid pinned commit. With this change, BitNet is fetched successfully and CI progresses further.
The current failure in wasi_nn-bitnet-x86-tl2 is a compilation error inside BitNet upstream code (ggml-bitnet-mad.cpp) with Clang 18, which appears unrelated to the commit pin update.

@Divyansh200102 The original CI failure was caused by BitNet failing to fetch due to an invalid pinned commit. With this change, BitNet is fetched successfully and CI progresses further. The current failure in wasi_nn-bitnet-x86-tl2 is a compilation error inside BitNet upstream code (ggml-bitnet-mad.cpp) with Clang 18, which appears unrelated to the commit pin update.

I know but currently the bitnet workflow seems to be working fine after disabling the shadow clone so bumping the version for this specific problem doesn't make sense to me and it isn't solving the issue.
https://github.com/WasmEdge/WasmEdge/actions/runs/21870696747/job/63126374247?pr=4443

404980e) no longer exists upstream, causing FetchContent

also you said here that this commit doesn't exist but I do see it in the upstream microsoft/BitNet@404980e . So this was likely a shadow clone problem and not something that needs a version bump.

@Divyansh200102 Thanks, I just checked and it looks like the BitNet workflow is now working after disabling the shallow clone and allowing a full history fetch.
In this PR, I tried an alternative approach by updating the pinned BitNet commit while keeping shallow clone enabled, since the previously pinned commit appeared unreachable in CI and I wanted to ensure we were using a valid and up-to-date upstream commit.
Given that the shallow-clone fix already resolves the issue, bumping the BitNet commit may not be necessary. If maintainers prefer to keep the existing pinned version, I’m happy to close this PR.