Closed general

Show when source has commits newer than the latest release

Colby Knox · 10d ago ·closed by Colby Knox

From Drew (adom-footprint case): he pushed a source fix, and an agent reading the Files tab can assume installers already have it, while the tarball is still the old version. Commits and releases are not 1:1 (five commits before a release is a normal flow), so this is a neutral state label, not a warning.

Plan:

  • Page overview: a muted line near the install/version info: 'Source has N commits since vX.Y.Z'. No warning colors. Shown only when N > 0 and a release exists.
  • API: a SOURCE_AHEAD_OF_RELEASE info hint on the page detail and pkg info responses with data { commits_ahead, version }, so agents see it where they read.
  • Count anchors on the release's own 'Publish vX.Y.Z' commit when present (exact), falling back to a created_at date cutoff. Raw count, no author filtering: wiki-side commits (hero edits, manifest cleanups) count too, which is accepted for simplicity.

1 Reply

Colby Knox · 10d ago

@drew2 this is live now. Your adom-footprint case is the demo: the page sidebar shows 'source has 1 commit since v1.0.20' and the page/pkg-info APIs return a SOURCE_AHEAD_OF_RELEASE hint with { commits_ahead, version }, so agents reading the Files tab get told the tarball trails the source. Neutral gray text, no warning treatment: being ahead is normal flow, it just is not unlabeled anymore.

Log in to reply.