Update changelog and bump version

[mlissner]

This is a pretty straightforward one with a major version bump — 3.0.0, baby!

This will be the first automated release, so I think the process is:

• Merge this (assuming you like it)
• Go to PyPi and generate a token
• Go to this project's Github settings and create a token named PYPI_TOKEN
• Tag the merge commit with v3.0.0
• Push the tag
• While you wait for Github Actions to push to PyPi, do a release if you please :)

I think that should be it!

[pcraciunoiu]

@mlissner how did you generate this changelog? Since it may be something that needs maintained, I'm hoping it's easy for me to do it too moving forward...

[mlissner]

By hand, I'm afraid, but the idea is that you could ask folks to update the ## Upcoming section in each PR moving forward, then your task is just to ① enforce that (this is the hard part!), and ② Tweak the changelog to move the ## Upcoming, ## Current and ## Past headers around, which is pretty easy.

I haven't looked at the automated ways of generating changelogs much. I suspect they'd be a pain to deal with in an open source project since they usually rely on commit messages being perfectly formatted (I think).

[pcraciunoiu]

OK I'm not opposed to having it updated, but I won't guarantee it's always up to date :)

Will follow these steps soon!

[pcraciunoiu]

After some trial and error with the multilayered env vars in the new GitHub Secrets, I only had to make a small change to the build workflow in but it worked - #241

Publish job - https://github.com/django-ses/django-ses/actions/runs/2074206130

On PyPi: https://pypi.org/project/django-ses/3.0.0/

And GH release: https://github.com/django-ses/django-ses/releases/tag/v3.0.0

Try it out and let me know if you have any issues or spot anything. I did a quick spot check by downloading the archives from PyPi and v2.6.1 and v3.0.0 look to have similar structures, with a few differences in packaging files, hopefully all to be expected.

Thanks again!