zend-authentication
zend-authentication copied to clipboard
remove @deprecated class and method
bump php version in composer :-)
@vaclavvanik This PR does not imply a change in PHP requirements.
Oh, you are right. I thought rashly
rebased
I'll close this until v3 development of this component begin
:(. this is why I think we need to have per-branch : 2.4, 2.5, 2.6, 3.0 , early works merged is better imo. //cc @gianarb @weierophinney
This can begin now on the develop branch. Essentially, this PR is indicating that we have developers wanting to work on BC-breaking changes, which means that the develop branch should become the 3.0 branch. I'll review, and, on merge, bump the branch aliases for the develop branch.
mergeable? Or i should re-create PR against develop branch?
@weierophinney I've changed target branch to develop
@weierophinney merge-able ?
Is there anything I can do to get it merged? Thank you.
This repository has been closed and moved to laminas/laminas-authentication; a new issue has been opened at https://github.com/laminas/laminas-authentication/issues/9.
This repository has been moved to laminas/laminas-authentication. If you feel that this patch is still relevant, please re-open against that repository, and reference this issue. To re-open, we suggest the following workflow:
- Squash all commits in your branch (
git rebase -i origin/{branch}
) - Make a note of all changed files (`git diff --name-only origin/{branch}...HEAD
- Run the laminas/laminas-migration tool on the code.
- Clone laminas/laminas-authentication to another directory.
- Copy the files from the second bullet point to the clone of laminas/laminas-authentication.
- In your clone of laminas/laminas-authentication, commit the files, push to your fork, and open the new PR. We will be providing tooling via laminas/laminas-migration soon to help automate the process.