jitpack.yml is completely ignored on JitCI (no output from before_install, not even echo)

[fuzeblocks]

---

Repository: fuzeblocks/homeplugin
Build log: https://jitci.com/gh/fuzeblocks/HomePlugin/builds/b1KZX0QE9V0H4S1E441GPP0VQW/build.log

Describe the bug

jitpack.yml at the root of the repository is not being read/executed at all during the build on JitCI (jitci.com). Even a minimal before_install: - echo "test" produces no output in the build log.

Steps to reproduce

1. Add a jitpack.yml at the repo root with:

   before_install:
     - echo "JITPACK_YML_IS_READ"
   

2. Trigger a build on JitCI (or JitPack) for fuzeblocks/homeplugin.

3. Inspect the build log.

Expected behavior

The log should show the echo output, as documented here: https://docs.jitpack.io/building/#custom-commands

Actual behavior

The echo output never appears. The build log shows only the default JitPack commands:

$ git clone --branch main https://github.com/fuzeblocks/homeplugin.git .
$ git checkout -qf ce3ed2a5e0d5ee87b56c3dc2a0e099eabb349a3f
$ mvn -B -v
$ mvn -B de.qaware.maven:go-offline-maven-plugin:resolve-dependencies
$ /home/jitpack/build/_init_commands
$ mvn -B install -DskipTests

/home/jitpack/build/_init_commands runs but produces zero output, and the final Maven command used is the plain default mvn -B install -DskipTests, not the custom install: block I defined in jitpack.yml.

This previously caused an actual build failure for us: we needed to install Java 25 via SDKMAN in before_install/install to compile against --release 25, but since jitpack.yml is ignored the build kept using the default Java 21 toolchain, resulting in:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.13.0:compile (default-compile) on project modern: Fatal error compiling: error: release version 25 not supported -> [Help 1]

jitpack.yml content used

before_install:
  - sdk install java 25.0.2-open
install:
  - . ~/.sdkman/bin/sdkman-init.sh && sdk use java 25.0.2-open && java -version && mvn -B install

The file is valid YAML (verified with yaml.safe_load), no tabs, no encoding issues, located at repo root, and correctly named jitpack.yml.

Additional context

This looks related to the long-standing issue #4260 ("jitpack.yml is no longer working or being read"), which appears to still be unresolved. Happy to provide any additional logs/details.

---