Skip to content
rlsbl.checks.release
Updated
On this page

The checks that read outside the working tree: the remote's refs, the branch, the CI publish credentials, and the follow-ups a conversion still owes.

#rlsbl.checks.release

#rlsbl.checks.release

Release checks (tag: release): the refs and the Releases hanging off them, the branch, the CI credentials, and the follow-ups a recorded conversion still owes the outside world.

Checks: unpublished-refs, branch-sync, ci-publish-secrets, old-repo-archived, go-deprecation-published.

Every check in this module reads something OUTSIDE the working tree -- the remote's refs, the GitHub API, the Go module proxy -- which is why they carry the release tag rather than project: the offline tags (project, changelog, quality, prepush) stay answerable with no network, and a networked check placed in one of them would make an offline run fail for a reason that has nothing to do with the repository.

All of them are fail-closed. A probe that cannot answer is a hard error, never a pass: "we could not ask" is not evidence that a ref is pushed, a secret exists, a repository is archived, or a module is deprecated.

#register_release_checks

python
def register_release_checks(app)

Register release-tag checks on app.

#_transition_record_paths

python
def _transition_record_paths(ctx)

Every transition record this project can reach, newest home first.

The three homes :func:rlsbl.transition_record.get_transition_record_path resolves: a standalone project's own record, the workspace-scoped record, and one per releasable. A monorepo carries facts in all three, and a conversion follow-up is owed whichever record recorded it.

#_read_transition_record

python
def _read_transition_record(ctx, reporter)

(events, error_outcome) -- the events, or a finalized failure.

A malformed record is this check's finding, not a traceback: reading a record FOR USE is where :func:rlsbl.transition_record.read_events raises, and a check that consumes one has to report it.

#_followup_outcome

python
def _followup_outcome(verdict, reporter, *, passed)

Report a :class:rlsbl.transition_record_followup.FollowupVerdict.

#register_networked_release_checks

python
def register_networked_release_checks(app)

Register the probing release-tag checks on app.

#_same_commit

python
def _same_commit(a, b)

Do two git object names denote the same commit, allowing abbreviation?

A release commit may be recorded abbreviated (the schema accepts 7 to 40 hex characters) while a resolved ref is always full, so the comparison is by common prefix -- the same rule the release record applies.

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