Closed nmggithub closed 3 months ago
I just pushed a commit to remove the potential problem flag. I noticed the page for my package on the index had picked up some of my changes to my Readme.md, so hopefully this gets picked up soon as well.
Thanks for the report, @nmggithub . We're currently processing builds for Xcode 16b3 for our Ready for Swift 6 project, which delays things a bit. Builds are going to take longer to be picked up than usual for a few more days.
Also note that we don't build default branch changes immediately but rather coalesce them over a maximum of 24 hours.
Ok, builds have finally appeared. Documentation hasn't for some reason, but that's ok for now. Closing this.
It looks like your package has actually uncovered a small bug! Logged here: https://github.com/SwiftPackageIndex/SwiftPackageIndex-Server/issues/3215
It looks like your package has actually uncovered a small bug! Logged here: #3215
Cool to know! Glad I could be of help, however accidental it was.
Hello!
I recently submitted my package Kass to the index. It took a while to show up on the website, but it is now appearing in the index. Unfortunately, the builds are not, and it looks like it hasn't been built at all. The only thing I can thing of that would cause this is the additional flag I added in my
.spi.yml
file.It's intended purpose is to be fed into the
docc
command, by way ofswift generate-documentation
. According to the DocC plugin documentation:The
docc
tool provides the option to specify a specific*.docc
folder to use. I am not sure where your build process addscustom_documentation_parameters
, and I have been unable to find anything in your public repositories that specify as such.However, I would expect this to cause a build failure, or at least a failure in the build pipeline (as documentation generation is not a build-time step). The site reports zero builds, and has done so for at least the past 30 minutes. Can you please confirm why this is happening?
To note, the main page for my package currently displays this message under Compatibility:
As it has been at least half an hour, which is more than a few minutes, I am raising this issue.