Repository navigation
chore(registry): bump plugin pins after fleet hygiene merges - #112
Merged
Merged
Conversation
Advance the bar, copy-mode, search, git-panel, file-manager, and devtools gitlinks to the reviewed main commits their hygiene PRs produced. Refresh the git-panel, file-manager, and devtools manifest hashes because those PRs changed bitty-plugin.toml, and mirror the new user-facing descriptions for git-panel and file-manager. Regenerate the index; the official set stays at 11 entries.
Xuepoo
added
chore
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.
Priority: P2 | Area: registry | Labels: chore, P2, area:registry | Milestone: v0.1.0 | RFC: none | Task: fleet hygiene closeout
Summary
Advance every
plugins/<name>gitlink whose hygiene PR merged in this closeout, refresh themanifest_hashvalues for pinned manifests that changed, and regenerate the index. The official set stays at 11 entries.Pin changes
ed11fb344407e188a31f353d81de81d790453cee5dfc2e20607a4d7efdcf1be89195b3edc22b7ca0869d6aa91cfefe645a715988b60d1e1e2c61aea12d28ac709f38ed7977c1e7aba6c9bfc8f14afdc03ecc51f79682e96457f619d89fb5456a686ba387f3016ef2431ba08f042745501c198070ae52f2d2baf716252fadc6b14374866e9e689ac1b23deee354fc557fd5b24e70a426ff056f14457f57ffacf4e21e8bb7c778dc08191305f463b258ae824e8ccc92630b4400d395df1e79ba2b37cd820f49376691cd91add838268fad332978cc51421eb258d930eb3f5369ec6cda352090b912d8a3fbfda860308376Each new pin is the repository's current default-branch
HEAD(git ls-remote), so every gitlink points at a mainline commit.Manifest hashes
git-panel:3c54e6e9…→0ecd711c…file-manager:ad29971a…→56180148…devtools:d2174239…→babf1de7…bar,copy-mode, andsearchkept their hashes because their hygiene PRs did not touchbitty-plugin.toml. The git-panel and file-manager registry descriptions now mirror the new user-facing manifest text.Verification
just registry-generate→wrote generated/registry.json (11 plugin(s), 11 unverified).just registry-validate→ 0 errors, 36 warnings (pre-existing unsigned, resolver-grammar, and pin-reachability notices plus three stray local-directory notices).just registry-check→generated/registry.json is up to date (11 plugin(s)).just check→ pass (fmt-check, markdownlint, type-check, 161 tests, registry gates, app build).gitleaks detect --source .→ no leaks.Notes
git update-index --cacheinfo 160000,<sha>,<path>; no nested checkout was modified.dashboardandpaletteare intentionally untouched: neither repository had a merged hygiene PR in this closeout.