1.5.1-rc.1
Pre-release
Pre-release
·
158 commits
to main
since this release
1.5.1-rc.1 - 2026-08-08
Candidate for 1.5.1. It carries one fix that matters more than the rest: writes were refused on any install reached directly on a mapped port.
Fixed
- Saving settings, logging in, and every other write now work when Stackyard is reached directly on a mapped port, such as
http://server:8700. nginx forwarded a Host header with the port stripped while the browser's Origin kept it, so the two never matched and every write was refused as an origin mismatch. Only installs behind a reverse proxy on 443 were unaffected, which is why this survived 1.5.0. - German, Spanish, French, Persian and Chinese translate a further 34 strings that were left as English in their catalogues.
- Admin translates the Dock, Health and Badge pills, the Edit button, the Secret checkbox, the colour and poll-interval labels, the widget Name and Widget Type labels, and the editor's section title.
- The poll interval reads as one sentence in every language instead of wrapping the field in English words.
- App and widget names in the Settings list sit beside their icon in Persian instead of aligning to the far side of the row.
- The divider between the Settings navigation and the section beside it runs the full length of the section instead of stopping one screen down.
- The icon preview in the app editor no longer draws its artwork edge to edge.
- Colour swatches that wrap onto a second row line up under the row above instead of splitting to opposite edges.
If you are testing this
The origin fix is the one to exercise. Browse your instance directly on its mapped port, not through a reverse proxy, and save something in Settings. On 1.5.0 that fails with "Forbidden: origin mismatch".
For maintainers
- A Playwright suite now drives the admin UI against the built image, in Chromium and WebKit. It found the origin bug on its first working run.
- Those browser tests run on pull requests that touch the interface, on every merge, and as a gate on the release itself: a tag can no longer publish an image they reject.
- Backend coverage is measured and floored, the frontend path map is checked, and formatting is enforced.
- This is the first release mirrored to Docker Hub as well as ghcr.io.
Full changelog: v1.5.0...v1.5.1-rc.1