All Versions
Latest Version
Avg Release Cycle
240 days
Latest Release
1900 days ago

Changelog History

  • v1.3.0 Changes

    April 08, 2019

    ๐Ÿš€ This release updates several components to more recent versions, adds better flow to set up self-hosted instances and adds many small improvements to the overall software package.
    Logged users can now add their email to sent messages.

    Major Changes

    • โœ‚ Removed server sign experimental feature, since it had several compatibility issues #289
    • โž• Added reply_to field to messages sent by logged in users #290

    ๐Ÿ›  Minor Changes and bug fixes

    • ๐Ÿ”„ Changed the development workflow to use pipenv #281
    • โšก๏ธ Updated development environment setup instructions #81
    • ๐Ÿ›  Fix box description multi-line issue #280
    • โšก๏ธ Update OpenPGP.js to version 3 #284
    • โž• Added meta description and alt text to home page #283
    • ๐Ÿ›  Fixed missing contact information on closed box page #287

    โšก๏ธ How to update from previous version

    Since the dependency management of the project changed. You will need to change the instruction you usually do to run the project. This time you will need to run the following commands after fetching the new code changes:

    • $ pipenv install
    • ๐Ÿ— $ gulp build
    • $ pipenv run python collectstatic

    ๐Ÿš€ The deployment commands (such as celery and gunicorn) should now be preceded by pipenv run.

  • v1.2.0 Changes

    April 10, 2018

    ๐Ÿš€ This release brings more control to the user key state, automating reminders of expiration for all keys and letting the user audit recent key changes. Also several annoying issues were fixed and more clear instructions were added to the front-end.

    Major changes:

    • ๐Ÿ‘Œ Improved key verification. Now all users are notified, more than once, when their key is about to expire. #274
    • ๐ŸŒฒ Key change log. In order to improve transparency and control to the user, all changes to their "public key" field are record and shown in the settings page. #275

    ๐Ÿ›  Minor changes and bug-fixes:

    • โšก๏ธ Updated the project dependencies (some with vulnerabilities) #256, #261
    • ๐Ÿ›  Fixed settings overlapping button issue #252
    • โž• Added instructions to first time users, when the box list is empty #246
    • โšก๏ธ Users can now update their passwords (those who signed up using email+password) #254
    • โž• Added instance information to the about page #262
    • โž• Added custom error pages #265
    • Re-factor of the key verification function (key_state) #266
    • When generating the submit page, the owner key is verified #267
    • โšก๏ธ Updated openpgp.js to v2.5.3 #268 (solves the extended expiration problem described here)
    • ๐Ÿ›  Fix syntax error caused by an invalid translation block #276

    โšก๏ธ How to update from previous version

    ๐Ÿ‘ In this version SUPPORT_NAME and SUPPORT_EMAIL environment variables are now required. So before going through any of the following steps add them to your environment or .env file.

    โšก๏ธ To update from the previous version, you need to run the following commands after fetching the new code changes:

    • $ pip install -r requirements/requirements.txt
    • ๐Ÿ— $ gulp build
    • $ python collectstatic
  • v1.1.0 Changes

    August 04, 2017

    ๐Ÿ‘Œ Improvements in this release:

    • It is now possible to send small files (#242)
    • ๐Ÿ‘ Hawkpost now supports multiple languages. At this moment the existing ones are Portuguese and English. (#237)
    • โž• Added an extra protection for brute-force attacks to all login forms. (#244).

    โฌ†๏ธ How to upgrade:

    โฌ†๏ธ To upgrade from the previous version you should follow the normal procedure:

    • Pull sources
    • Install new dependencies through pip
    • โš™ Run Migrations
    • ๐Ÿ— Compile the new CSS (gulp build)
    • ๐Ÿฑ Collect the new static assets
    • Start your service
  • v1.0 Changes

    April 19, 2017

    ๐Ÿš‘ This is the first official version. This means that during the last few months the code has been tested and all critical issues (know to date), related to the main feature and purpose of the application, were addressed.