I recently had the chance to test out the new API, and it worked like a charm.
Thank you for exposing release notes via an API so that I can automate uploading those to Tidelift (though I still need to write a tool to handle that process so I don’t have to hand-craft a bash to upload a single version ).
On the API documentation, I assumed the
name parameter needed to be URL encoded. My packages all begin with
npm scope, so the name typically needs to be URL encoded before POSTing it places. During my test, I URL encoded the name, and that seemed to work fine.
Generating a token was pretty straight forward.
I POST’d release notes for a version,
3.1.1, of my package,
@hutson/generator-python-library, that does not exist (It’s not a tag on the repository or published to
npm), and I received
HTTP/1.1 201 Created. I’m not sure what the expected behavior should be here.
Related to that, in the UI, I’m not sure how to access release notes for versions other than the latest. I was hoping to go back and delete the invalid version release notes.