Let's see if we can automate some of the fixes necessary after dependency updates, necessary due to breaking changes.
I'm skeptical about this working, because very recent releases breaking something won't be what models know about, so this will rely on them figuring it out just from the error message. Perhaps we can do some clever prompting to point them to the release's diff (the PR body includes the release notes in most cases, what Copilot will use), which is available from the release if it's one in the GitHub repo.
#1167 needs to be done before this so package consolidation is solved.
Jira issue