maziggy 5 napja
szülő
commit
1b8c6efaab
2 módosított fájl, 12 hozzáadás és 2 törlés
  1. 11 1
      CHANGELOG.md
  2. 1 1
      backend/app/core/config.py

+ 11 - 1
CHANGELOG.md

@@ -2,7 +2,16 @@
 
 All notable changes to Bambuddy will be documented in this file.
 
-## [1.3.1] - Unreleased
+## [1.3.2] - Unreleased
+
+### Added
+
+### Changed
+
+### Fixed
+
+
+## [1.3.1] - 2026-11-11
 
 ### Added
 - **Bambu Lab H3C support (#3442, requested by @Mx772, contributed by @daltonclift in #3490)** — Bambuddy now supports the H3C: its nine-slot AMS 3H, the nine-PrintTool SwapTek rack and the per-PrintTool external inputs. The printer card lays out the AMS 3H like the unit, with a dryer box around the slots of its drying zone and the ambient readings in the header, shows the nine-position PrintTool rack, and names the external inputs **Ext-n**. Load and unload work from Bambuddy; an unload ends with pulling the filament back by hand, since the AMS 3H can't rewind, and the card says so. A load into a slot that reports no filament is refused. Drying targets the AMS 3H's drying zone, and chamber heating switches the airduct to heating mode first, because the H3C's chamber heater only heats in that mode. Queued prints are sent with the slot numbering Bambu Studio uses, and the slot numbering of every other printer is unchanged. A stopped print's filament usage is scaled by layers, since the H3C's progress includes its start sequence. The H3C gets its own firmware check, its 14 maintenance tasks with links to Bambu's guides (listed only when an H3C is added) and its fault texts. Queue jobs that a daily build stored for an H3C with the old slot numbers are corrected once on start. Tested on an H3C with firmware 01.01.03.00.
@@ -41,6 +50,7 @@ All notable changes to Bambuddy will be documented in this file.
 - **A camera window no longer opens a dozen streams to the printer at once (#3431, reported by @buffdriver)** — When the floating camera window was open while the page loaded (after a refresh, for example), Bambuddy opened about twenty camera streams for it. Only one was shown. The browser kept the rest open until the tab was closed, and they filled its six connections to the server. The page started each stream while still preparing to draw the window. It prepared the window several times before showing it, and every attempt left a stream behind. Streams now start only once the window is on the page. The camera page, the camera wall and the stream overlay start their streams the same way.
 - **A printer whose file service hangs during a print is no longer asked again and again until it refuses every upload (#3474, reported by @F9mm)** — When the card could not be read at print start, the timelapse baseline was read again every two minutes for the whole print, and each round walked the card twice: up to eight new FTPS connections, each hanging for 30 s against a hung printer. An H2S kept a session for every one of them, then answered every connection with "421 There are too many connections", and no queued job could reach it until the printer was restarted. The card is now read once per round. It is read again only while the print records a timelapse, the wait doubles after each failed round (up to 30 minutes), and it stops after five. A connection or listing that times out now pauses the background timelapse scans of that printer for five minutes. Opening files and sending prints are not held up by this. A printer that answers "421 too many connections" now gets its own message in the queue, saying it may need a restart, instead of "Bambuddy will retry automatically". Wiki updated.
 
+
 ## [1.3.0] - 2026-10-06
 
 ### Added

+ 1 - 1
backend/app/core/config.py

@@ -7,7 +7,7 @@ from pydantic import Field
 from pydantic_settings import BaseSettings
 
 # Application version - single source of truth
-APP_VERSION = "1.3.1"
+APP_VERSION = "1.3.2"
 GITHUB_REPO = "maziggy/bambuddy"
 BUG_REPORT_RELAY_URL = os.environ.get("BUG_REPORT_RELAY_URL", "https://bambuddy.cool/api/bug-report")