Fluorine-Manager.git/.github, branch main

Prepare 0.3.0 release

2026-06-17T07:08:53Z

release: preserve draft stable releases

2026-05-24T19:04:23Z

release: prepare 0.2.2 stable

2026-05-24T18:48:04Z

Update MO2 beta 12 integration

2026-05-24T05:19:52Z

build: migrate Dockerfile + plugin_python from pip/poetry to uv

2026-05-16T17:57:25Z

Dockerfile: drop apt python3/python3-pip, copy the uv static binary from ghcr.io/astral-sh/uv:latest, install python-build-standalone via `uv python install` (replacing the manual curl), run aqtinstall via `uv tool run`, install build-time packages via `uv pip install --system --break-system-packages --python ...`. Same swap applied to the CI workflow's inline package-install step. plugin_python: convert pyproject.toml from [tool.poetry] to PEP 621 [project] + [dependency-groups], drop poetry.lock, replace abatilo/actions-poetry + `poetry install/run` with astral-sh/setup-uv + `uv sync/run` in libs/plugin_python/.github/workflows/linting.yml. Co-Authored-By: Claude Opus 4.7 (1M context)

ci: install runtime python deps inside build container

2026-05-15T00:53:59Z

The builder image is pulled from GHCR and reused across CI runs, so Dockerfile changes to its pip install line don't take effect until docker.yml is manually triggered. Move the install into the CI build step so PRs that add new python deps work without an image rebuild. Co-Authored-By: Claude Opus 4.7 (1M context)

ci: bring back stable releases on v* tag push

2026-05-02T19:37:51Z

Local stable builds picked up host CPU flags (AVX-512) and shipped binaries that crashed on user CPUs without those instructions. CI runs on generic GitHub-hosted x86-64 runners, so all release builds need to go through it now. - Trigger workflow on push of any v* tag in addition to main. - Resolve channel from the ref: tags/v* -> stable, otherwise beta. - Tarball name follows channel: fluorine-manager-.tar.gz on stable, fluorine-manager-beta.tar.gz on beta. - Beta publish step gated on channel==beta to avoid double-publishing when a tag also lives on main. - New "Publish stable release" step creates/updates a release at the tag, marks it --latest, and attaches the versioned tarball. To cut v0.2.0: `git tag v0.2.0 && git push origin v0.2.0`. Co-Authored-By: Claude Opus 4.7 (1M context)

Fix Updates tab compile + CI failure propagation

2026-04-24T00:37:07Z

- settingsdialogupdates.cpp missed an include of settings.h (it was only getting the forward-declared version from settingsdialog.h), which broke every settings().setX() call. Now included directly. - UpdatesSettingsTab is not a QObject so it has no tr() member; add Q_DECLARE_TR_FUNCTIONS to get a static tr() via QCoreApplication. - CI: the docker run chained commands with `;` so a ninja failure got masked by the trailing `ccache -s`. Capture the build-inner.sh exit status and `exit $status` at the end so real build failures fail the step instead of bleeding into the tar packaging step and producing a confusing "Cannot stat: No such file" error. Co-Authored-By: Claude Opus 4.7 (1M context)

ci: chown build dir before packaging tarball

2026-04-23T21:26:09Z

The docker build runs as root inside the container and the bind-mounted build/ tree ends up root-owned on the runner. The runner-user tar step then can't create the archive. Fix up ownership before packaging. Co-Authored-By: Claude Opus 4.7 (1M context)

Drop stable release step from CI

2026-04-23T21:16:09Z

Stable releases are cut manually against a tag (see CHANGELOG.md). CI only publishes the rolling `beta` release now, so the always-skipped Publish stable release step and the `v*` tag trigger were just noise in the job graph. Co-Authored-By: Claude Opus 4.7 (1M context)