Publish the updates on plugin supporting code

[Bert-Proesmans]

Hi guys, I'm writing in from the context of sops pull request getsops/sops#1465 (read: sops, a wrapper of age, cannot currently process age keys that are handled by age plugins).

The referenced PR makes use of the age go-code as a library and specifically interacts with the exposed plugin package and abstraction structs committed here 6976c5f...c89f0b9 (committed to master at 2023-08-05)

Do you guys think that functionality is tested comprehensively enough, and builds enough functionality scope, to publish it under a new (point-)release?

Please mention if there are blockers, or otherwise unrelated milestone information, that affect the next releasedate. I fully intend to contribute and see the above PR through!

[Bert-Proesmans]

Hi @FiloSottile, I'm pinging you in case you wanted to be aware of the question to create a new release but somehow missed this thread. Do you happen to have more details about the schedule for the next release of age?

[Bert-Proesmans]

Done with release v1.2.0 (https://github.com/FiloSottile/age/releases/tag/v1.2.0)

[FiloSottile]

Thanks for reaching out, and glad the release works for you! Feel free to ping me on SOPS issues if there's something we can do on our side to enable you.