Automated releases based on dprint-plugin-typescript release?

[dsherret]

Hey, thanks for putting in the work and creating this! 😊

I think it would be beneficial to automate the releases of this based on the releases of dprint-plugin-typescript on cargo (I do a lot of releases). Any ideas for automating it?

Notes

• For getting dprint-core version based on dprint-plugin-typescript, I think cargo metadata could be used (https://doc.rust-lang.org/cargo/commands/cargo-metadata.html) then the Cargo.toml in this repo could be updated programatically based on that.
• I don't think there will be any breaking changes in the API, but we can deal with them when a build fails.

[devongovett]

Thanks for your work on dprint! It's really awesome.

Dependabot is probably the simplest, though not completely automated. I'd still have to merge the pr, bump the version in package.json, and run the release workflow. Perhaps that could be automated somehow as well.

[dgellow]

In case that's useful, I had great experience with https://github.com/googleapis/release-please. It's also available as a GitHub workflow you can setup to automate part of the process.