Releases: zabartcc/api
Releases · zabartcc/api
v1.4.0 - New Email Provider
What's Changed
- Makes changes necessary to use a new email provider for sending.
- Removes any references to old
@zabartcc.orgemails.
Full Changelog: v1.3.1...v1.4.0
Release v1.3.1
What's Changed
This release includes bug fixes and a slightly reworked event sign-up process to make signing up for events easier.
- Fixes a bug where users retained staff member permissions even after being removed from the roster.
- Replaces the old "enter the callsign of a position" event signup with dropdown options.
- Fixes incorrect staff emails.
- Remove magic CIDs from the codebase.
See: #45
Release v1.2.2
Release v1.2.1
Release v1.2.0
What's Changed
- Release v1.2.0 by @cdconn00 in #31
- Changes website certifications to be GCAP-compliant.
- Allow ECs to see feedback.
Full Changelog: v1.1.6...v1.2.0
v1.1.6 - Update Removal Notice Email Check
v1.1.5 - Hotfixes of v1.1.4
What's Changed
- Added hotfixes to ensure scheduled emails are delivered to controllers.
Full Changelog: v1.1.4...v1.1.5
v1.1.4
What's Changed
- Update StatsController.js by @JWZABARTCC in #20
- Release v1.1.4 by @cdconn00 in #24
- Release 1.1.4 - Environment Check Hotfix by @cdconn00 in #25
Description
- Adds logic to send reminder emails to controllers see #22.
Full Changelog: v1.1.3...v1.1.4
v1.1.3 - Reduce Cookie Lifetime
What's Changed
- JWTs are now only valid for 5 days to prevent issues with submission to VATUSA api.
Full Changelog: v1.1.2...v1.1.3