Skip to content

chore: prepare v0.2.4 release metadata#145

Merged
SSobol77 merged 1 commit into
mainfrom
chore/prepare-v0.2.4-release-metadata
Jul 11, 2026
Merged

chore: prepare v0.2.4 release metadata#145
SSobol77 merged 1 commit into
mainfrom
chore/prepare-v0.2.4-release-metadata

Conversation

@SSobol77

@SSobol77 SSobol77 commented Jul 11, 2026

Copy link
Copy Markdown
Owner

Summary

Prepare ECLI v0.2.4 release metadata without building, tagging, uploading, or publishing release artifacts.

Changes

  • bump authoritative project and packaging version surfaces from 0.2.3 to 0.2.4;
  • add complete v0.2.4 release notes;
  • reconstruct the missing v0.2.3 changelog section;
  • update README current-release presentation;
  • update current Windows and Command Plan version examples;
  • index the v0.2.4 release notes;
  • add documentation and packaging regression tests for release metadata, runtime version, authoritative version surfaces, and exact asset semantics.

Release identity

ECLI v0.2.4 — Extensions, Diagnostics, and Release Gate Hardening

The release metadata covers:

  • Extensions Layer foundation;
  • extension-backed TextMate rendering and language detection;
  • theme registry and migration;
  • F4 Diagnostics/Linter architecture;
  • OS/artifact-aware F4 provisioning contracts;
  • Linux official evidence drift validation;
  • source, built-artifact, and final release-asset gate separation;
  • fail-closed publication ordering;
  • exact 21 ECLI-owned GitHub Release asset contract.

Preserved boundaries

This PR does not:

  • create a release branch or tag;
  • build release artifacts;
  • create releases/0.2.4;
  • upload GitHub Release assets;
  • publish to PyPI;
  • modify release workflow logic;
  • modify publication conditions;
  • modify historical docs/release/v0.2.3.md;
  • claim completed clean-machine Debian 13 installer validation.

Validation

Passed:

  • uv run ruff check src tests scripts
  • uv run ruff format --check src tests scripts
  • uv run python scripts/check_runtime_imports.py
  • uv run pytest -q
  • make validate-version-consistency
  • make validate-gate2
  • uv run ecli --version
  • git diff --check

Results:

  • 2055 passed, 4 skipped
  • pyproject=0.2.4 ecli.__version__=0.2.4
  • ecli 0.2.4
  • PASS: exact 21 clean ECLI-owned asset names

The exact release asset contract remains:

  • 21 unique ECLI-owned uploaded assets;
  • no uploaded .sha256 sidecars;
  • no GitHub-generated source archives counted as ECLI-owned assets;
  • no numeric public asset prefixes.

Known release-cut follow-up

Three real TextMate performance/scroll tests were skipped because repository-local historical log fixtures are absent. This does not block the metadata PR, but equivalent real-file evidence must be supplied or explicitly validated before the v0.2.4 release cut.

Summary by CodeRabbit

  • New Features

    • Released ECLI version 0.2.4 with Extensions Foundation, syntax and theme integration, and F4 Diagnostics/Linter architecture.
    • Added OS- and artifact-aware provisioning evidence and expanded release validation guidance.
    • Added comprehensive v0.2.4 release notes, upgrade information, known limitations, and safety boundaries.
  • Documentation

    • Updated README, changelog, installation guidance, architecture documentation, and release indexes for v0.2.4.
  • Tests

    • Added automated checks for release metadata, documentation consistency, version reporting, and the expected release asset set.

@coderabbitai

coderabbitai Bot commented Jul 11, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

ECLI’s release metadata is updated from v0.2.3 to v0.2.4 across documentation, packaging sources, release notes, and automated consistency checks.

Changes

v0.2.4 Release Metadata

Layer / File(s) Summary
Release documentation and safety boundaries
CHANGELOG.md, README.md, docs/architecture/..., docs/install/..., docs/release/...
Adds v0.2.4 release content, architecture details, safety boundaries, validation instructions, and the exact 21-asset release rule.
Package version source updates
pyproject.toml, flake.nix, packaging/arch/PKGBUILD, packaging/nix/package.nix
Bumps authoritative package version values to 0.2.4.
Release metadata contract tests
tests/docs/test_v024_release_metadata.py, tests/packaging/test_release_metadata_v024.py
Adds checks for documentation identity, version consistency, CLI output, artifact naming, release asset semantics, and workflow paths.

Estimated code review effort: 3 (Moderate) | ~20 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely summarizes the main change: preparing v0.2.4 release metadata.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/prepare-v0.2.4-release-metadata

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.

@sonarqubecloud

Copy link
Copy Markdown

@coderabbitai coderabbitai 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.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/release/v0.2.4.md`:
- Line 8: Update the PyPI link in the v0.2.4 release notes to reference the
ecli-editor v0.2.4 page or the unversioned project page instead of version
0.0.1.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: ff52255f-5298-415c-ada3-2a5adf95dc33

📥 Commits

Reviewing files that changed from the base of the PR and between acdfc46 and 22fd201.

📒 Files selected for processing (12)
  • CHANGELOG.md
  • README.md
  • docs/architecture/command-plan-service.md
  • docs/install/windows.md
  • docs/release/README-release.md
  • docs/release/v0.2.4.md
  • flake.nix
  • packaging/arch/PKGBUILD
  • packaging/nix/package.nix
  • pyproject.toml
  • tests/docs/test_v024_release_metadata.py
  • tests/packaging/test_release_metadata_v024.py

Comment thread docs/release/v0.2.4.md
File: docs/release/v0.2.4.md
Website: https://www.ecli.io
Repository: https://github.com/SSobol77/ecli
PyPI: https://pypi.org/project/ecli-editor/0.0.1/

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Update the PyPI link to the v0.2.4 release.

The release notes currently link to ecli-editor/0.0.1/, which is misleading for v0.2.4. Use the v0.2.4 page or the unversioned project page.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/release/v0.2.4.md` at line 8, Update the PyPI link in the v0.2.4 release
notes to reference the ecli-editor v0.2.4 page or the unversioned project page
instead of version 0.0.1.

@SSobol77 SSobol77 merged commit 0f60a83 into main Jul 11, 2026
7 checks passed
@SSobol77 SSobol77 deleted the chore/prepare-v0.2.4-release-metadata branch July 11, 2026 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant