Release 3.0.0-alpha.2

[dsbilling]

No description provided.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
13912195	Triggered	Generic Password	d53bd9e	docker-compose.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[what-the-diff]

PR Summary

• Revamped Release Workflow: The triggering of the release procedure has shifted from 'released' to 'published', and the source data's reference branch has been updated to 'develop' from 'main'.
• Added new user interest feature: The PR introduces an event_interests table which captures user's preferences relation to events. Foreign key constraints have been upheld.
• Improved import arrangement: A necessary re-association of the import commands in __init__.py to accommodate the new event_interest model has been made.
• API Endpoints Enhanced: The endpoint routes for event interests have been re-styled (from /{event_id} to /events/{event_id}/interests) leading to better understanding and a more coherent set of endpoints being featured.
• Frontend API Calls Altered: To ensure uniformity with the updated endpoint structure, event interest API call paths inside the event-interest.ts file have been switched.
• Housecleaning of Unused Files: Deleted stray files status.ts and Profile.tsx that were not currently useful to the overall system.
• Launched Docker Solutions for PostgreSQL: New Docker files and Docker Compose files have been drafted for smoother PostgreSQL operation based on a specified, optimal configuration.
• Frontend Imports Reordered and Formatted: Unneeded import statements have been removed from nav-user.tsx, and the changelog.tsx file has been styled consistently.
• Healthchecks are in place: To ensure smooth functioning, healthchecks have been incorporated in the Docker Compose files for frontend and backend services.
• Code Readability Enhanced: Several minor adjustments have been made throughout the codebase to improve readability and consistency, such as indentation and line formatting.