Skip to content

Commit 398781c

Browse files
🔖 bump version 0.1.0rc5 -> 0.1.0 (#99)
1 parent 4de8a72 commit 398781c

File tree

3 files changed

+29
-13
lines changed

3 files changed

+29
-13
lines changed

CHANGELOG.md

Lines changed: 26 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -13,13 +13,29 @@ Initial release!
1313

1414
### Added
1515

16-
- An email backend that stores emails in a database ala a Message model rather than sending them via SMTP or other means
17-
- A database backend that routes writes to the Message model to a separate database
18-
- A Message model that stores the contents of an email
19-
- A relay service intended to be run separately, either as a standalone Docker image or as a management command within a Django project
20-
- Initial documentation (README.md)
21-
- Initial tests
22-
- Initial CI/CD (GitHub Actions)
23-
24-
[unreleased]: https://github.com/westerveltco/django-email-relay/compare/HEAD...HEAD
25-
[0.1.0]: https://github.com/westerveltco/django-email-relay/releases/tag/v0.1.0rc1
16+
- An email backend that stores emails in a database ala a Message model rather than sending them via SMTP or other means.
17+
- Designed to work seamlessly with Django's built-in ways of sending emails.
18+
- A database backend that routes writes to the Message model to a separate database.
19+
- A Message model that stores the contents of an email.
20+
- The Message model stores the contents of the email as a JSONField.
21+
- Attachments are stored in the database, under the 'attachments' key in the JSONField.
22+
- Should be able to handle anything that Django can by default.
23+
- A relay service intended to be run separately, either as a standalone Docker image or as a management command within a Django project.
24+
- A Docker image is provided for the relay service. Currently only PostgreSQL is supported as a database backend.
25+
- 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).
26+
- The relay service can be configured with a healthcheck url to ensure it is running.
27+
- Initial documentation.
28+
- Initial tests.
29+
- Initial CI/CD (GitHub Actions).
30+
31+
### New Contributors!
32+
33+
- Josh Thomas <[email protected]> (maintainer)
34+
- Jeff Triplett <@jefftriplett>
35+
36+
### Thanks ❤️
37+
38+
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.
39+
40+
[unreleased]: https://github.com/westerveltco/django-email-relay/compare/v0.1.0...HEAD
41+
[0.1.0]: https://github.com/westerveltco/django-email-relay/releases/tag/v0.1.0

pyproject.toml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ authors = [
77
{name = "Josh Thomas", email = "[email protected]"},
88
]
99
classifiers = [
10-
"Development Status :: 3 - Alpha",
10+
"Development Status :: 4 - Beta",
1111
"Framework :: Django",
1212
"Framework :: Django :: 3",
1313
"Framework :: Django :: 3.2",
@@ -94,7 +94,7 @@ path = "src/email_relay/__init__.py"
9494
[tool.bumpver]
9595
commit = true
9696
commit_message = ":bookmark: bump version {old_version} -> {new_version}"
97-
current_version = "0.1.0rc5"
97+
current_version = "0.1.0"
9898
push = false # set to false for CI
9999
tag = false
100100
version_pattern = "MAJOR.MINOR.PATCH[PYTAGNUM]"

src/email_relay/__init__.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
11
from __future__ import annotations
22

3-
__version__ = "0.1.0rc5"
3+
__version__ = "0.1.0"

0 commit comments

Comments
 (0)