Skip to content

Commit

Permalink
🔖 bump version 0.1.0rc5 -> 0.1.0 (#99)
Browse files Browse the repository at this point in the history
  • Loading branch information
joshuadavidthomas authored Oct 27, 2023
1 parent 4de8a72 commit 398781c
Show file tree
Hide file tree
Showing 3 changed files with 29 additions and 13 deletions.
36 changes: 26 additions & 10 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 <[email protected]> (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
4 changes: 2 additions & 2 deletions pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ authors = [
{name = "Josh Thomas", email = "[email protected]"},
]
classifiers = [
"Development Status :: 3 - Alpha",
"Development Status :: 4 - Beta",
"Framework :: Django",
"Framework :: Django :: 3",
"Framework :: Django :: 3.2",
Expand Down Expand Up @@ -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]"
Expand Down
2 changes: 1 addition & 1 deletion src/email_relay/__init__.py
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
from __future__ import annotations

__version__ = "0.1.0rc5"
__version__ = "0.1.0"

0 comments on commit 398781c

Please sign in to comment.