Deployed documentation does not match released versions

[KennethSundqvist]

The documentation called "latest" includes the maxMessageLength option which isn't in the latest release (1.1.16). Look here: https://raven-js.readthedocs.org/en/latest/config/index.html#maxmessagelength

The latest release (1.1.16) and some releases before it are also not included in the list of versions.

"Latest" ought to be called "Unstable" or "In development" if that is what it documents, and all released versions should be added to the documentation.

I was using the maxMessageLength option because I saw it in the documentation and got very confused why it did not work (because it has not been released yet).

[mattrobenolt]

Yeah, I agree this is confusing. Do you know how I'd do this in Readthedocs? Ideally, yes, I'd make latest be the latest tagged release, and not master.

[KennethSundqvist]

I've never used Readthedocs.

[mattrobenolt]

Alright, then I'll figure out what needs to be done.

[mattrobenolt]

I've released 1.1.17, so that fixes this immediate issue. I'm going to open another to figure out a better way to publish docs though to prevent this from happening again.