Skip to content

RepoRewind v0.2.0 — Your repository, one command away

Latest
Latest

Choose a tag to compare

View all tags
@OthmaneBlial OthmaneBlial released this 01 Sep 10:52
· 4 commits to main since this release
v0.2.0
4e29ad0

RepoRewind 0.2.0 — one-command private Git documentaries

RepoRewind 0.2.0 turns a local Git history into a private, evidence-backed documentary through one public command. The npm artifact, provenance statement, v0.2.0 source tag, GitHub Release, and live playground are released as one verified gate.

Run it in any local Git repository:

cd /path/to/your/repository
npx reporewind .

The command analyzes the checked-out first-parent history, starts a read-only server on a random 127.0.0.1 port behind an unpredictable session path, opens the browser, and loads the validated history automatically. Press Ctrl C to stop the session. Use --no-open on a remote shell.

What changed

  • The real application is available as a one-click guided fictional case.
  • reporewind [repository] is the primary local workflow; reporewind analyze remains the portable JSON workflow.
  • The npm tarball has no runtime dependencies, includes only reviewed distributable files, and passes exact-package smoke tests.
  • The README now starts with the public one-command path, the expected result, the local-first privacy contract, and a direct link to the real guided case without embedded media clutter.
  • Film export starts with Share Safety and can produce a story pack containing four poster/still PNGs, the trailer, GitHub-ready Markdown, a privacy report, and a checksum manifest.
  • Story Director proposes explainable Git-backed chapters that can be reordered, excluded, retitled, and rendered into the selected trailer/story pack.
  • The Insights desk exposes eight bounded archaeology views with explicit limits and links to supporting evidence.
  • A reproducible performance envelope covers 120, 1,000, and 5,000-commit histories through analyzer, browser, playback, and story-pack paths.
  • If WebGL cannot start, the same archive opens as a text-first evidence workspace with search, Insights, comparison, Story Director navigation, and poster export.

Migration

The archive schema remains at version 1. Generate a portable archive with:

npx reporewind analyze /path/to/repository \
  --output ./reporewind-history.json

No archive migration is required.

Supported versions and limits

  • Node.js 24 is recommended; Node.js 22.13 or newer is supported.
  • The exact public artifact is exercised on Linux, macOS, and Windows with Node.js 22 or 24 during the release gate.
  • The one-command session binds only to IPv4 loopback and does not fetch refs, LFS objects, or submodules.
  • Histories are limited to 256 MB, 250,000 commits, and 2,000,000 file-change entries. Use --max-commits earlier on ordinary laptops.

Rollback

The public v0.1.0 source release remains available as the previous stable release. The immutable v0.2.0 tag matches the npm artifact, provenance, live playground, README command, and displayed version.

Once an npm name/version is published it is immutable. If 0.2.0 must later be withdrawn, deprecate it with a specific recovery message, keep the GitHub release and checksums available for investigation, fix forward with 0.2.1, and move the latest dist-tag only after the replacement passes the complete release gate.

Verification gate

The following evidence agrees on 0.2.0:

The temporary npm token secret was removed from GitHub immediately after publication, and repository Actions was disabled again. The reusable credential remains only in the owner’s macOS Keychain.

Assets 2
Loading