From 398781c38a7dbdcae7f0d4667facda285f9d2b32 Mon Sep 17 00:00:00 2001
From: Josh Thomas <josh@joshthomas.dev>
Date: Fri, 27 Oct 2023 17:35:17 -0500
Subject: [PATCH] :bookmark: bump version 0.1.0rc5 -> 0.1.0 (#99)

---
 CHANGELOG.md                | 36 ++++++++++++++++++++++++++----------
 pyproject.toml              |  4 ++--
 src/email_relay/__init__.py |  2 +-
 3 files changed, 29 insertions(+), 13 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 570a361..1aece31 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -13,13 +13,29 @@ Initial release!
 
 ### Added
 
-- An email backend that stores emails in a database ala a Message model rather than sending them via SMTP or other means
-- A database backend that routes writes to the Message model to a separate database
-- A Message model that stores the contents of an email
-- A relay service intended to be run separately, either as a standalone Docker image or as a management command within a Django project
-- Initial documentation (README.md)
-- Initial tests
-- Initial CI/CD (GitHub Actions)
-
-[unreleased]: https://github.com/westerveltco/django-email-relay/compare/HEAD...HEAD
-[0.1.0]: https://github.com/westerveltco/django-email-relay/releases/tag/v0.1.0rc1
+- An email backend that stores emails in a database ala a Message model rather than sending them via SMTP or other means.
+    - Designed to work seamlessly with Django's built-in ways of sending emails.
+- A database backend that routes writes to the Message model to a separate database.
+- A Message model that stores the contents of an email.
+    - The Message model stores the contents of the email as a JSONField.
+    - Attachments are stored in the database, under the 'attachments' key in the JSONField.
+        - Should be able to handle anything that Django can by default.
+- A relay service intended to be run separately, either as a standalone Docker image or as a management command within a Django project.
+    - A Docker image is provided for the relay service. Currently only PostgreSQL is supported as a database backend.
+    - A management command is provided for the relay service. Any database backend supported by Django should work (minus SQLite which doesn't make sense for a relay service).
+    - The relay service can be configured with a healthcheck url to ensure it is running.
+- Initial documentation.
+- Initial tests.
+- Initial CI/CD (GitHub Actions).
+
+### New Contributors!
+
+- Josh Thomas <josh@joshthomas.dev> (maintainer)
+- Jeff Triplett <@jefftriplett>
+
+### Thanks ❤️
+
+Big thank you to the original authors of [`django-mailer`](https://github.com/pinax/django-mailer) for the inspiration and for doing the hard work of figuring out a good way of queueing emails in a database in the first place.
+
+[unreleased]: https://github.com/westerveltco/django-email-relay/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/westerveltco/django-email-relay/releases/tag/v0.1.0
diff --git a/pyproject.toml b/pyproject.toml
index 8881094..1a2d743 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -7,7 +7,7 @@ authors = [
   {name = "Josh Thomas", email = "josh@joshthomas.dev"},
 ]
 classifiers = [
-  "Development Status :: 3 - Alpha",
+  "Development Status :: 4 - Beta",
   "Framework :: Django",
   "Framework :: Django :: 3",
   "Framework :: Django :: 3.2",
@@ -94,7 +94,7 @@ path = "src/email_relay/__init__.py"
 [tool.bumpver]
 commit = true
 commit_message = ":bookmark: bump version {old_version} -> {new_version}"
-current_version = "0.1.0rc5"
+current_version = "0.1.0"
 push = false   # set to false for CI
 tag = false
 version_pattern = "MAJOR.MINOR.PATCH[PYTAGNUM]"
diff --git a/src/email_relay/__init__.py b/src/email_relay/__init__.py
index 11a88f8..f11ec6a 100644
--- a/src/email_relay/__init__.py
+++ b/src/email_relay/__init__.py
@@ -1,3 +1,3 @@
 from __future__ import annotations
 
-__version__ = "0.1.0rc5"
+__version__ = "0.1.0"