[PR #145] [MERGED] chore: release v3.4.0 #148

Closed
opened 2026-10-13 19:48:00 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/Glitchy-Sheep/boosty-downloader/pull/145
Author: @Glitchy-Sheep
Created: 8/15/2026
Status: ✅ Merged
Merged: 8/15/2026
Merged by: @Glitchy-Sheep

Base: main ← Head: release/v3.4.0


📝 Commits (1)

📊 Changes

3 files changed (+11 additions, -3 deletions)

View changed files

📝 CHANGELOG.md (+2 -0)
📝 pyproject.toml (+1 -1)
📝 uv.lock (+8 -2)

📄 Description

Promotes the Unreleased changelog into v3.4.0 and bumps the version.

Release notes

Added

  • Debug log now tells what happened to every request, not only that it started: outcome lines with status and timing (-> 200 in 0.31s) or the error chain (-> FAIL ClientConnectorError <- ConnectionResetError in 12.1s), dns/connect phase timings, retry attempt numbers (attempt 2/5), and a live connecting... line - a hang or a killed handshake is readable straight from the log

Fixed

  • Long post titles no longer crash the download with "File name too long" (#93, #88): folder and file names are cut to fit the filesystem limit, and the post date, the dedup id and the file extension always survive the cut
  • If the full path is still too long for the OS (a deep destination folder on Windows), the error now says what to do: move the destination folder closer to the drive root
  • Titles with dots keep them: a post named "v2.0" no longer turns into "v20"

Changed

  • Single-post downloads (--post-url) now name the folder the same way as the full run: date - title (id) - the id tail keeps same-titled posts apart
  • Debug log now keeps query keys in logged URLs (?sig=...&expire=... instead of cutting the query off) - easier to match a failing request to an endpoint, values stay hidden
  • Already downloaded posts are untouched: folders are never renamed, a new-style name appears only when an updated post is re-downloaded

After merge

Run task release:tag - it verifies fresh main and pushes the tag; the tag triggers the release workflow (build -> PyPI -> GitHub Release).


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Glitchy-Sheep/boosty-downloader/pull/145 **Author:** [@Glitchy-Sheep](https://github.com/Glitchy-Sheep) **Created:** 8/15/2026 **Status:** ✅ Merged **Merged:** 8/15/2026 **Merged by:** [@Glitchy-Sheep](https://github.com/Glitchy-Sheep) **Base:** `main` ← **Head:** `release/v3.4.0` --- ### 📝 Commits (1) - [`9b72c77`](https://github.com/Glitchy-Sheep/boosty-downloader/commit/9b72c77513497cb62e404255b9166c345e0343cb) chore: release v3.4.0 ### 📊 Changes **3 files changed** (+11 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `CHANGELOG.md` (+2 -0) 📝 `pyproject.toml` (+1 -1) 📝 `uv.lock` (+8 -2) </details> ### 📄 Description Promotes the Unreleased changelog into v3.4.0 and bumps the version. ## Release notes ### Added - Debug log now tells what happened to every request, not only that it started: outcome lines with status and timing (`-> 200 in 0.31s`) or the error chain (`-> FAIL ClientConnectorError <- ConnectionResetError in 12.1s`), dns/connect phase timings, retry attempt numbers (`attempt 2/5`), and a live `connecting...` line - a hang or a killed handshake is readable straight from the log ### Fixed - Long post titles no longer crash the download with "File name too long" (#93, #88): folder and file names are cut to fit the filesystem limit, and the post date, the dedup id and the file extension always survive the cut - If the full path is still too long for the OS (a deep destination folder on Windows), the error now says what to do: move the destination folder closer to the drive root - Titles with dots keep them: a post named "v2.0" no longer turns into "v20" ### Changed - Single-post downloads (`--post-url`) now name the folder the same way as the full run: `date - title (id)` - the id tail keeps same-titled posts apart - Debug log now keeps query keys in logged URLs (`?sig=...&expire=...` instead of cutting the query off) - easier to match a failing request to an endpoint, values stay hidden - Already downloaded posts are untouched: folders are never renamed, a new-style name appears only when an updated post is re-downloaded ## After merge Run `task release:tag` - it verifies fresh main and pushes the tag; the tag triggers the release workflow (build -> PyPI -> GitHub Release). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-13 19:48:00 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Glitchy-Sheep/boosty-downloader#148
No description provided.