What's Changed

• fix: catch parent DeviceManagerError in print-path scan recovery (follow-up to #50) by @szrudi in #53
• fix: guard against 0 / unfriendly font-scale editing (#49) by @szrudi in #51
• fix: safe variable rename when backspacing the name to empty by @szrudi in #52

Full Changelog: v1.8.2...v1.8.3

What's Changed

• fix: self-heal stale libusb context in the print path (#48) by @szrudi in #50

Full Changelog: v1.8.1...v1.8.2

What's Changed

• fix: recover from stale libusb context in list_printers (v1.8.1) by @szrudi in #46

Full Changelog: v1.8.0...v1.8.1

What's Changed

• feat: key real printers by serial number, not the volatile USB id — closes #40 by @szrudi in #41
• feat: stable virtual printer ids — optional explicit id + safe slug — closes #42 by @szrudi in #43
• feat: default printer selection to a real printer instead of Auto-select by @szrudi in #44
• refactor: extract shared state_store; route usb_power through it by @szrudi in #45
• feat: persist per-printer label settings (tape size, colors) — closes #20 by @szrudi in #39

Full Changelog: v1.7.0...v1.8.0

Now part of labelle-org 🎉

labelle-web is now an official project under labelle-org, alongside the labelle library it builds on. Thanks @maresb for the invite — see labelle-org/labelle#139 for the backstory.

What this means for your install

If your compose.yaml still references ghcr.io/szrudi/labelle-web, update it to the new namespace:

services:
  labelle-web:
    image: ghcr.io/labelle-org/labelle-web:latest

Then docker compose pull && docker compose up -d will bring in this release and every future one.

If you don't update right away

Nothing breaks. The final szrudi-namespace image (ghcr.io/szrudi/labelle-web:1.6.6) keeps working indefinitely. Its footer shows a "we've moved" banner so you know when you're on the old track — but no new releases will land there.

What changed in the code

• The migration banner that v1.6.6 introduced is removed.
• Every szrudi/labelle-web reference in compose.yaml, README, and in-app links is updated to labelle-org/labelle-web.

Functionally identical to v1.6.6 minus the banner.

What's Changed

• chore(transfer): point repo references to labelle-org/labelle-web by @szrudi in #35

Full Changelog: v1.6.6...v1.7.0

This is the final release on ghcr.io/szrudi/labelle-web. The repo has moved to labelle-org/labelle-web — see v1.7.0 for migration instructions. The footer banner in this release is the in-app reminder.

What's Changed

• chore(footer): add labelle-org migration banner by @szrudi in #34

Full Changelog: v1.6.5...v1.6.6

What's Changed

• ci(pr-image): sweep predecessor image on each push by @szrudi in #32
• fix(server): handle missing uhubctl + missing DYMO without traceback spam by @szrudi in #36

Full Changelog: v1.6.4...v1.6.5

Batch mode now auto-previews row 1

When batch mode first activates — either by clicking "+ Add Variable" or by typing {{name}} directly into a widget — the first row's preview is now active by default. Typing values into row 1 updates the live preview immediately, with no need to click the eye icon first.

Existing flows are untouched: clicking the eye icon to deselect still works, and loading a label file with a pre-selected row still respects whatever selection the file contained.

What's Changed

• fix(batch): auto-select row 0 when batch mode first activates by @szrudi in #31

Full Changelog: v1.6.3...v1.6.4

Variable syntax changed: {{name}} instead of :name: ⚠️

A small but breaking tweak to the batch-print variable syntax introduced in 1.6.0. Placeholders now use double curly braces:

old: Hello :name:
new: Hello {{name}}

Why

Colons are common in legitimate QR / barcode content — URLs (http://), IPv6 literals, port numbers, key:value pairs, base64 padding — and the old :name: regex was greedy enough to false-match them. Switching to {{ }} brings labelle-web in line with Handlebars / Jinja / Mustache and drops the collision risk to near zero.

What to do

Re-save any label .json files that contain :varname: placeholders, replacing them with {{varname}}. If you don't, those placeholders will print literally instead of being substituted.

(If you haven't saved any label files yet — which is most users, since batch mode just shipped two days ago — no action needed.)

Anything else?

No behavioural changes. Auto-detection, the variable-rename heuristic, cut marks, copies, pause, cancel — all unchanged. Just the placeholder syntax.

What's Changed

• Switch batch-print variable syntax from :name: to {{name}} by @szrudi in #25

Full Changelog: v1.6.2...v1.6.3

Footer shows real build info

The footer at the bottom of the page now reads its version, commit, and branch from the running server's /api/health instead of from a Vite build-time constant. Practical effect:

• Production builds (released from main) show a clean v1.6.2 as before.
• Dev / PR / local builds show v1.6.2-dev (abc1234) so you can tell at a glance whether you're looking at a release or a preview.
• The "newer release available" prompt only fires on production builds — previously it could falsely flag feature-branch builds as out-of-date even when they were ahead.

Developer-facing: no more -dev suffix in package.json

Previously, working on a feature branch meant flipping 1.6.X-dev ↔ 1.6.X in package.json by hand at merge time. That's gone. package.json now always holds the version this commit would release if merged, and the -dev marker is added at display time when /api/health reports a branch that isn't main (if the health call fails, the footer omits -dev rather than mislabeling a build with no commit info). One less merge-time chore.

docs/ARCHITECTURE.md has a new short "Versioning convention" subsection that describes the new flow.

What's Changed

• feat: runtime version display + drop -dev suffix from package.json by @szrudi in #26

Full Changelog: v1.6.1...v1.6.2