(mp3tag) v3.33.1 released on 6 February 2026

[Caligatio]

Checklist

• I have checked the moderation queue that no new version has been submitted (only visible when logged in), or the submitted package version has failed the automated checks.

Please navigate to the following link to view the moderation queue.

• I have verified that the new version is a stable release.
• I have looked to see if there are any Bug reports that prevents a new version being submitted and that no existing Outdated Reports have been created.
• I have verified the new version has a Windows binary (EXE or MSI installer, Zip or other archive, etc).
• I have verified that this is the correct repository, and the package is maintained by the chocolatey-community user.

New Software Version

3.33.1

Download location

https://www.mp3tag.de/en/download.html

Package Page

https://community.chocolatey.org/packages/mp3tag

[github-actions]

Thanks for raising this issue!

The packages within this repository are maintained by a small team of volunteer Community Maintainers, in their own time. Their time, like yours is important. Please help them by not wasting it.

This is a community repository where the expectation is that everybody will get involved by raising pull requests to fix problems they find. This will also allow that problem to be fixed more quickly as you don't have to wait for a member of the Community Maintainer Team to pick it up.

If you are unable to fix the issue yourself, the Community Maintainers Team will look at it when time allows. There are no service level agreements, nor should there be any expectation on when people can resolve issues in their own time.

A few dos and don'ts:

• Do provide as much information as you can in any issue that you raise.
• Don't complain that an issue has not yet been picked up or resolved. You are expected to help out in this community maintained repository. If you are unable to do so, don't complain when others don't adhere to your timelines. There is no SLA nor should you have any expectation of one.
• Do read the CONTRIBUTING and COMMITTERS documentation before raising a pull request as it contains valuable information on what automation is used in this repository.
• Do read the Code of Conduct.
• Don't post your frustration in comments. The Community Maintainers Team are not a punching bag for your frustration. You will only end up banned from the repository.

Thank you.
(Automatically posted message)