Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: Fix cleanup of the backup composer lock file #1331

Merged
merged 1 commit into from
Mar 15, 2023

Conversation

theofidry
Copy link
Contributor

@theofidry theofidry commented Mar 14, 2023

The trap function was registered as the last bash instruction and as a result was not executed if anything failed before, e.g. the composer update command or building the PHAR itself.

In the event the build PHAR script fails, the temporary backup composer.lock file may be created and not removed.

Also add the backup composer.lock file to the gitignore for good measure.

Q A
Type bug
BC Break yes

The trap function was registered as the last bash instruction and as a
result was not executed if anything failed before, e.g. the composer
update command or building the PHAR itself.

In the event the build PHAR script fails, the temporary backup
composer.lock file may be created and not removed.
@greg0ire greg0ire added the CI label Mar 15, 2023
@greg0ire greg0ire added this to the 3.6.1 milestone Mar 15, 2023
@greg0ire greg0ire merged commit f24167d into doctrine:3.6.x Mar 15, 2023
@greg0ire
Copy link
Member

Thanks @theofidry!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants