Releases: urda/django-letsencrypt
Django Let's Encrypt - 4.1.0
This is a production-ready release of django-letsencrypt
.
Please refer to the README
of the project to get started.
v4.1.0
There are no major project changes or code updates. This release aligns with
recent Django releases and Python releases.
- Internal Updates:
urls.url
replaced withurls.re_path
.- See commit
d8e823ed5d4dac9a8be885b1f616d7425681d7f7
.
- See commit
- Address
models.W042
warning forletsencrypt.AcmeChallenge
.- See commit
5d644e7e0ec3b5db9e9a28d3b662cc9bab15b188
.
- See commit
- Dependency Updates:
pytz
version2021.3
or greater now required.
- Project Updates
- Testing and other related automations have moved to GitHub Actions.
- Updated
.python-version
file for latest releases.
- No longer supported:
- Python
3.6
. - Travis CI has been dropped from the project.
- Python
- General Updates:
- General
README
updates. - Updated copyright headers.
- We still try and follow the supported versions as detailed:
- General
Django Let's Encrypt - 4.0.0
A quick introduction to this release:
- No major code changes have been made.
- This is to sync with the latest versions of
python
andDjango
available. - If you are a happy user on the previous version
v3.0.1
, the upgrade should be painless **as long as you meet the new version minimums for bothpython
andDjango
. - I made the choice to make this a clean "major version" upgrade as the latest
Django
release schedules have really streamlined working withDjango
. So in order to not disrupt installations since this is a large minimum version change, the choice was made to make this the4.0
release.
This is a production-ready release of django-letsencrypt
.
Please refer to the README
of the project to get started.
v4.0.0
- Breaking Changes
- This was made as an overall major version bump due to the drastic supported
version changes. However, the project and code mostly remain the same. This
version sync allows the project to be easily kept up to date and upgraded. - As per the Django Project Docs.
This project does a major version upgrade to only support:- Release Series
3.1
starting with version3.1.2
. - Release Series
3.0
starting with version3.0.10
. - Release Series
2.2 LTS
starting with version2.2.16
.
- Release Series
- This project supports the following python versions:
- Python
3.6
- Python
3.7
- Python
3.8
- Python
pytz>=2020.1
is now required.- Travis Updates:
- For the time being, we will continue to use
travis
. - Updated to support target versions as detailed for both Django and Python.
- For the time being, we will continue to use
- Operational Excellence Changes:
- Updated
.python-version
file to latest values. - Dropping
slack
notification (for now). - Updated the
example_project
requirements.txt
versions.
- Updated
- General Updates:
- General
README
updates. - Updated copyright headers.
- General
- This was made as an overall major version bump due to the drastic supported
Django Let's Encrypt - 3.0.1
This is a production-ready release of django-letsencrypt
.
Please refer to the README
of the project to get started.
v3.0.1
- Breaking Changes
Django 1.8
support has been dropped.v3.0.0
is the last supported
version for users still onDjango 1.8
.
- Documentation Changes
- Update the
ACME challenge
link inREADME.rst
.
- Update the
- Project Changes
- Disable
universal
wheel creation insetup.cfg
. - Add a
python_requires
entry intosetup.py
.- You can learn more about this feature by reading
this
document.
- You can learn more about this feature by reading
- Bumped to the latest
pytz
, version2018.4
. - Switched from
reStructuredText
toMarkdown
.
- Disable
- Internal Changes
- Bumped
DJANGO_VERSION
targets in.travis.yml
.
- Bumped
- Thanks to Contributors:
Django Let's Encrypt - 3.0.0
This is a production-ready release of django-letsencrypt
.
Please refer to the README
of the project to get started.
v3.0.0
- New Features
django-letsencrypt
now supportsDjango 2.0
!
- Breaking Changes
python2
support has been dropped.v2.0.1
is the last supportedpython2
version for this package.Django 1.10
support has been dropped.v2.0.1
is the last supported
version for users still onDjango 1.10
.
- Project Changes
- Make Travis CI install the proper
django
version first, before installing
the rest ofrequirements.txt
during building. Thanks to
michael-k for providing a pull request. django
tested version bump.1.11.7
to1.11.8
.
- Added
tox
to the project to test multiple versions ofpython
and
django
together.
- Make Travis CI install the proper
Django Let's Encrypt - 2.0.1
This is a production-ready release of django-letsencrypt
.
Please refer to the README
of the project to get started.
v2.0.1
- Internal Changes
- Bumped
DJANGO_VERSION
targets in.travis.yml
. - Bumped to the latest
pytz
, version2017.3
. - Updated
requirements.txt
to separate requirement needs. - Updated
classifiers
insetup.py
. - Organized and updated
Makefile
for easier reference and use. - Configured
Makefile
to support uploading toTest PyPi
.
- Bumped
Django Let's Encrypt - 2.0.0
This is a production-ready release of django-letsencrypt
.
Please refer to the README
of the project to get started.
v2.0.0
- Breaking Changes
- Django
1.9
support has been dropped. There will be no further updates
to fix any issues that may arise from usingdjango-letsencrypt
with
1.9
.
- Django
- Internal Changes
django-letsencrypt
now supports Django1.11
.- Updated builds to use the latest
1.8
,1.10
releases. - Bumped to the latest
pytz
, version2017.2
. - Updated
setup.py
marking any Django1.9
releases as incompatible. - Removed Python
nightly
from Travis builds and testing. - Removed
squashed
migrations from the project. PLEASE NOTE: If you
are on an olderv1.x
release of this project, please make sure to
UPGRADE tov1.1.1
and migrate your database. Failure to do so
will cause a lot of problems, since this release only has the single
migration file.
Django Let's Encrypt - 1.1.1
This is a production-ready release of django-letsencrypt
.
Please refer to the README
of the project to get started.
v1.1.1
- Internal Changes
- Removed the need to render
ACME
responses through a template. Instead
responses are now passed through aHttpResponse
with acontent_type
of
text/plain
. Thanks to Peter Curet
for providing a pull request.
- Removed the need to render
- Corrected
Copyright
dates across the project - Thanks to Contributors:
Django Let's Encrypt - 1.1.0
This is a production-ready release of django-letsencrypt
.
Please refer to the README
of the project to get started.
Do note: this release has a squashed
migration so please be sure to upgrade your installations to this version! The 2.x
release will NOT have the old migrations and will ONLY have the squashed migration for official MySQL
support.
v1.1.0
- Project Changes
- Admin
ordering
for the Django admin page is now down bychallenge
- Removed
created_ts
andupdated_ts
from model - Switched
challenge
andresponse
fromTextField
toCharField
- Admin
- Internal Changes
- Added testing for
detail
view forACME
objects - Removed
migrations.py
thanks to existingexample_project
's manage.py
- Added testing for
Django Let's Encrypt - 1.0.8
This is a production-ready release of django-letsencrypt
.
Please refer to the README
of the project to get started.
v1.0.8
- Project Changes
- Require
pytz
for SQLite users. - Update
travis
branch build targets.
- Require
Django Let's Encrypt - 1.0.7
This is a production-ready release of django-letsencrypt
.
Please refer to the README
of the project to get started.
v1.0.7
- Project changes
- Final "feature" release of the 1.x branch. 2.0 will support
mysql
.
This had to be done due to certain model upcoming model changes, and
will result in a new set of migrations.
- Final "feature" release of the 1.x branch. 2.0 will support