mirror of
https://github.com/Glitchy-Sheep/boosty-downloader.git
synced 2026-10-14 21:33:23 +00:00
[PR #123] [MERGED] chore: release v3.1.0 #128
Labels
No labels
api-drift
bug
ci
documentation
enhancement
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Glitchy-Sheep/boosty-downloader#128
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/Glitchy-Sheep/boosty-downloader/pull/123
Author: @Glitchy-Sheep
Created: 8/9/2026
Status: ✅ Merged
Merged: 8/9/2026
Merged by: @Glitchy-Sheep
Base:
main← Head:release/v3.1.0📝 Commits (5)
86636f1chore: 🔨 Move from Makefile to Taskfilea16d9a0feat: 🚀 Release wizard with preflight checks and PR flow617909bMerge remote-tracking branch 'origin/main' into release/v3.1.04dcb16cchore: release v3.1.077c1499refactor: 💄 Wizard output: command ladder and compact release notes📊 Changes
22 files changed (+1043 additions, -300 deletions)
View changed files
📝
.env.example(+0 -0)📝
.github/actions/setup/action.yml(+3 -0)📝
.github/workflows/ci.yaml(+10 -11)📝
.github/workflows/release.yaml(+10 -13)📝
CHANGELOG.md(+14 -4)➖
Makefile(+0 -129)➕
Taskfile.yml(+183 -0)📝
docs/development/01-dev-tools.md(+22 -15)📝
docs/development/02-testing.md(+8 -6)📝
docs/development/03-ci.md(+7 -7)📝
docs/development/04-releasing.md(+27 -36)📝
pyproject.toml(+1 -1)📝
pyrightconfig.json(+5 -1)➕
scripts/_integration_env.py(+81 -0)➕
scripts/api_preflight.py(+21 -0)📝
scripts/build_install.py(+17 -16)➕
scripts/posts_example.py(+20 -0)📝
scripts/release.py(+406 -56)📝
test/integration/analysis/get_author_posts_test.py(+8 -0)📝
test/integration/configuration.py(+4 -3)...and 2 more files
📄 Description
Promotes the Unreleased changelog into v3.1.0 and bumps the version.
Release notes
Added
Fixed
Security
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.