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

When i do a composer update, i do not get the new version, is this normal? #381

Closed
j0k3r opened this issue Dec 30, 2020 · 1 comment
Closed

Comments

@j0k3r
Copy link
Collaborator

j0k3r commented Dec 30, 2020

Thanks @k00ni Just one question, sorry this is certainly a stupid question, but when i do a composer update, i do not get the new version, is this normal?

Originally posted by @mathias1981 in #380 (comment)

@k00ni
Copy link
Collaborator

k00ni commented Dec 30, 2020

There are no stupid questions :)

I think there is a misunderstanding here. Latest version of PDFParser is still 0.17.1. But there are changes since which can be seen here: v0.17.1...master. My fix for #367 is not part of the master (branch) yet, but will be after it has been reviewed (=accepted) and merged. Then you will see it in that list also.

To be able to get this fix (and all other changes since 0.17.1) I have to create a new version manually. This I (or others) will do after #380 got merged. Hope it helps.

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

No branches or pull requests

2 participants