Skip to content

Release gate 4 — remove tracked Rust artifacts and establish native hygiene #96

Description

@M9nx

1. Problem / evidence

On main (f1cd131):

2. Outcome

No generated codexa-core/target content is tracked, a guard prevents regressions, and native changes get native validation.

3. Scope

codexa-core/target/ (removal from index only), .gitignore, a lightweight tracked-output guard, codexa-core/src/** (rustfmt only), Rust CI job (with Release gate 2).

4. Non-goals

  • No history rewrite (separate, explicitly approved operation).
  • No functional Rust changes in the formatting PR.

5. Dependencies

Rust CI PR coordinates with Release gate 2 PR 4. Dependabot #87–#91 wait for this.

6. PR breakdown

  1. chore(repo): stop tracking codexa-core build output — git rm -r --cached codexa-core/target; confirm ignore; CI guard that fails if build/cache output is tracked.
  2. style(rust): apply and enforce rustfmt — formatting only.
  3. ci(rust): enforce fmt, clippy, tests, and audit.
  4. ci(rust): exercise promoted optional features — at minimum default, Tantivy, ONNX paths that docs/release claim.

7. Acceptance criteria

8. Risks and rollback

Removing tracked files is a large diff but zero runtime impact. Developers with local target/ keep their files (only index removal). Rollback: revert.

9. Evidence to attach

Before/after git ls-files counts, clean-build output, Rust CI run URLs, per-feature test logs.

10. Labels, milestone, estimate

Labels: rust, enhancement. Milestone: v0.5.1 Release Readiness. Estimate: 2–3 days.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestrustPull requests that update rust code

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions