Consider our Dependabot upgrade experience

[reefdog]

Dependabot is telling people about the SDK upgrades, including… us! Whee! Here's the PR that it just opened on the front-end:

PhilanthropyDataCommons/front-end#656

Lacking from the output which some other (but not all) Dependabot PRs have:

• Release notes
• Changelog
• Commits

I'll bet we don't generate some of those, and maybe shouldn't/won't. But as an SDK user, when notified by Dependabot of an update, I would like some useful call to action to inspect what changed. I leave it to the room to discuss what's right for this project.

[reefdog]

Bumping this, not for immediate resolution but just because it's probably worthwhile to +1 anytime it has a noticeable impact.

Even as a PDC dev, I'm not always plugged into the SDK update cycle / what comes with each version. I know where to find it (https://github.com/PhilanthropyDataCommons/service/blob/main/CHANGELOG.md), but I shouldn't have to. It would be much more intuitive for the Dependabot PR to have some way of getting to the changelog so I can see just what I'm upgrading and why.

I know our SDK deployment process might make this a real hassle if not impossible. But still, it's a real need that our SDK users will have as well, so I'll keep politely beeping the horn.

[reefdog]

Wait… I'm even more confused just now…

That PR bumps @pdc/sdk from 0.9.1 to 0.9.2. But of course those version numbers don't mean anything in the context of this repo. I thought tracking it back to the service repo would illuminate, but service's main branch only seems to be on 0.9.1. What is 0.9.2?

Moved this to a separate and more focused issue: #23