* update changelog
* add blog post
* update reference
* update download page
* update version in config.yml
* update announcement
* point reference.html to 1.3.1 docs
Also add reference-1.3.1.html, which redirects to 1.3.0 docs
* update integrity hashes
* redirect reference.html directly to 1.3.0 to avoid double redirect
* Docs(download): mention other CDN
so that developers know their possible alternatives and can decide by themselves which option they want to use for their project.
None of the 3 listed options require any work from Leaflet side (as of today) for new releases, they directly pull updated from npm registry.
cdnjs uses a configuration file in their repo to know which files to fetch from npm registry:
https://github.com/cdnjs/cdnjs/blob/master/ajax/libs/leaflet/package.json
In case the `dist/` folder changes, this configuration file requires manual modification (the community may directly send a PR to do so).
* Docs(download): add disclaimer about external CDN services
in order to try avoiding questions and/or complaints in case of CDN unavailability or any other issue.
