Sergio Rey
Sergio Rey
yes, see the top of this issue.
I think the reason the docs were not getting updated (2.4 was the last version) is that I forgot to run the sync step last release. I just did a...
The other complication I want to address is that with the move to versioneer, I'm not quite sure how to have the right tag on the docs when we build...
the release is ready to go, but I wanted to see if we could dial in the doc build as part of the release. Ideally, we want to be able...
This is the problem with the current approach: 
I have a draft release on gh that will create the v2.6.0 tag when published.
So if I publish the release, I can then update the docs and it should grab the new tag?
release action appears to work for [pypi](https://pypi.org/project/pysal/)
Will have to fix the version tag before pushing to pypi in that action:  Version is 2.6 but our badge in the description is 2.5.
Once #1252 is merged, the remaining thing (I think) here is to add this [gh-action](https://github.com/pysal/spaghetti/actions/runs/1043807199/workflow).