Skip to content

Tags: camelot-dev/camelot

Tags

v2.0.0

Toggle v2.0.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore(release): prepare 2.0.0 (#816)

Co-authored-by: bosd <ebo@stefcy.com>

v2.0.0rc1

Toggle v2.0.0rc1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix(release): --clobber the GitHub-release asset upload (unblocks PyP…

…I publish) (#812)

Co-authored-by: bosd <ebo@stefcy.com>

v1.0.9

Toggle v1.0.9's commit message
release v1.0.9

v1.0.8

Toggle v1.0.8's commit message
Release v1.0.8

v1.0.7

Toggle v1.0.7's commit message
Release v1.0.7

v1.0.6

Toggle v1.0.6's commit message
release v1.0.6

v1.0.4

Toggle v1.0.4's commit message
"Fixup workflow, only upload files pypi can handle"

v1.0.3

Toggle v1.0.3's commit message
Release 1.0.3

v1.0.2

Toggle v1.0.2's commit message
release 1.0.5

v1.0.1

Toggle v1.0.1's commit message
I've addressed a few regressions and documentation issues that came u…

…p after a repository change:

- I updated the release workflow in `.github/workflows/release.yml` to use `release-drafter`. This will now automatically create draft releases with changelogs based on merged pull requests. The release can then be manually published from the GitHub UI, which triggers the PyPI publishing workflow.
- I added the `Programming Language :: Python :: 3` classifier to `pyproject.toml`. This should fix the issue where the Python version shield on your README was showing "missing".
- I added documentation for the new release process in `docs/dev/releasing.rst` and linked it in the main `index.rst`.
- As you requested, I restored the emoticons to the workflow file name.

I encountered some timeouts while running the test suite. However, since these changes are isolated to configuration, CI, and documentation, I believe the risk of a code regression is minimal.