fix(readme): link release badges to the filtered release page#89
Merged
Conversation
Adding .gitkeep for PR creation (default mode). This file will be removed when the task is complete. Issue: #88
The C# Release and Rust Release shields.io badges in README.md displayed a per-language version (csharp-v*, rust-v*) but their Markdown link target pointed at the generic /releases page, which mixes C# and Rust releases. Clicking the C# v2.4.0 badge could land on a Rust release whenever Rust released last. Change the link target to the filtered releases page using the same language selector encoded in the GitHub release-title prefix: - C# badge: /releases?q=C%23&expanded=true - Rust badge: /releases?q=Rust&expanded=true This always lands on the latest release of the matching language with the release notes expanded inline, so the page agrees with the badge. Markdown cannot derive the target from the badge image (no JS), and GitHub's /releases/latest ignores any per-language filter, so a language-scoped target URL is required.
Force-include curl -I header dumps under docs/case-studies/issue-88/logs/ so the evidence referenced from the case-study README stays in the repo. .gitignore excludes Logs/ for build output, but case-study evidence is checked in alongside the analysis as in issue-86.
Member
Author
Working session summaryConfirmed: all three workflows are scoped to their language directories. A README-only change correctly skips them. The work is done. Summary:
This summary was automatically extracted from the AI working session output. |
Member
Author
🤖 Solution Draft LogThis log file contains the complete execution trace of the AI solution draft process. 💰 Cost: $2.822198📊 Context and tokens usage:Claude Opus 4.7:
Total: (76 new + 114.3K cache writes + 3.2M cache reads) input tokens, 19.0K output tokens, $2.810175 cost Claude Haiku 4.5:
Total: 9.4K input tokens, 524 output tokens, $0.012023 cost 🤖 Models used:
📎 Log file uploaded as Gist (1506KB)Now working session is ended, feel free to review and add any feedback on the solution draft. |
Member
Author
🎉 Auto-mergedThis pull request has been automatically merged by hive-mind.
Auto-merged by hive-mind with --auto-merge flag |
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
1 participant
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.
Summary
README.mddisplayed the per-language version but the badge link target was the generic/releasespage, mixing C# and Rust releases. Clicking theC# v2.4.0badge could land on a Rust release.C#for C# releases,Rustfor Rust releases, with&expanded=trueso the latest release card opens inline at the top.docs/case-studies/issue-88/capturing the issue, PR, release data, probe logs, template snapshots, and a full case-study analysis.Fixes #88
Root cause
In Markdown
[](target), the badge image and the link target are independent. The image was set up with shields.iofilter=csharp-v*so it shows the latest C# tag, but the link target was the unfiltered/releasesURL. Markdown cannot derive the target from the image (no JS), and GitHub's/releases/latestignoresfilter, so a language-scoped target URL is needed.The fix uses GitHub's
releases?q=<title-prefix>&expanded=truewhich displays only the language's releases with the latest one expanded at the top, agreeing with the badge image.Diff (README.md)
Template comparison
Per issue #88 requirements, the three referenced CI/CD templates were compared:
csharp-ai-driven-development-pipeline-template/README.md: no GitHub release version badge.js-ai-driven-development-pipeline-template/README.md: no header badges at all.rust-ai-driven-development-pipeline-template/README.md: no GitHub release version badge.None of the templates publish multiple languages from one repository, so they have no per-language
filterbadge and therefore no matching defect to report upstream. Detailed indocs/case-studies/issue-88/README.md.Case study
Full analysis with reconstructed timeline, requirement list, root cause, alternatives considered, and validation steps:
docs/case-studies/issue-88/README.mdEvidence (issue/PR/release JSON, probe headers, template snapshots) is preserved in:
docs/case-studies/issue-88/github-data/docs/case-studies/issue-88/logs/docs/case-studies/issue-88/templates/Test plan
curl -sI 'https://github.com/link-foundation/link-cli/releases?q=C%23&expanded=true'returns HTTP 200. Evidence:docs/case-studies/issue-88/logs/releases-q-csharp-headers.txt.curl -sI 'https://github.com/link-foundation/link-cli/releases?q=Rust&expanded=true'returns HTTP 200. Evidence:docs/case-studies/issue-88/logs/releases-q-rust-headers.txt.releases?q=C%23&expanded=trueshows onlyC# v2.4.0and excludes Rust releases.releases?q=Rust&expanded=trueshows onlyRust v0.1.0and excludes C# releases.mainand click each release badge to confirm landing on the expanded latest release of the matching language.