please keep release names in sync with tags
See original GitHub issuerelease name (also listed on project main page) lists: 2020.11.1 but the tag is 20.11.1, can you please rename the release to match the tag. This could save time when bumping as there is no 2020.11.1 on pypi.
stderr:
ERROR: Could not find a version that satisfies the requirement flake8-bugbear>=2020.11.1 (from versions: 16.4.0, 16.4.2, 16.6.0, 16.6.1, 16.7.0, 16.7.1, 16.9.0, 16.10.0, 16.10.1, 16.11.0, 16.11.1, 16.12.0, 16.12.1, 16.12.2, 17.2.0, 17.3.0, 17.4.0, 17.12.0, 18.2.0, 18.8.0, 19.3.0, 19.8.0, 20.1.0, 20.1.1, 20.1.2, 20.1.3, 20.1.4, 20.11.1)
ERROR: No matching distribution found for flake8-bugbear>=2020.11.1
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6
Top Results From Across the Web
How to Manage Releases with Semantic Versioning and Git ...
Using a standard versioning system, such as semantic versioning with Git, and knowing how to use Git tags to easily tag a repository...
Read more >Use Tags and Smart Folders in Notes on your iPhone, iPad ...
With iOS 15 and iPadOS 15, you can use tags to quickly categorize your notes so you can easily find them later. Just...
Read more >In git, how do I sync my tags against a remote server?
Either way is a hack, and the "right" answer is to stop changing tags all the time.
Read more >Sync release version. · Actions · GitHub Marketplace
This example assumes a post release operation i.e changes are made to a README after a new version is releaased.
Read more >Tagging files - Cloud-Sync documentation
If you type a new tag name, the visible tags list will be filtered, based on the text that you've typed. ... So...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

No, thanks for reporting and thanks for sharing that it’s been helpful. This was just tongue in cheek poking at myself.
I had a similar ‘issue’, when I went to GitHub to see the latest release and put
20.3.2in my requirements. The installation failed because the actual latest release (when going to PyPi page) is21.3.2.