chore: prepare 0.4.0 release - #30
Conversation
Reviewer's GuideThis 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
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 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. Comment |
There was a problem hiding this comment.
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.
| [project] | ||
| name = "blazeserve" | ||
| version = "0.3.1" | ||
| version = "0.4.0" |
There was a problem hiding this comment.
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.
What changed / why
AI assistance disclosure
ai-assistedlabel should be applied.Evidence and tests
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:
Bug Fixes:
Build:
Documentation: