Bump version to 2.2.0

[getzze]

Next steps:

• merge to master (I would prefer to use main but only @Diaoul can change that, so let's use master for this release).
• tag the new version
• make a release on github and pypi (any idea how?)

There is only one breaking change that is the default encoding is now 'utf-8' instead of the original encoding, so I think it's fine not to bump to version 3.0

[Diaoul]

merge to master (I would prefer to use main but only @Diaoul can change that, so let's use master for this release).

Let me know where and when I should do this 👍

[getzze]

merge to master (I would prefer to use main but only @Diaoul can change that, so let's use master for this release).

Let me know where and when I should do this 👍

I just pushed a main branch to this repo, you have to make it the default branch in Settings - General - Default Branch. Thanks!

[getzze]

I just saw you updated enzyme, I'll update the version for the dependency then.

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
subliminal
__init__.py
Project Total

This report was generated by python-coverage-comment-action

[Diaoul]

Yes, please run some tests in case I broke something 😆

[Diaoul]

@getzze I did something else which seems more the way to go

• Changed default branch to develop
• Renamed develop to main

👉 this way the PRs are all switched against main

[getzze]

Ah cool, that's even better!

Tests are passing with the last enzyme version 🎉

[getzze]

I saw you added a publish github action to enzyme, if we add it to subliminal it will automatically publish the new tagged version to Pypi?

[ptrcnull]

one little nitpick that i didn't catch earlier: do we have to print Not using any configuration file. every single time? wouldn't it be better as a debug print?

[getzze]

Yes, I don't like it either.
The problem is that when the config file is parsed, the logger is not set yet therefore the message is "printed".
Another problem I saw is that the two options --debug and --verbose are redundant.

[ptrcnull]

i'd say redundant options are alright, synonymous flags just make it easier for users to get it first try :P

[Diaoul]

it will automatically publish the new tagged version to Pypi?

Yes, not tagged though, released and published on GitHub

1. That usually start with a tag
2. Then you go do make a new release based on that tag (draft or otherwise), you can decide if beta or not
3. Only when the release is "published" (i.e. not draft anymore) the workflow will trigger and publish on PyPI 👍

Automation all the way 🤖

[Diaoul]

I just did all the config so it works as well for Subliminal: there is a PYPI_TOKEN secret and GitHub is a trusted publisher 👍
You can just copy pasted the publish.yaml file (must be this name) 👏

[getzze]

I added the publish.yaml file and a .readthedocs.yaml file also. I will draft a release!

[ptrcnull]

good job!! thanks everyone, really happy to see a new release ^^

[getzze]

I managed to make the release! Thank you all!
I changed the github action to automatically make a Github release and a Pypi release when a new tag is added.
The documentation in readthedocs was not updated though. If found this gha, but I am not sure it would work.