Release dev.kit 0.13.0#27
Merged
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR releases dev.kit 0.13.0 and updates repo-contract detection so that repo-owned manifests can satisfy the config contract when they explicitly opt in via contract: config or contracts: [config] (rather than relying on filename-only heuristics like deploy.yml).
Changes:
- Add manifest-metadata detection for config contract coverage and surface it as factor evidence.
- Harden the test suite to assert it is using the checkout-local
dev.kitshim/version, and add regression assertions for the new config-manifest behavior. - Bump versioned artifacts and docs to 0.13.0 (package metadata, generated context, references, changelog).
Reviewed changes
Copilot reviewed 9 out of 10 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
lib/modules/repo_factors.sh |
Adds config-contract opt-in detection via manifest metadata and includes it in factor status + evidence. |
tests/suite.sh |
Ensures tests run against the checkout-local dev.kit; adds assertions for new evidence and for filename-only deploy configs not satisfying config contract. |
tests/fixtures/docker-repo/deploy.yml |
Updates fixture to opt into config contract via contracts: - config. |
deploy.yml |
Opts this repo’s deploy manifest into config contract coverage via contracts: - config. |
package.json |
Bumps package version to 0.13.0. |
package-lock.json |
Updates lockfile version metadata to 0.13.0. |
docs/references/config-contract-surfaces.md |
Documents manifest opt-in example for config contract (contracts: [config]). |
docs/context-coverage.md |
Updates guidance to include manifest metadata as a valid repair path for config gaps. |
changes.md |
Adds 0.13.0 changelog entry describing the new config-contract opt-in behavior. |
.rabbit/context.yaml |
Regenerates context for 0.13.0, reflecting the repo’s updated config contract coverage. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
660658f to
3cc8417
Compare
udx-github
previously approved these changes
May 27, 2026
3cc8417 to
e98c94c
Compare
udx-github
approved these changes
May 27, 2026
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
deploy.ymlas runtime config unless the manifest content itself carries config contract evidence; no custom filename or custom manifest kind is hardcoded.Validation
bash tests/suite.sh --only repo-contractmake testudx/rabbit-automation-action: config now reportspresentwithdeploy.ymlas config contract evidence.Notes
dev.kitshim/version, so tests do not accidentally exercise a globally installed release.deploy.ymlfilename alone does not satisfy the config contract.