ci: avoids latest-release workflow to run on forks

[helio-frota]

Closes #1507

[ctron]

What is the exact issue we run into? I think every fork should be able doing this.

[helio-frota]

This is to prevent this failure when updating forks:

[helio-frota]

I think every fork should be able doing this.

This means I need to configure something in the fork to avoid this error and probably makes no sense for a fork to publish artifacts. Although I don't know if this happens to other people 🤔

Error: writing blob: initiating layer upload to /v2/helio-frota/trustd/blobs/uploads/ in ghcr.io: denied: permission_denied: write_package
Removing temporary Podman image storage for pulling from Docker daemon
/usr/bin/podman --root /tmp/podman-from-docker-2HR3I4 rmi -a -f
(node:7397) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead
(Use `node --trace-deprecation ...` to show where the warning was created)
Error: podman exited with code 125
Error: writing blob: initiating layer upload to /v2/helio-frota/trustd/blobs/uploads/ in ghcr.io: denied: permission_denied: write_package

[ctron]

I does work fine for my fork: https://github.com/ctron/trustify/actions/runs/14190434291 … Though I'm not sure I configured anything specifically.

[helio-frota]

thanks, yeah I see your fork is working fine:

my fork is missing packages and deployments part and contains a different number of release-tags 🤷

[helio-frota]

@ctron I'm ok closing the issue and PR...

I'll follow @jcrossley3 way on disabling actions on my fork 👍