Using AI Library Upgrade

This guide shows the typical flow for upgrading dependencies with Lineai and AI assistance.

1. Open a pull request with dependency changes

• Update your dependency file (e.g., .csproj, pom.xml, build.gradle).
• Open a PR as you normally would.

2. Review Change Request impacts

• Lineai evaluates the PR and enriches the Change Request with library‑specific impacts.
• In Lineai, open the Change Request linked to your PR and review differences and impacted items.

3. Generate upgrade tickets

• The service uses AI to produce actionable tickets with:
  • Recommended API replacements or refactors
  • Conditions of satisfaction and risks
  • Investigation items where automation is not possible

Tickets appear as PR comments or in your issue tracker depending on your integration.

Track progress on the AI Workflow Status page while tickets are generated and applied.

4. Auto‑implement fixes (optional)

• When permitted, the system can apply changes and push commits back to the PR branch.
• Each commit is small and scoped to ticketed changes to aid review.

5. Validate in CI/CD

• Your pipeline builds and tests the PR normally.
• If configured, build results are sent to Lineai to inform iterative improvements.

6. Iterate if needed

• On build failures, the system can try up to a few times to improve the changes based on build feedback.
• When builds pass, proceed with normal code review and merge.

Tips

• Keep PR descriptions clear; include release notes links when available.
• Maintain a repo guidance file (e.g., agents.md) with build/test instructions for best AI results.
• See Custom Prompting for recommended structure: Custom_Prompting.md
• You can use the feature in a read‑only mode (no auto‑push) to review tickets first.