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

Update dependencies #260

Merged
merged 4 commits into from
Mar 23, 2022
Merged

Update dependencies #260

merged 4 commits into from
Mar 23, 2022

Conversation

driehle
Copy link
Member

@driehle driehle commented Mar 22, 2022

  • Marks 3.2 series as unmaintained
  • Updates dependencies to latest versions
  • Fixes one static analysis issue occuring with newer version of Psalm

@driehle driehle added the Enhancement New feature or request label Mar 22, 2022
@driehle driehle self-assigned this Mar 22, 2022
@driehle driehle added this to the 4.0.1 milestone Mar 22, 2022
@driehle driehle changed the base branch from 4.1.x to 4.0.x March 22, 2022 13:06
@driehle driehle marked this pull request as ready for review March 22, 2022 13:06
@driehle driehle requested review from a team March 22, 2022 13:07
@driehle driehle force-pushed the feature/dependencies branch from 88a5220 to 66f5dc6 Compare March 22, 2022 13:11
Copy link
Member

@malarzm malarzm left a comment

Choose a reason for hiding this comment

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

Left some questions but I believe these changes are way too drastic for a bugfix release

"doctrine/mongodb-odm": "^2.3.0",
"doctrine/persistence": "^2.2.3",
"doctrine/mongodb-odm": "^2.3.2",
"doctrine/persistence": "^2.4.0",
Copy link
Member

Choose a reason for hiding this comment

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

What's the point in bumping doctrine/persistence? ODM itself is fine with ^2.2

Copy link
Member Author

Choose a reason for hiding this comment

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

Why not? Since it is the same major there shouldn't be any issues in upgrading.

Copy link
Member

Choose a reason for hiding this comment

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

Probably best done in a minor release, rather than a patch release

Copy link
Member Author

Choose a reason for hiding this comment

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

Ok, I changed the base

"doctrine/doctrine-module": "^5.0.0",
"doctrine/doctrine-laminas-hydrator": "^2.2.1 || ^3.0.0",
"doctrine/doctrine-module": "^5.1.0",
"doctrine/doctrine-laminas-hydrator": "^3.0.1",
Copy link
Member

Choose a reason for hiding this comment

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

What's the point in dropping ^2.2.1? That's really drastic for a bugfix release

Copy link
Member Author

Choose a reason for hiding this comment

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

2.2 series will soon be unmaintained

@driehle driehle changed the base branch from 4.0.x to 4.1.x March 22, 2022 20:46
@driehle driehle modified the milestones: 4.0.1, 4.1.0 Mar 22, 2022
Copy link
Member

@malarzm malarzm left a comment

Choose a reason for hiding this comment

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

I'm perfectly fine with these bumps in a minor release 👍

@driehle driehle merged commit 579f056 into doctrine:4.1.x Mar 23, 2022
@driehle driehle deleted the feature/dependencies branch October 26, 2022 06:56
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.

3 participants