Updates "Dude, Where's My Stuff?" to v2.7.0 and adds Google Sheet API Verification Metadata

[jaybyrrd]

What's New?

New features

• Add Google Sheets data exporting, see README.md for more details (Big thanks to @jaybyrrd)

Full Changelog: Thource/[email protected]

[runelite-github-app]

Includes non-plugin changes

Includes changes by non-author

dude-wheres-my-stuff: 37644bf348929e2540567fb1f955d812a4b5ca54...6672e8c123d79811c9bddb3c58e452e79a6bcc22

[jaybyrrd]

Fixes the issue in #6252

[YvesW]

Thource should do that himself in that PR. Also beware that reviewing dependencies might take a very long time.

Additionally, there's already a google sheets API that got reviewed. Try using that.

[jaybyrrd]

Gotcha. We didn't know if it matters who raises the change since we have been working together on getting this released. In his PR he mentioned reaching to me to work on the issue he ran into.

With regard to api versions, we are using a major version that is significantly more recent than the one available. Also we don't know when they intend to update. Can we raise an issue on their plugin to update to this version? It seems prudent to prefer newer versions over older ones on dependencies like these.

On dependency review, totally understood. I can take a closer look but I think all of them are managed by Google so I hope that helps.

[YvesW]

1. Like I said, Thource has to do it in his own PR. He's the only author of the plugin. If he wants to add you, he has to add you to the plugin file before your PRs are allowed to be merged into the hub for his plugin.
2. They probably aren't changing dependency versions, since it requires reviewing all changes made to it/potentially reviewing the whole dependency again. Asking them to use a newer version is useless; if you'd require a newer version, you'd just add it as dependency.
3. Reviewing a dependency takes a lot of time and only one of the reviewers does this. Expect it to probably take months. Thus, try using the already reviewed version.

[jaybyrrd]

@YvesW our package takes non transitive dependencies on other packages too and will require a review regardless I think. Who typically does the review? We are happy to go through the right process. Perhaps the process can be lighter since the packages are related/the same and it's mainly versioning.

We can certainly have Thource raise the pull request.

[Felanbird]

Duplicate of #6252