I'll have to dig up exactly when it was, but the most recent incident was unfortunately with crypto, in the middle of the v0.6 series, when behavior of 'binary' changed. Nothing serious, but it locked me out of my application, and (theoretically) reduced the security of my tokens by about a dozen bits (concern worthy but not much more when I'm using 256 bits or more).
Before that was in v0.4 and had something to do with events. And another which is probably so old I'm not sure it's going back and figuring out what happened. And now that I'm thinking of it, there's one more involving pause()ing HTTP streams. If that was during a minor version increment, it still should have been a major version increment. Again I have no problems with improvements, but people really need to be in the habit of marking their breakages. Otherwise version numbers are meaningless, and we should move to Git commit ids (or "commits in ancestry" if you really like growing numbers). On Thursday, January 24, 2013 2:28:24 PM UTC-7, Mikeal Rogers wrote: > > > On Jan 24, 2013, at January 24, 20131:03 PM, Austin William Wright < > [email protected] <javascript:>> wrote: > > Node.js has broken reverse compatibility three times on me, and not in a > minor version update, during a *patch* update. > > > What broke, and in which versions? I'm not aware of compatibility changes > in minor versions since pre-0.4 > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
