Skip to content

chore: shorten a package keyword rejected by the registry - #137

Merged
bal7hazar merged 1 commit into
mainfrom
chore/registry-keywords
Sep 27, 2026
Merged

bal7hazar merged 1 commit into
mainfrom
chore/registry-keywords

Conversation

@bal7hazar

Copy link
Copy Markdown
Collaborator

origami_security, origami_rating, origami_random and origami_defi 1.8.0 are published on scarbs.xyz. The registry refused origami_map and origami_hexmap with a non-JSON response. Both carry the 21-character keyword procedural-generation; the accepted crates have keywords of at most 13 characters. This replaces it by generation.

No source change.

🤖 Generated with Claude Code

The scarbs.xyz registry refused origami_map and origami_hexmap 1.8.0; both carry the
21-character keyword "procedural-generation", the four accepted crates have keywords of at
most 13 characters.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@bal7hazar
bal7hazar merged commit 04ab30c into main Sep 27, 2026
10 checks passed
@bal7hazar
bal7hazar deleted the chore/registry-keywords branch September 27, 2026 22:16
bal7hazar added a commit to bal7hazar/nalgebra-cairo that referenced this pull request Oct 1, 2026
…es a release at a later commit that leaves the published packages untouched (#89)

The 0.1.1 publication stopped after 12 of 54 packages: scarbs.xyz refused nalgebra_linalg_spectral2 (keyword "symmetric-tridiagonal", 21 characters; same refusal as dojoengine/origami#137). Option A of the project manager:
- keywords, the only manifest field changed, in the 7 unpublished packages over the limits (linalg_spectral2..6, linalg3, linalg4): every package now has at most 8 keywords of at most 20 characters;
- scripts/release.py continues a release begun at an older commit only when that commit is an ancestor of HEAD, every package recorded as published is still published, and `git diff --name-only --no-renames` touches none of their files (directories, readme / license-file, inherited ones included) nor Scarb.toml, Scarb.lock, .gitignore, .scarbignore; the check is printed; self-test cases.

Dry run on the branch: "continuing the release begun at 3e5e4ba: ... lists 8 file(s); checked against the 12 package(s) already published and Scarb.toml, Scarb.lock, .gitignore, .scarbignore: none of them is touched".

Review (Codex unavailable, quota; the owner's fallback on Claude, on Fable since the work is Opus 5.5's): slingfall/review-9-rel-fix PASS WITH FINDINGS on 028f065 (2 minor, 3 notes on the continuation check), all fixed in ba3dbe2; slingfall/review-9-rel-fix-2 (claude-fable-5-1) PASS WITH FINDINGS on ba3dbe2, notes only (follow-ups: ignore files in intermediate directories, a lagging index for the in-flight package, release.py --self-test in CI). CI 78 / 78 green on ba3dbe2.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

1 participant