Create new release with recent changes

[Riceman2000]

The changes merged in this PR: #241 fixed an issue with the API that makes an endpoint (ListDnsRecords) unusable. The code has been reviewed and merged, a new release should be generated.

Keeping these changes unreleased for weeks/months will generate more issues and general help requests as people experience broken behavior and (understandably) don't check the commit log to see if their problem has been resolved.

Some other low hanging fruit that could be tossed into this Crate release:

• Adding the repository field
  • Issue: Crates missing repository field #235
  • PR: Add repository in Cargo.toml #242
• Deriving Eq, PartialEq for DnsRecord
  • Issue: Derive Eq for DnsContent #226
  • PR: Derive Eq for DnsContent #227
  • In general please read this on trait derivation: https://users.rust-lang.org/t/what-traits-should-i-normally-derive/484/5
• Not really for a Crate release but please clear out the repository for things more than 1-2 years old as most of it will no longer be applicable

Thank you for your time, I would love to see this repository to get some TLC and bring it up to date for the latest Cloudflare API. It would be very useful for my application along with many others.

[DougAnderson444]

+1

A release would be great, right now my code is breaking because

• Remove 'locked' field from DNS Record spec as it's no longer returned by the API #241

hasn't been incorporated into a release yet.

Also, the Cargo.toml needs to add the repository field for the next release.

cc @Noah-Kennedy

[Riceman2000]

I am having the exact same issue @DougAnderson444 I am glad I am not the only one.

One thing that I have been attempting is to do is make a Crate based off of the OpenAPI schemas posted by Cloudflare in this repository: https://github.com/cloudflare/api-schemas

I think this should be possible but I have not found any tooling that will work with APIs this large/complex, they all have one little thing that is not supported. If you have any ideas I would love to hear them and maybe we can get a working solution up and running. If done properly, an automated pipeline should be able to handle most of this work (in theory).

Thanks for the response