After switching the tooling in my (registered) Julia package from pre-1.0 (REQUIRE, attobot) to post-1.0 (Project.toml, Registrator, TagBot action) I’m having trouble getting Documenter to build the docs for the current release and set the stable link correctly.
Before the switch, docs were built and deployed from a julia-0.6 worker running whatever release of Documenter was compatible with it, and now docs are built and deployed from a julia-1.0 worker with Documenter 0.24.x – I have read and followed all the upgrade instructions for the interim Documenter releases, and the new setup does correctly build the docs for my master branch and links them as “dev”; this part seems to work as intended.
I realize this may be some kind of chicken-and-egg problem. In the first step of the tooling switch, I created my Project.toml and in there set
version=0.6.0 (the previous release had been 0.5.0). After pushing my commits to Github, the Travis build got triggered and the new docs were built and linked as “dev”. At that stage I guessed this was expected behavior because, although the Project.toml said
version=0.6.0, there had not been a release with that version number/tag yet, so Documenter didn’t really have a reason to build docs for “0.6.0” and treat them as “stable”. Then I set up Registrator and the TagBot action on my repo, got my new version registered (yay!) and eventually TagBot kicked in and made the release (yay!) and tagged it. Now, I thought, my repo should be in a state where Documenter would realize that there’s a 0.6.0 release and treat it as stable. So I went to Travis and manually triggered a build from master. The build stage for Documenter runs through, I can see it’s getting the right commit, and it can see the new tag
* [new tag] v0.6.0 -> v0.6.0
Warning: removing `stable` and linking `stable` to `v0.5.0`.
so the 0.6.0 release somehow seems to get ignored. The “dev” branch does have the correct docs for master, but no “0.6.0” docs branch is created, and “stable” still points to the previous 0.5.0 release.
How can I tell Documenter to recognize the new release? IIRC in the past new releases were handled automatically by Documenter, and I guess this should still be happening, so I assume I’ve broken something somewhere… maybe it’s related to the
versions.js file? Though I thought that is created automatically.
Note, currently my 0.6.0 and master point to the same commit, would that cause a problem?