Skip to content
rlsbl.commands.release.rollback
Updated
On this page

Rollback helpers for cleaning up after a failed release: deleting tags, reverting version bump commits, and removing GitHub Releases.

#rlsbl.commands.release.rollback

#rlsbl.commands.release.rollback

Rollback helpers for cleaning up after a failed release: deleting tags, reverting version bump commits, and removing GitHub Releases.

#_is_tracked

python
def _is_tracked(project_dir: str, path: str) -> bool

Return True if path is tracked in git at the current HEAD/index.

Uses git ls-files --error-unmatch which exits non-zero for paths that are not tracked. Any failure (untracked path, not a git repo, git unavailable) is treated as "not tracked" so cleanup falls through to its normal orphan-removal behavior.

#_cleanup_release_artifacts

python
def _cleanup_release_artifacts(project_dir: str, version: str, *, changes_dir: str | None=None, releases_dir: str | None=None) -> None

Best-effort removal of generated files that become orphaned after rollback.

After git reset --hard reverts the release-created commits, files created during finalization (renamed JSONL, per-version markdown, renamed release TOML) are left as untracked because they never existed in the pre-release history. Removing them prevents a dirty working tree that blocks the next attempt.

Tracked-file guard: a candidate that is TRACKED in git at the post-reset HEAD is left alone. This is the re-release case -- an earlier partial attempt committed finalize files (e.g. {version}.jsonl); after git reset --hard restores them as tracked files, deleting them would leave D (deleted-from-index) entries that dirty the tree and block a retry with --no-allow-dirty. Only genuinely orphaned (untracked) artifacts are removed.

changes_dir overrides the default per-project .rlsbl/changes/ location -- in explicit releasable mode the finalized JSONL and its per-version .md live in the releasable's changes dir. releases_dir overrides the default per-project .rlsbl/releases/ location the same way -- in explicit releasable mode the release-file finalization archives v{version}.toml/.md under the releasable's own releases dir.

More tools from this site

  • claudestream Drive Claude Code from Python: run it as a subprocess and read its output as typed events, with async and sync sessions, sandbox policies, and tools you define in Python
  • claudewheel A TUI Claude Code Launcher that lets you have more than one profile, manage sessions lifecycle, pick the exact CC version, model to use (even older unlisted ones), pick which GitHub account to use, etc.
  • dirstat Fast, single-binary directory statistics CLI: every file under a tree grouped by format, with counts, sizes, and lines of code, as a colored terminal table or as JSON
  • fastware A batteries-included ASGI framework: msgspec JSON, a managed Granian server, dependency injection, SSE, WebSockets, auth, and a test client
  • go-toml-edit Zero-dep TOML editing library for Go with comment preservation
  • howmuchleft The fastest Claude Code statusline: context window, 5-hour, and weekly limit usage as three customizable gradient bars, rendering in about 6 ms
  • orxtra
  • pgdesign
  • predraw Declarative rendering pipeline: describe a scene in JSON and get SVG, PNG and WebP out, with light and dark style tokens, reusable components and text converted to path outlines
  • reposummary Turn a git repository's history into a Markdown journal: pick a time window or revision range and get a readable digest of what changed, optionally narrated by an LLM
  • safegit git wrapper CLI that gives each commit its own temporary index and retries ref updates on conflict, so concurrent agents share one repository
  • saferm Command-line replacement for rm that archives every deletion with a mandatory reason and the context it ran in, so deleted files can be listed, inspected and restored
  • selfdoc Static Site Generator that builds a project's documentation site directly from its source code, so the docs can never drift from the code they describe, with SEO/AEO, first-class blog, search, and cross-project linking built in
  • strictcli
  • stricttest An always-on test-isolation floor: a pytest plugin and a Go env-hygiene module that make a test suite structurally unable to reach real credentials, the real HOME, the network, or the development repository.
  • wesktop A Python framework that turns an ASGI web app into a desktop application, serving it from a local Granian server and displaying it in a native OS window via pywebview
Search