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

Allow locking the deps #58

Merged
merged 1 commit into from
Jan 30, 2025
Merged

Allow locking the deps #58

merged 1 commit into from
Jan 30, 2025

Conversation

greg0ire
Copy link
Member

@greg0ire greg0ire commented Jan 30, 2025

On doctrine/website, which is a regular Symfony application, we put the composer.lock under version control, as we should. In order to be able to have the same experience in the CI as we have locally, we should use the same version of the dependencies. To that end, let's allow passing the dependency-versions option to ramsey/composer-install on workflows that are reused on doctrine/website .

Proofs

We can see that the option is taken into account in the following logs:

On doctrine/website, which is a regular Symfony application, we put the
composer.lock under version control, as we should.
In order to be able to have the same experience in the CI as we have
locally, we should use the same version of the dependencies.
To that end, let's allow passing the dependency-versions option to
ramsey/composer-install on workflows that are reused on
doctrine/website.
@greg0ire greg0ire merged commit 9061a3b into doctrine:main Jan 30, 2025
@greg0ire greg0ire deleted the locked-deps branch January 30, 2025 21:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants