Skip to content

chore: prepare 0.4.0 release - #30

Merged
whoisjayd merged 1 commit into
mainfrom
release/v0.4.0
Sep 11, 2026
Merged

whoisjayd merged 1 commit into
mainfrom
release/v0.4.0

Conversation

@whoisjayd

@whoisjayd whoisjayd commented Sep 11, 2026 •

Copy link
Copy Markdown
Owner

What changed / why

  • Change: Bump release version to 0.4.0 across all synchronized locations: pyproject.toml, package version, UI template, k8s deployment manifest, tests, and changelog.
  • Why: Delivers the 0.4.0 minor release containing machine-readable CLI outputs, local contributor smoke environment, live IPv6 testing, offline deployment validation, compatibility policy, and CodeQL security hardening.

AI assistance disclosure

  • AI assistance was used and disclosed; the ai-assisted label should be applied.
  • Tools and use: Automated release synchronization according to Section 16 of AGENTS.md.
  • Accountable human: Jaydeep Solanki (@whoisjayd).

Evidence and tests

  • Full quality gates and test suite passed locally with 88.37% coverage.
  • Python package distribution built and twine check passed.

Summary by Sourcery

Prepare the 0.4.0 release with synchronized version metadata and the documented feature, testing, and security improvements included in the release.

New Features:

  • Add machine-readable JSON output modes for diagnostic and benchmark CLI commands.
  • Add contributor smoke testing, live IPv6 integration coverage, offline deployment validation, compatibility guidance, and expanded protocol integration tests.

Bug Fixes:

  • Harden path traversal protections for upload and ZIP endpoints.
  • Prevent HTTP response splitting through attachment filename sanitization.

Build:

  • Bump the project and synchronized release artifacts to version 0.4.0.

Documentation:

  • Publish the 0.4.0 changelog and normative compatibility policy.

@whoisjayd whoisjayd added the ai-assisted Disclosed AI assistance; requires careful accountable human review label Sep 11, 2026
@sourcery-ai

sourcery-ai Bot commented Sep 11, 2026 •

Copy link
Copy Markdown

Reviewer's Guide

This release-preparation PR synchronizes all tracked version references to 0.4.0, updates the deployment image and version tests, and adds the 0.4.0 changelog entry summarizing the shipped CLI, testing, deployment, compatibility, protocol, and security improvements. Reviewers should verify that no version-bearing locations remain stale and that the lockfile, package metadata, runtime endpoint, UI, and Kubernetes tag agree.

File-Level Changes

Change Details Files
Synchronize the project version to 0.4.0 across packaging, runtime metadata, user-facing UI, deployment configuration, and version assertions.
  • Update the package metadata and lockfile release version.
  • Update the exported runtime version and operational endpoint expectations.
  • Update the UI display and Kubernetes image tag.
  • Record the 0.4.0 changelog entry and release date.
pyproject.toml
uv.lock
blazeserve/__init__.py
blazeserve/ui.py
deploy/k8s/deployment.yaml
tests/integration/test_operational_endpoints.py
tests/unit/test_version.py
CHANGELOG.md
Document the functionality and security improvements included in the 0.4.0 release.
  • Summarize machine-readable CLI output, contributor smoke testing, IPv6 coverage, offline deployment validation, compatibility policy, and protocol tests.
  • Document path traversal barriers and response-splitting sanitization.
CHANGELOG.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented Sep 11, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 5ceb58db-8b3a-4052-859b-a32245e6e1ed


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've found 1 issue

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="pyproject.toml" line_range="7" />
<code_context>
 [project]
 name = "blazeserve"
-version = "0.3.1"
+version = "0.4.0"
 description = "⚡ Ultra-fast HTTP file server with advanced performance optimizations, real-time metrics, and production-ready architecture — supports byte-range/multi-range downloads, TLS, Basic Auth, throttling, uploads, streaming ZIP, CORS, and a polished CLI."
 readme = { file = "README.md", content-type = "text/markdown" }
</code_context>
<issue_to_address>
**nitpick:** The 0.4.0 release is not listed as supported in SECURITY.md; its supported-version table still marks only 0.3.x, so users of the current release are incorrectly told that their version is unsupported.

**Triggers:** When users consult the security policy after upgrading to 0.4.0.

**Suggested fix:** Update SECURITY.md to include 0.4.x as the supported release range and adjust the older-version entry accordingly.
</issue_to_address>

Sourcery assessment

Needs a human reviewer. The Kubernetes manifest now deploys the v0.4.0 container image; if that tag is missing or faulty, a rollout could fail to start pods or cause an outage. Reverting restores the previous image reference, but any outage during the rollout has already occurred.


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

Comment thread pyproject.toml
[project]
name = "blazeserve"
version = "0.3.1"
version = "0.4.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nitpick: The 0.4.0 release is not listed as supported in SECURITY.md; its supported-version table still marks only 0.3.x, so users of the current release are incorrectly told that their version is unsupported.

Triggers: When users consult the security policy after upgrading to 0.4.0.

Suggested fix: Update SECURITY.md to include 0.4.x as the supported release range and adjust the older-version entry accordingly.

@whoisjayd
whoisjayd merged commit 5a78026 into main Sep 11, 2026
22 checks passed
@whoisjayd
whoisjayd deleted the release/v0.4.0 branch September 11, 2026 08:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ai-assisted Disclosed AI assistance; requires careful accountable human review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant