Conversation
Not sure whether this makes sense to surface in the changelog given that it deals with an internal, unversioned API. That said, if a customer is using connectapi for things dealing with git and they run into this issue, they should have some way of knowing that they need to upgrade. It's not their fault that connectapi is using internal APIs. @jonkeane let me know what you think. |
jonkeane
left a comment
There was a problem hiding this comment.
These changes look good, thanks for jumping on these
Not sure whether this makes sense to surface in the changelog given that it deals with an internal, unversioned API.
I agree with your assessment that it's not worth calling out in the Connect changelog.
|
Sounds good, I also checked the connect extensions and didn't find any that rely on this functionality, so I think the extensions should keep running fine regardless (breaking these was what prompted us to add that PR checklist item). |
Intent
Fix integration tests, which failed on the nightly connect build this week:
https://github.com/posit-dev/connectapi/actions/runs/24657089648/job/72093203473
Approach
Add a helper than can parse either the old format or the new.
Checklist
NEWS.md(referencing the connected issue if necessary)?devtools::document()?connectapi.