However our pod doesn't show up in search results from cocoapods.org
The updated MD files (README and CHANGELOG) that are supplied when the new pod version is published to the trunk aren't updated on the listing page
Background Context
When we initially published a pre-release version, we noticed that the page for our pod wasn't ever generated, the pod never showed up in the search results from cocoapods.org, and manually typing in the URL of the pod (https://cocoapods.org/pods/CloverPayments) would redirect to our where our framework is hosted on Github.
When we decided to publish the 1.0 as non-beta, we found this that seemed to indicated the README and CHANGELOG spec attributes are required binary pods. Since we're publishing an XCFramework, we made sure to include them in the 1.0 podspec. However, we published it with the Github edit/file view links, which appear to have rendered poorly when our listing page was generated (but it was generated this time).
This link:
"changelog": "https://github.com/clover/clover-ios-payment-sdk/blob/main/CHANGELOG.md"
Rendered as:
As such, we submitted a 1.0.1 podspec that included the raw file links for the README and CHANGELOG.
However this was about three days ago (as of this writing), and the listing page (readme and changelog both) still shows the outdated Github file view markup (JSON payload) rather than a formatted markdown that renders as human-readable.
The pod is also still not found when searching for the pod using it's full or partial name from cocoapods.org.
We are able to pull and integrate the pod in our Podfiles as one would normally do from the public trunk/specs repo.
Hey team!
Summary
cocoapods.orgBackground Context
When we initially published a pre-release version, we noticed that the page for our pod wasn't ever generated, the pod never showed up in the search results from
cocoapods.org, and manually typing in the URL of the pod (https://cocoapods.org/pods/CloverPayments) would redirect to our where our framework is hosted on Github.When we decided to publish the 1.0 as non-beta, we found this that seemed to indicated the README and CHANGELOG spec attributes are required binary pods. Since we're publishing an XCFramework, we made sure to include them in the 1.0 podspec. However, we published it with the Github edit/file view links, which appear to have rendered poorly when our listing page was generated (but it was generated this time).
This link:
"changelog": "https://github.com/clover/clover-ios-payment-sdk/blob/main/CHANGELOG.md"Rendered as:
As such, we submitted a 1.0.1 podspec that included the raw file links for the README and CHANGELOG.
"changelog": "https://raw.githubusercontent.com/clover/clover-ios-payment-sdk/main/CHANGELOG.md"However this was about three days ago (as of this writing), and the listing page (readme and changelog both) still shows the outdated Github file view markup (JSON payload) rather than a formatted markdown that renders as human-readable.
The pod is also still not found when searching for the pod using it's full or partial name from
cocoapods.org.We are able to pull and integrate the pod in our Podfiles as one would normally do from the public trunk/specs repo.