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

Bump xmlseclibs version #98

Merged
merged 1 commit into from
Jun 16, 2017
Merged

Bump xmlseclibs version #98

merged 1 commit into from
Jun 16, 2017

Conversation

chris1312
Copy link
Contributor

#97

@coveralls
Copy link

Coverage Status

Coverage remained the same at 67.553% when pulling 3d0e659 on chris1312:master into 3c5f58c on simplesamlphp:master.

@thijskh
Copy link
Member

thijskh commented Jun 6, 2017

If you also bump the composer.lock then Travis can show us whether the testsuite still passes (spoiler: it does).

@chris1312
Copy link
Contributor Author

Sorry, I did not catch..

This project does not contain composer.lock. Do you say that you want me to commit composer.lock into the project? I see in Travis build (e.g. for PHP7) that the 3.0.0 version of xmlseclibs was installed.

@thijskh
Copy link
Member

thijskh commented Jun 6, 2017

Indeed, my mistake. The tests pass, that's a good start!

@chris1312
Copy link
Contributor Author

Is there anything more you expect from this pull request?

@thijskh
Copy link
Member

thijskh commented Jun 7, 2017

Not per se, just need to find some time to do some further testing, then merge.

@jaimeperez
Copy link
Member

Hi @chris1312!

I would also like to see how the discussion in robrichards/xmlseclibs#123 ends up before we trust the 3.0.0 to be stable and final. I'm afraid of bumping the version here to see days afterwards that it was removed to merge that PR instead.

That said, I'm really looking forward to this myself too...

@chris1312
Copy link
Contributor Author

OK, sure!

@thijskh
Copy link
Member

thijskh commented Jun 7, 2017

@jaimeperez Those two pr's are functionally the same, right? So would it matter much to change later?

@jaimeperez
Copy link
Member

Nah, I don't think there'll be changes to the code (not significantly anyway). I'm just afraid of some kind of mess if Rob tries to fix it so that proper credit is given to the code by merging the existing PR, but he doesn't seem to be responsive at all, and if something breaks, we can always fix it.

So given that we are in master here, 👍 from me too.

@thijskh
Copy link
Member

thijskh commented Jun 16, 2017

Thanks for your contribution!

@thijskh thijskh merged commit cea679a into simplesamlphp:master Jun 16, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants