My woodpecker plugin can't read files from cloned repository

[JasterV]

So, I've implemented a plugin to manage release PRs of my Rust projects using the release-plz tool.

Here is the bash script: https://codeberg.org/JasterV/docker/src/branch/main/release-plz/update-pr.sh (Have in mind it contains a few commands that I've added to try to debug whats going on)
And this is the Dockerfile: https://codeberg.org/JasterV/docker/src/branch/main/release-plz/update-pr.Dockerfile

The problem is that when I run release-plz update which needs to read the Cargo.toml file from the repository, it can't find it

This is very weird because I added ls and pwd commands that tell me that the file is there and that the script runs in the folder where the repo is cloned. For instance, these are the CI logs:

---

--- Running release-plz update ---
// Output of running ls -R
.:
CHANGELOG.md
Cargo.lock
Cargo.toml
LICENSE
Makefile.toml
README.md
deny.toml
release-plz.toml
rust-toolchain.toml
src

./src:
lib.rs
rc_map.rs
subscription.rs

// Output of running pwd
/woodpecker/src/codeberg.org/JasterV/event_bus.rs

2026-03-05T17:42:57.771205Z ERROR release_plz: /usr/local/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/release-plz-0.3.156/src/main.rs:22: Failed to read metadata from manifest at ./Cargo.toml

Caused by:
0: failed to start cargo metadata: No such file or directory (os error 2)
1: No such file or directory (os error 2)
Error: Failed to read metadata from manifest at ./Cargo.toml

Caused by:
0: failed to start cargo metadata: No such file or directory (os error 2)
1: No such file or directory (os error 2)

---

Am I missing something that I should consider? Why is the script not able to read the Cargo.toml? I've ran it locally in my local project and it works fine:(

[qwerty287]

This looks weird indeed. Is release-plz possibly influenced by some env var so it looks for the file at a different path?
Would it work with an absolute path as well? Maybe you could try that with $(pwd)/Cargo.toml? It should work with the relative one as well though.

[JasterV]

I've identified the issue! Basically the No such file or directory error was caused because the docker image didn't contain the cargo command.

I didn't think cargo was necessary for the release-plz binary to run, and the error message is not clear about it

So anyway, it wasn't a problem of woodpecker after all :)