Releases: eveseat/notifications
Releases · eveseat/notifications
v5.0.0
What's New
- SeAT provides Discord native integration (no more
/slack
appendix is required) by @warlof and @recursivetree in #81 - SeAT give ability to use Mention feature inside dispatched notifications
- Administrators can now test their setup by triggering a test notification by @recursivetree in #79
What's Changed
- add contract notifications by @recursivetree in #74
- refactor: add slack rate limiting by @recursivetree in #75
- fix: use rate limiting for contracts by @recursivetree in #76
- refactor: remove 'my notifications' page by @recursivetree in #78
- chore: improve logging on observers by @warlof in #80
Breaking Changes
- SeAT Core (all packages published against @eveseat organization) routes are now prefixed with
seatcore::
by @warlof and @recursivetree in b4765f7 and 29b053c
New Contributors
- @recursivetree made their first contribution in #73
Full Changelog: 4.3.3...5.0.0
v4.3.3
v4.3.2
v4.3.1
Fix
- prevent squad notifications to interfere with squads events when an user is either added or removed (eveseat/seat#769).
v4.3.0
Enhancements
- provide notifications for squad module including new application, new member and member removal
Fix
- update Tinker version to fix deprecated dependency
CAUTION
If you're using a bare-metal installation of SeAT (non Docker), you will have to manually edit your composer.json
file located at root SeAT installation directory (default is /var/www/seat/composer.json
) and alter the line 19 from "laravel/tinker": "^1.0",
to "laravel/tinker": "^2.5",
in order to be able to deploy that new version.
v4.2.0
v4.1.0
Enhancements
- a new notification is available to track attacked customs offices (eveseat/seat#681)
Fix
- corporation new application notification was not sent (eveseat/seat#682)