[jlongster]

Issue for this PR

Closes #

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

release-process-daemon.yml hardcoded PROTOCOL_VERSION: 7. The daemon is on protocol 8 now (#61875), so the release's --version checks would fail, and the manifest and release notes would say 7.

Instead of bumping the number (and needing a workflow change on every protocol bump), the checks job reads PROTOCOL_VERSION from packages/process-daemon/src/protocol.rs and exposes it as a job output; build, build-windows and release set PROTOCOL_VERSION from it, so every existing use keeps working unchanged. release now also lists checks in needs so it can read the output.

Needed before tagging the 0.5.0 release (#62007).

How did you verify your code works?

Ran the sed extraction against src/protocol.rs (prints 8) and checked the workflow still parses as YAML. The release jobs themselves only run on a tag or manual dispatch.

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

[opencodejr]

The change looks sound to me. The sed extraction returns 8 from src/protocol.rs (the job's default working-directory is packages/process-daemon, so the relative path resolves). All four uses of $PROTOCOL_VERSION are in build, build-windows and release, and each now gets the value from the checks output. release also has checks in needs. With test -n, the run fails early if the constant's format ever changes, so an empty version can't slip through. I couldn't run the release jobs end to end, since they only run on a tag or manual dispatch.

Public API: unchanged (CI workflow only).

[thdxr]

lgtm