arlyon
commented
6 months ago The automated release pipeline has been borked for a while sadly so I have been having to publish releases to GitHub manually. The latest version on the website is the latest git tag but not all tags have a github release so it's all a little messy. We are going to have to rework a decent chunk of the CI / release pipeline for the next branch once it is ready for primetime so I have been putting off fixing it since it'll be soon obsolete.
Apologies for the confusion. Also on my list is updating the readme alongside this stuff.
Once we figure out why semantic release cargo is failing this should all resolve itself and change logs, tags, cargo releases, and GitHub releases should remain synced up.
jwiesler
Describe the bug
https://www.payments.rs/ has a big button labelled "Documentation".
It links to https://docs.rs/async-stripe/0.34.2/stripe , which says "The requested version does not exist"
https://docs.rs/async-stripe/latest/stripe/ shows the latest version as
v0.34.1The latest release shown on the GitHub project page is
v0.18.3, because that's the latest version marked at https://github.com/arlyon/async-stripe/releasesAlso, the top of https://www.payments.rs/ contains a link that implies that it links to the tag
v0.34.2, but that link actually just goes to https://github.com/arlyon/async-stripe (which only displaysv0.18.3as the latest GitHub release, as mentioned above).This… does not inspire confidence for someone looking at this library for the first time. I'd recommend:
crates, and the website.To Reproduce
See above.
Expected behavior
See above.
Code snippets
No response
OS
N/A
Rust version
N/A
Library version
N/a
API version
N/A
Additional context
No response