[AAASM-2962] 🐛 (profile): Fix broken version badges on non-versioned repo rows#18
Merged
Merged
Conversation
Contributor
Author
Claude Code review — AAASM-2962 (org profile version badges)CI stateNo PR checks run on Scope vs. acceptance criteria
Verified: the release-pointer query resolves to Minor aside (not this PR): agent-assembly's GitHub "Latest" flag still points at VerdictReady for approval and merge. No CI to fix; every version indicator on the org page is now truthful. — Claude Code |
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Fixes the broken/empty version badges in the org landing-page repo table (
profile/README.md). Four rows usedgithub/v/tag/<repo>, but those repos have zero tags/releases, so the badges rendered empty.Per AAASM-2962, these repos aren't versioned artifacts, so the badge is fixed to match each repo's nature (rather than adding meaningless git tags):
github/v/release/agent-assembly?include_prereleases&sort=semver(labelformula), linking the formula. Shows the core release the tap installs (v0.0.1-beta.1).tracks) — the product version the docs document.—); it's org config, not a versioned artifact.status: reservedbadge (the spec lives in the monorepo per project policy; this repo is reserved).Related ticket
Closes AAASM-2962
How to verify
Open the org page (https://github.com/ai-agent-assembly) — the tap + docs rows show
v0.0.1-beta.1;.githubshows—; spec showsreserved. No empty/"no tag" badges remain.Checklist
[AAASM-XXXX] <GitEmoji> (<scope>): <summary>