# We are close to releasing JabRef 5.10

**URL:** https://discourse.jabref.org/t/we-are-close-to-releasing-jabref-5-10/3874
**Category:** Beta Testing
**Created:** [July 2, 2023, 9:38am UTC](https://discourse.jabref.org/t/we-are-close-to-releasing-jabref-5-10/3874 "2023-07-02T09:38:02Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![ThiloteE](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/thilotee/32/1008_2.png) [@ThiloteE](https://discourse.jabref.org/u/ThiloteE)
#### Post date: [July 2, 2023, 9:38am UTC](https://discourse.jabref.org/t/we-are-close-to-releasing-jabref-5-10/3874/1 "2023-07-02T09:38:03Z")

</div>

Hello folks,

there is progress and a new version will be released in one of the coming weeks. The main reason why I text you today is to ask for beta testing 😇

While we look forward to any feedback about the new version, there is [a particular security relevant change](https://github.com/JabRef/jabref/pull/10044) that requires testing. For all the people that use JabRef via Proxy, please check out the newest development version. You can download it from here: [https://builds.jabref.org/main/](https://builds.jabref.org/main/)

### This needs testing:

1. Check if the proxy configuration works.
2. Then close and restart JabRef and check if the proxy configuration still works. Including Websearch.

### Because:

- We added an option to encrypt and remember the proxy password.
- We now encrypt and store the custom API keys in the OS native credential store

Greetings,

ThiloteE