Skip to content

feat: list crew-companion from its own repository - #91

Merged
KiroCrewCaptain merged 1 commit into
mainfrom
feat/pin-crew-companion
Nov 18, 2026
Merged

KiroCrewCaptain merged 1 commit into
mainfrom
feat/pin-crew-companion

Conversation

@bolichen97

Copy link
Copy Markdown
Collaborator

What

Flips crew-companion in catalog/official-registry.json from a builtin source to a git source in its own KiroCrewCaptain repository, pinned at the commit Kiro Crew's adoption pin table names for it in kirodotdev/KiroCrew#39004:

App Repository ref Version
crew-companion https://github.com/KiroCrewCaptain/kirocrew-app-crew-companion 2eb2e98469149ea740d7f82b6df701dbf872c9a3 1.0.1

The row gets the same note the other adopted apps carry, naming Kiro Crew 0.14.0, and its Kiro Crew org author gains the https://github.com/KiroCrewCaptain URL. No other row changes.

The commit is the head of the repository's main, with green CI on ubuntu, macOS and Windows plus the reproducible-bundle, README and internal-content jobs. Its manifest declares the same permissions as the built-in it replaces, and a desktop block with the four windows the built-in's desktop shell code drew (the avatar on every display, a background notification window, the panel and the gallery), which the desktop app's window host serves (App Kit level 7).

Merge condition: right after the Kiro Crew pin PR

The Kiro Crew PR is kirodotdev/KiroCrew#39004. It adds the pin row and moves the wheel version. This PR is not set to auto-merge: the driver merges it once kirodotdev/KiroCrew#39004 has landed.

  • This PR merged first: no Kiro Crew build pins crew-companion yet, so a host that has the built-in is not moved, and the catalog entry and that host's install disagree until the pin lands.
  • The Kiro Crew PR merged first: a nightly host adopts at this commit while the published catalog still lists crew-companion as builtin, which gives an adopted record no install source for an update or a reinstall until this one lands.

Verification

  • tools/format.py: already normalized.
  • tools/validate.py: OK. The 3 warnings were already there, on other apps.
  • pytest tests/: 522 passed (with the jsonschema[format] validators installed, so the date-time and uri checks are active).
  • Kiro Crew's scripts/adoption_pin.py compute at this commit with --min-sdk-level 7 prints the pin PR's row byte for byte, and on the pin PR's tree every row, this one included, measures ok over the network.
  • The pin PR's upgrade smoke ran update and reinstall of the adopted app against the published catalog with only this row changed: both reached the pinned commit and kept the app's reminders, settings and avatars.

Switch crew-companion from a builtin source to a git source in
KiroCrewCaptain/kirocrew-app-crew-companion at the commit Kiro Crew's
adoption pin table names for it (kirodotdev/KiroCrew#39004). Lands
right after that pin PR.
@github-actions

Copy link
Copy Markdown

GPT 5.6 Review — ✅ no blocking findings

GPT 5.6 completed its review of 99ad5970b6ab964a6e5de5cb645dee9b35c000f9 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 99ad597

@github-actions

Copy link
Copy Markdown

App Readiness Review — ✅ no blocking findings

Every app repository this PR adds or re-pins passed the blocking readiness rules at 99ad5970b6ab964a6e5de5cb645dee9b35c000f9.

Rules: review/app-readiness-rules.md (base-branch snapshot). This comment is updated in place on each push.

Review details

No findings.

crew-companion @ 2eb2e98469149ea740d7f82b6df701dbf872c9a3

No findings.

[APP-READINESS-REVIEWED] 99ad597

@github-actions

Copy link
Copy Markdown

Opus 5 Review — ✅ no blocking findings

Opus 5 completed its review of 99ad5970b6ab964a6e5de5cb645dee9b35c000f9 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 99ad597

@KiroCrewCaptain
KiroCrewCaptain merged commit 3b8c847 into main Nov 18, 2026
7 checks passed
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.

2 participants