Releases: anonaddy/anonaddy
Releases Β· anonaddy/anonaddy
v1.2.0
- Upgraded application to Laravel 11
- Fixed #632
- Added
applied count
andlast applied
to Rules - Added
Update Available
link above version number when a new release is available
Laravel 11.x requires a minimum PHP version of 8.2.
v1.1.0
- Added
last_forwarded
,last_blocked
,last_replied
andlast_sent
to aliases. You can view each of these by hovering over the "count" in theForwards/Blocks
andReplies/Sends
columns in the table on the aliases page. #119 - You can also now sort your aliases by
Last Forwarded At
,Last Blocked At
,Last Replied At
andLast Sent At
. - Added option in General settings to turn off the above 'last used at' from being saved.
- Added ability for addy.io to automatically decrypt PGP encrypted replies/sends from aliases on the server. They must be encrypted using the
no-reply@addy.io
public key. See #599 for more details. - Attached PGP public keys and signatures will now be removed in any replies/sends in order to prevent accidental leaking of ones real email address.
usernames
,domains
andrecipients
resources will no longer returnaliases
in their API response because there was no pagination. Instead analiases_count
will be returned. You can use get all aliases endpoint specifying the ID of ausername
,domain
, orrecipient
instead.- Fixed #604
- Fixed #605
- Fixed #143
- Fixed #619
v1.0.9
v1.0.8
- Added overrides to fix rollup issue on Docker image
- Fixed return types for account details API endpoint
v1.0.7
- Added query parameters to get aliases API endpoint
recipient
,domain
,username
- https://app.addy.io/docs/#aliases-GETapi-v1-aliases - Fixed return type in account details API endpoint
- Updated to Vite 5
v1.0.6
v1.0.5
- Added missing limits to
api/v1/account-details
endpoint
v1.0.4
v1.0.3
- Updated domain options endpoint
v1.0.2
- Fixed issue with email verification notification
- Prevented alias count request being made if no recipients are found for a search