‼️ Notice to Developers: Possibly Required Reset of "master" Branch

[kblaschke]

This announcement is only for developers working with libprojectM's Git repository, using either a local clone or a GitHub fork of it and having synced it recently or have auto-sync enabled on a GitHub fork.

We're sorry to announce that some commits have mistakenly being pushed to the master branch of the main libprojectM repository instead of a fork, which were removed by resetting master to the previous state.

If you've not checked or synced the https://github.com/projectM-visualizer/projectm repository after 4:00 UTC on April 30, 2025, and not have auto-sync enabled on your fork, you don't have to take action. Otherwise, here's what you need to do:

Local Repository

• Make sure your local changes are stashed or committed to a separate branch and you don't have any own commits in master.
• Check out master.
• Make sure you've added the upstream repository as a remote, in our examples called origin.
• Reset your local master to the current upstream masterusing git reset --hard origin/master.

GitHub Fork

• Disable auto-sync for your fork if enabled.
• Disable force-push restrictions on your fork's master branch.
• Clone/update a local repository and proceed with the steps noted under "Local Repository" above.
• Force-push your now reset local master branch to your fork.
• Reenable branch protection and auto-sync as needed.

[actionless]

could you please tag a new release, because the current master not describing into the correct tag:

$ git describe --long | sed 's/^v//;s/\([^-]*-g\)/r\1/;s/-/./g'
3.1.8.r623.gc94063bcb

should be instead:

4.1.4.rXXX.gc94063bcb

[actionless]

please ignore the message above, i was running a wrong command:

$ (git describe --tags --long | sed 's/^v//;s/\([^-]*-g\)/r\1/;s/-/./g') || echo 0.0.0.r$(git rev-list --count HEAD).g$(git rev-parse --short HEAD)
4.1.0.r44.gc94063bcb

[actionless]

although, actually, master branch still weirdly resolves to 4.1.0 instead of 4.1.4

[kblaschke]

To get the latest 4.1.x release, please use the v4.1.x branch. Master is currently the 4.2.0 WIP (or "development branch"), and not necessarily stable or feature-complete. It will be updated accordingly upon release. I've thought about using a version number that better reflects this, e.g. 4.1.9999 for the current state of master.

On each minor/major release, we'll create another patch branch for that version, so we can easily backport bug fixes, security patches and other improvements to previous releases while being able to stabilize the master branch before tagging the next release.