Skip to content
This repository has been archived by the owner on Nov 11, 2020. It is now read-only.

Bump doctrine/common dependency #207

Merged
merged 2 commits into from
Feb 24, 2015
Merged

Bump doctrine/common dependency #207

merged 2 commits into from
Feb 24, 2015

Conversation

jmikola
Copy link
Member

@jmikola jmikola commented Feb 24, 2015

No description provided.

@jmikola jmikola added the task label Feb 24, 2015
@jmikola jmikola added this to the 1.0.11 milestone Feb 24, 2015
jmikola added a commit that referenced this pull request Feb 24, 2015
Bump doctrine/common dependency
@jmikola jmikola merged commit 724071c into 1.0.x Feb 24, 2015
@jmikola jmikola deleted the 1.0-deps branch February 24, 2015 23:40
@jmikola jmikola modified the milestones: 1.1.8, 1.0.11 Feb 25, 2015
@@ -1,5 +1,2 @@
phpunit.xml
vendor
composer.lock
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why commiting the lock file in the library ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I talked with @naderman about this at FOSDEM. It's ignored for projects that depend on ODM, so it doesn't affect our users, but it gives developers consistency for reproducing test results (also the "build status" icon).

@BernardoSilva
Copy link
Contributor

Commiting the lock file will force dependencies to be locked for that specific version.
If you're locking the dependencies to a specific revision it can cause issues if we depend directly on doctrine/mongodb.

@naderman
Copy link
Member

Composer does not consider the content of a dependency's lock file, only the lock file in the root project itself is ever used.

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

Successfully merging this pull request may close these issues.

4 participants