Passport: Release notes for 0.4.0?

[dlong500]

I understand that I can look through the actual commit history to see specifically what has changed, but is v0.4.0 a breaking change from 0.3.2?

Any chance of getting some summary of changes?

[jaredhanson]

See #598.

There's no changes to the public facing API. Upgrading from 0.3.x to 0.4.x should not cause any compatibility problems.

[jorrit]

In any case, I would like to request the addition of release notes for each release. It is a chore for the maintainers, but it is very welcome for all users, as the presence of these issues indicates.

[semy]

For me after upgrading to 0.4.0 I get a bug:

error: Sending 500 ("Server Error") response: TypeError: next is not a function at attempt (/Users/sg/web/dev/crypto/bitcoin/project/node_modules/passport/lib/middleware/authenticate.js:186:32) at authenticate (/Users/sg/web/dev/crypto/bitcoin/project/node_modules/passport/lib/middleware/authenticate.js:362:7)

Maybe it's better to check this!

[jaredhanson]

@semy - Could you provide any details about how you are using passport that results in that error? This may be an application-level bug, but it is impossible to pinpoint without further information.

[pronebird]

I am updating from 0.2.2 -> 0.4. What a minefield. Is it that so hard to maintain a changelog? Thanks.

[franc23]

I am getting the same error as semy:
TypeError: next is not a function
at attempt (/sourcefolderpath/node_modules/passport/lib/middleware/authenticate.js:186:32)
at authenticate (/sourcefolderpath/node_modules/passport/lib/middleware/authenticate.js:362:7)

Has this issue been resolved and hence closed. If so, could someone point us to the solution please.

[franc23]

https://github.com/ga-wdi-exercises/project3/issues/52 is the resolution for this. Need to pass in "next" as the third parameter.