Skip to content

Distribution: Glama is still on 0.1.13 - #13

Merged
Karzone merged 1 commit into
mainfrom
claude/beautiful-archimedes-dbzisv
Oct 11, 2026
Merged

Karzone merged 1 commit into
mainfrom
claude/beautiful-archimedes-dbzisv

Conversation

@Karzone

@Karzone Karzone commented Oct 11, 2026

Copy link
Copy Markdown
Owner

Summary

Corrects the Glama row in docs/DISTRIBUTION.md. #7 said the auto-build triggered by the v0.1.14 release reported 0.1.14, and that was wrong.

On 2026-10-11, Glama's Releases tab shows:

  • 0.1.13 as Latest, published 2026-10-05 02:58;
  • 0.1.12, published 2026-09-28, which is six days before the GitHub v0.1.12 release;
  • nothing for 0.1.14 or 0.1.15.

So Glama releases don't follow GitHub releases one for one. The row now says a Glama release for 0.1.15 is still owed.

Related issue

None.

Type of change

  • Bug fix
  • New feature / analyzer
  • Documentation
  • Build / CI / tooling
  • Other

Checklist

  • dotnet build passes (docs only)
  • dotnet test passes (docs only)
  • Added or updated tests for the change
  • Updated docs / README if behavior or usage changed
  • Change keeps TestAtlas zero-config, offline, and deterministic

Notes for reviewers

One line changed, in the Glama row only. The row's older note, that Glama "Auto-Release is on: every GitHub release triggers a Glama build", is left as it was. These dates contradict it, but I haven't seen Glama's own setting.

🤖 Generated with Claude Code

https://claude.ai/code/session_013F6VMUcDtZmJX3ZibLuzXg


Generated by Claude Code

Its Releases tab shows 0.1.13 as Latest and nothing for 0.1.14 or 0.1.15,
so the row's claim that the 0.1.14 auto-build reported 0.1.14 was wrong.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013F6VMUcDtZmJX3ZibLuzXg
@Karzone
Karzone merged commit 7f8026f into main Oct 11, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants