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

Merge release 2.2.0 into 3.0.x #178

Merged
merged 57 commits into from
May 16, 2021

Conversation

github-actions[bot]
Copy link
Contributor

Release Notes for 2.2.0

This release introduces compatibility with doctrine/cache 2.0, adds support for PSR-6 caching in metadata factories, and adds support for proxy class name resolvers to reduce coupling to doctrine/common proxies.

2.2.0

  • Total issues resolved: 0
  • Total pull requests resolved: 12
  • Total contributors: 4

Improvement

Enhancement

Deprecation,Improvement

franmomu and others added 30 commits December 19, 2020 18:57
This file is not needed for a end user
Upgrade to Psalm 4.3.1 and use ramsey/composer-install
Psalm is reporting an apparenlty unexistent issue reported in
vimeo/psalm#5193, for now this ignores
those issues.
Co-authored-by: Grégoire Paris <postmaster@greg0ire.fr>
Co-authored-by: Alexander M. Turek <me@derrabus.de>
Deprecate using doctrine/cache in favour of PSR-6
Instead of returning strings, TestFileDriver::loadMappingFile now
returns array<string, ClassMetadata> as the interface says.
Analyze tests directory with Psalm
Remove unnecessary github actions branch filters
Add class-string typehint for getAssociationTargetClass
@alcaeus
Copy link
Member

alcaeus commented May 15, 2021

@greg0ire does the 3.0.x branch still make sense at this point?

@greg0ire
Copy link
Member

One thing is for sure, it shouldn't be the default branch

From what I see here, it seems to be mostly about type declarations: 2.2.x...3.0.x

I can try performing the merge up with imerge like last time, and then we should start thinking about releasing 3.0 so that it's not a pain every time 😅

@greg0ire
Copy link
Member

greg0ire commented May 15, 2021

I updated the default branch.

@greg0ire greg0ire force-pushed the 2.2.x-merge-up-into-3.0.x_60a019593b1c08.06542033 branch 5 times, most recently from 1c1f752 to 3fde89b Compare May 15, 2021 20:54
@greg0ire greg0ire force-pushed the 2.2.x-merge-up-into-3.0.x_60a019593b1c08.06542033 branch from 3fde89b to a38ed90 Compare May 16, 2021 09:01
There is only one directory for which this will work.
@alcaeus alcaeus closed this May 16, 2021
@alcaeus alcaeus reopened this May 16, 2021
@alcaeus alcaeus force-pushed the 2.2.x-merge-up-into-3.0.x_60a019593b1c08.06542033 branch from a38ed90 to 2fe30da Compare May 16, 2021 12:44
greg0ire added 2 commits May 16, 2021 15:04
We have found that there were lots of conflicts during the last merge up
to 3.0. Reaching level 7 on lower branches reduces differences between
them and thus the amount of conflits for future merges. It should also
ensure that no new PHPStan error are discovered when merging up because
they are detected at level 7 and not at level 5.
@greg0ire
Copy link
Member

Let's merge #180 before proceeding with this one.

@greg0ire
Copy link
Member

Done, let me merge 2.2.x it into this branch now.

@greg0ire greg0ire force-pushed the 2.2.x-merge-up-into-3.0.x_60a019593b1c08.06542033 branch 4 times, most recently from 634f836 to fdea89e Compare May 16, 2021 17:02
greg0ire
greg0ire previously approved these changes May 16, 2021
@greg0ire greg0ire force-pushed the 2.2.x-merge-up-into-3.0.x_60a019593b1c08.06542033 branch from fdea89e to 89319ee Compare May 16, 2021 17:07
@greg0ire greg0ire merged commit f7f8365 into 3.0.x May 16, 2021
@greg0ire greg0ire deleted the 2.2.x-merge-up-into-3.0.x_60a019593b1c08.06542033 branch May 16, 2021 17:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants