Repository navigation
Conversation
Running `dep deploy:sentry` standalone (or after `deploy:symlink`) failed
with `The "release_path" does not exist`, because the recipe read the
revision and git log from {{release_path}}.
- Use {{release_or_current_path}} for revision and git commands.
- Resolve the previous release from `releases_list` when
`previous_release` is not set (standalone run).
- Limit commits with `git rev-list --max-count=200`; the previous
array_slice counted the `commit <sha>` header lines too, so only
100 commits were sent for the first release.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Running
dep deploy:sentrystandalone fails with:because the recipe reads the revision and git log from
{{release_path}}, which is removed bydeploy:symlink.Changes in
contrib/sentry.php:{{release_or_current_path}}instead of{{release_path}}for reading the current revision and running git commands.previous_releaseis not set (standalone run), resolve the previous release fromreleases_list, so only new commits are sent instead of the whole history.git rev-list --max-count=200. The previousarray_slice(..., 0, 200)was applied before filtering out thecommit <sha>header lines, so only 100 commits were sent for the first release.Tested locally (
localhost()host, archive strategy, fake Sentry API capturing the payload):after('deploy', 'deploy:sentry')dep deploy:sentryBefore the fix the standalone run failed with the
release_pathexception.php bin/docgenproduces no changes; phpstan, php-cs-fixer and phpunit pass.🤖 Generated with Claude Code