pidgin/nest

ade72caa087d
Add extra way to report security vulnerability

- Add an extra way of reporting a security vulnerability in the project. This
is done by creating a new issue in our issue tracker and ensuring that the
visibility of it is set so that only Pidgin Developers can view it.
- Fix a simple mistake in markdown link syntax in the contributing page which
links back to the Security page.
- Change hardcoded link to list of advisories to a Hugo ref link (if we ever
change the location of the advisories page this will make Hugo throw an error
since it won't be able to find the page, otherwise the link would just end up
being broken without us necessarily knowing about it.

Testing Done:
Ran `dev-server.sh` and verified content looks as intended.

Reviewed at https://reviews.imfreedom.org/r/806/
---
title: "2.14.1 Released!"
date: 2020-06-11T04:48:05-05:00
replaces: []
---
**Updated 2021-02-04 to strike out Bintray mentions as they have
[announced](https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/)
that they are sunsetting it. See
[Bintray Sunsetting]({{< ref "bintray-sunsetting.md" >}})**
So who would have guessed that some stuff would go wrong when we haven't
released in nearly two years?
The changes for 2.14.1 are small but important. There were some issues with
the Windows installer that made it impossible to install 2.14.0 and the
Mercurial revision in the About box was displaying "unknown".
Sorry for the inconvenience that this may have caused!
You can find 2.14.1 on
[SourceForge](https://sourceforge.net/projects/pidgin/files/Pidgin/2.14.1/)
~~as well as on
[Bintray](https://bintray.com/pidgin/releases/pidgin/2.14.1)~~.