Prevent upgrades from leaving software partially migrated

Ajwain is exploring Dependency and Upgrade Assurance to turn migration guidance, support policy, architecture constraints, and release standards into instructions for coding agents and independent checks in review and CI. The aim is to find required code, configuration, test, and rollout work that a version update alone does not reveal.

Find migration work hidden behind a successful version update

An upgrade can compile and pass existing tests while still using a removed configuration key, deprecated API, incompatible plugin, or rollout sequence that conflicts with the migration guidance. Version and dependency tools can identify what changed without determining whether the software has completed that work.

Dependency and Upgrade Assurance would evaluate the changed dependency or platform together with the affected code, configuration, tests, and release material supplied by the team.

Turn upgrade guidance into requirements for the change

The requirements for an upgrade may come from vendor migration guidance, internal support policy, customer support commitments, architecture constraints, or release standards. Ajwain would select the requirements relevant to the affected repository and give coding agents that guidance while they prepare the change.

Independent evaluation would then check the implementation in review and CI. It would identify the affected files or services, the requirement that remains unmet, and the correction, migration, test, or rollout work still needed.

Show what must be resolved before merge or release

A finding would connect the version change to the applicable migration or support requirement and the repository evidence used to assess it. Reviewers could see what was checked, what remains unresolved, and where missing evidence requires human judgment.

Existing dependency tools, tests, and reviewers would remain part of the workflow. Engineering teams would decide whether an exception is acceptable and whether unresolved work should prevent merge or release.

Start with an upgrade whose migration work is hard to verify

Use a past or current upgrade that required expert review beyond changing the version. Bring the repository, the migration and support requirements that applied, and the reviewers who owned the release decision to assess a focused Dependency and Upgrade Assurance proof of concept.

Discuss an upgrade review problem