Closed hyrodium closed 2 years ago
Thanks for the notification! In f59a639bd2f2228bffaf214923407c8a42993dbe I've added ssh key for both CompatHelper and TagBot, hope we can successfully trigger it in the next release.
In the meantime, I've manually recreated a tag v0.9.9+doc1
to trigger the release build for documentation.
For unknown reasons, Documenter refuses to update stable
with v0.9.9+doc1
so I manually create a not-yet-existed version v0.9.10
tag and then immediately removed it. Just to link stable version to v0.9.
I also tried to manually modify gh-pages
branch and then GitHub refuses to build pages for my manual commit 😢
Thanks for the quick fix!
For unknown reasons, Documenter refuses to update
stable
withv0.9.9+doc1
That was because we have [compat]
table in docs/Project.toml
and the specified version was old.
The version with meta (like v0.9.9+doc1
) seems available since Documenter v0.25 because the "Fixing broken release deployments" section is not documented in v0.2 4. https://juliadocs.github.io/Documenter.jl/v0.24/
https://juliatesting.github.io/ReferenceTests.jl/v0.9/ returns 404, but https://juliatesting.github.io/ReferenceTests.jl/dev/ is deployed.
This is because the setting of
DOCUMENTER_KEY
is not correct. See more information in https://juliadocs.github.io/Documenter.jl/dev/man/hosting/#GitHub-Actions.