It looks like there is an additional property added (“meta”), which is a breaking change with the library I am currently using (we are working on a fix).
My question is, is there a mailing list or a post on these boards, or some other way to know when changes are being pushed to the staging and production APIs?
Yep, this forum has an API Announcements category for this purpose. You can subscribe to new posts using the steps described here.
This is the announcement for the new meta entry:
@pfg’s answer (Thank you!) about the API announcements category is the correct place to look. I haven’t made an announcement about this change yet but will post one today.
@jekstrom What client library are you working on? There was one other report of this breaking a client and I’ve filed https://github.com/letsencrypt/boulder/issues/2883 to have a central place to discuss. Since the “meta” entry has been present since draft-02 I’m hesitant to roll it back at this point and would instead encourage clients to take the approach you are & develop a fix.
Small correction: That’s the announcement for a separate random entry at the top level of the
/directory. There isn’t an announcement about the “meta” entry.
Thanks for the reponses. We will have to monitor the API Announcement channel.
I am not directly involved in creating a client, but we have issued a PR (noted on the github issue) on the client that we’re using (https://github.com/fszlin/certes).
The issue was the client library was assuming a general structure of string -> uri.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.