feat(registry): add ViperPkg v0.1.0 (subdir of julia-the-viper) - #18
Merged
Conversation
Surface gap from today's audit follow-up: ViperPkg (UUID d7e4f8a0-5c3b-4d9e-8f2a-1b3c4d5e6f7a) lives at julia-the-viper/viper-pkg/ and was missed by the first sweep because it's not under julia-libraries/. Registered using Julia's subdir parameter rather than splitting into a standalone repo. Tag viper-pkg-v0.1.0 added upstream pointing at HEAD; package tree-sha1 = 5a024e278f3cb89f86a225cc53db1a077450a0e2 (subtree of julia-the-viper @ 5deaf32). Deps: Downloads, HTTP (1.10), JSON3 (1.14), SHA, TOML, Tar. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
hyperpolymath
enabled auto-merge (squash)
May 27, 2026 18:43
hyperpolymath
disabled auto-merge
May 27, 2026 18:43
hyperpolymath
added a commit
that referenced
this pull request
May 27, 2026
) After today's wave (#16 EchoTypes + KRLAdapter, #18 ViperPkg, #20 EchoTypes v0.2.0) Registry.toml carries 37 packages, but README's table and the [Unreleased] CHANGELOG section both reflected the pre-wave 34-package snapshot. Catch up the human-facing listings: README.adoc: add EchoTypes, KRLAdapter, ViperPkg rows (alphabetical insertion; EchoTypes pinned at v0.2.0 per the registered head, the other two at v0.1.0). CHANGELOG.md [Unreleased]: Added — registry entries for the 3 packages Changed — the scorecard.yml regression fix from PR #19 Wiki line — actual page count (9 + _Sidebar) and missing Registering-a-Package + Security pages noted ISSUE_TEMPLATE list now matches what was actually added (package_registration replaces "custom") Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
Surfaces a gap from today's registry audit follow-up: ViperPkg lives at
julia-the-viper/viper-pkg/and was missed by #16 because it's not under thejulia-libraries/directory tree the first sweep walked.d7e4f8a0-5c3b-4d9e-8f2a-1b3c4d5e6f7a0.1.0https://github.com/hyperpolymath/julia-the-viper.gitviper-pkgviper-pkg-v0.1.0(added upstream pointing at HEAD =5deaf32)5a024e278f3cb89f86a225cc53db1a077450a0e2(subtree of viper-pkg)Registered using Julia's
subdirparameter rather than splitting into a standalone repo — the meta-repo carries non-package material (workspace docs, sibling tooling) and is the natural home.Test plan
subdir = "viper-pkg"set inPackage.toml(Julia ≥1.5 supports subdir packages).Registry.tomlupdated withd7e4f8a0…→V/ViperPkg.Pkg.add("ViperPkg")should pull just the subdir.🤖 Generated with Claude Code