Repository navigation
Release-assets policy: the collect set, every attachable type in the signature check, the pruned snapshot pre-release - #53
Merged
Conversation
…signature check, the pruned snapshot pre-release What the collect steps copy since 2026-10-12 (every module's pom + .pom.asc, jllama's AAR signatures, poms and sources/javadoc jars, the agent's thin jar), the signature check over *.jar, *.aar and *.pom, and the new rule that github-snapshot deletes every asset the run did not upload while versioned releases are never pruned -- with the measurements that found the gaps. Status line in crossrepostatus.md. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AytmJF9faEiQEVt6eetQS2
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.
Summary
Policy side of a cross-repo change in java-llama.cpp, BitcoinAddressFinder, srcmorph and streambuffer: the GitHub release assets were incomplete against Maven Central (no poms, jllama's
llama-platformabsent, its AARs unsigned although their.ascexisted) and thesnapshotpre-release accumulated (208 assets on jllama, SpotBugs plugin jars from 2026-05 on three repos).policies/fat-jar-release-assets.md:*.jar,*.aar,*.pom); the status paragraph says which jobs are byte-identical throughshared-files.sha256and why jllama's copies are not..pom.asc(maven-gpg writes both intotarget/, also for pom-only modules), jllama's AAR signatures, poms and sources/javadoc jars, the agent's thin jar -- with the measurement that found the gaps, and the check against Central'smaven-metadata.xml.snapshotpre-release holds exactly the current upload": the measured backlog, the four rules (keep-set = the uploaded directory, after the upload, every deletion printed, versioned releases never pruned), nothing deleted by hand.crossrepostatus.md: one status bullet next to "No release asset is attached that CI has not run".Test plan
snapshotpre-release holds exactly the current upload")Related issues / PRs
Checklist
🤖 Generated with Claude Code
https://claude.ai/code/session_01AytmJF9faEiQEVt6eetQS2
Generated by Claude Code