Closed ozten closed 11 years ago
Looks like the plan is to cut a new 0.4.x release of node-openid, right? If so, once it lands in npm, passport-openid should pull it in automatically when you install modules, since its pegs this dependency at 0.4.x.
I'll keep tabs on the release, and will change the dependency versions if needed. Ping me here if any action is needed.
Tangentially related, but from crawling around the issues, looks like a new node-oauth release should be expected too, right? From the changeset, I'm hoping that can stay in the 0.9.x series and get new features downstream transparently as well.
Awesome, thanks @jaredhanson.
Looks like openid v0.5.0 was just published to npm. I've followed suit and published passport-openid v0.3.0, which also includes PAPE support.
All latest code is now in npm, closing.
Right on.
HTTP(S) proxy support for node-openid has landed on master.
We'd like passport-yahoo to get this updated dependency.
passport-openid currently depends on 0.4.x.
I think 0.4.x is still the current path to their next release, so I don't think we'd need to back-port that patch.
Any way we can help make this happen?
See https://github.com/havard/node-openid/issues/83