release_path does not exist on sentry:deploy

[DFcsapparel]

Deployer Version

v8.0.5

Target OS

Ubuntu 22

Which PHP version are you using?

PHP 8.5

Content of deploy.php or deploy.yaml

set('sentry', [
    'sentry_server' => 'https://sentry.selfhosted.cz',
    'organization' => 'myorg',
    'projects' => [
        'myproject'
    ],
    'token' => 's/x/x',
    'environment' => 'production',
]);

host('www1', 'www2', 'www3')
    ->setLabels([
        'env' => 'production',
    ])
    ->set('remote_user', 'myuser')
    ->set('deploy_path', '/var/www/admin/' . getenv('BRAND'))
    ->set('keep_releases', 5);

Steps to reproduce

dep deploy:sentry www1 --revision 4d7ebc3f127cb32169d90944905d27f1f4792e18 -vvvv

[www1] run cd /var/www/admin/brand/.dep/repo && (cat /var/www/admin/brand/current/REVISION)
[www1] Warning: Permanently added 'www1' (ED25519) to the list of known hosts.
[www1] 4d7ebc3f127cb32169d90944905d27f1f4792e18
[www1] ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /home/vader/.ssh/id_ed25519 -A -o ControlMaster=auto -o ControlPersist=60 -o $'ControlPath=~/.ssh/myuser@www1' myuser@www1 $': id$d6c291803457d6301a7e; bash -ls'
[www1] run cd /var/www/admin/brand/.dep/repo && (if [ -h /var/www/admin/brand/release ]; then echo +accurate; fi)
[www1]  Deployer\Exception\Exception  in sentry.php on line 214:
[www1]
[www1]   The "release_path" (/var/www/admin/brand/release) does not exist.

[DFcsapparel]

Hi there, i guess the main problem is that sentry recipe is getting release_path. Since you explicitly mention:
Since you should only notify Sentry of a successful deployment, the deploy:sentry task should be executed right at the end.
the release folder doesnt exist anymore at this time. Shouldnt be used release_or_current_path or current_path ?

https://github.com/deployphp/deployer/blob/master/contrib/sentry.php#L214

[meyshad]

Your diagnosis is right. This is not caused by the host configuration.

In Deployer 8, deploy:symlink either moves {{deploy_path}}/release to {{current_path}} or removes the release symlink. By the time an after('deploy', 'deploy:sentry') hook runs, release_path is therefore expected to be gone. The Sentry recipe still evaluates both default closures against that path: getReleaseGitRef() and getGitCommitsRefs() / getCurrentReleaseRevision().

--revision does not help by itself because the default Sentry config never reads that option. A practical workaround is to override both version and commits:

namespace Deployer;

set('sentry', [
    'sentry_server' => 'https://sentry.selfhosted.cz',
    'organization' => 'myorg',
    'projects' => ['myproject'],
    'token' => '...',
    'environment' => 'production',

    'version' => static fn (array $config): string =>
        (string) (input()->getOption('revision')
            ?: trim(run('cat {{current_path}}/REVISION'))),

    // Important: replacing only version still leaves the default commits
    // closure trying to read release_path.
    'commits' => [],
]);

With that override, the standalone command you posted can use the supplied revision:

dep deploy:sentry www1 --revision 4d7ebc3f127cb32169d90944905d27f1f4792e18 -vvvv

If commit association is needed in Sentry, you can populate refs explicitly from the same revision, or provide a custom commits closure that reads from current_path.

I would not change only the cd('{{release_path}}') line in getReleaseGitRef(): getCurrentReleaseRevision() also reads release_path. The recipe-level fix should use release_or_current_path consistently for both version and commit lookup when the task runs after publishing.