releases
releases copied to clipboard
A powerful Sphinx changelog-generating extension.
Over at pygae/galgebra, a lot of my release notes are of the form `The function :func:`useless_function` was deprecated`. Since these are neither features nor bugfixes, we're currently categorizing them as...
I really like what releases has done, and I'm considering adopting it in place of the technique I've [~~developed~~cobbled together](/jaraco/rst.linker), which performs textual substitution on the .rst to inject links....
This is just spitballing so I don't forget N months from now. The current curated-changelog-file approach works well enough, but has frustrating side effects I've never found solutions for, such...
the follow error is raising here: ``` Warning, treated as error: the releases extension does not declare if it is safe for parallel reading, assuming it isn't - please ask...
In cihai, I currently have a tag / release like this: https://github.com/cihai/cihai/blob/v0.9.0a1/cihai/__about__.py `__version__ = '0.9.0a1'` (First, since I prefix my version tags with `v`, #54/#76 applies by master link breaking...
Hi there! I've just ported the documentation for on of my older projects to Sphinx and, since I really, really like `releases`, I was hoping to port that project's change...
Hello, I was just wondering if there were any plans to support building LaTeX documentation with this extension? I write a lot of docs that are consumed both as HTML...
Today I discovered that if you have list above your changelog, Sphinx will choke on it. This is also true if the pre-changelog list is in an included file. Example...
When poking around exposing a parsed changelog programmatically (so folks could e.g. figure out whether the changelog needs updating with a release entry at release time) I realized there's data...
I have the following changelog: ``` rst * :release:`1.1 ` * :feature:`-` New feature * :release:`1.0 ` * :feature:`-` Initial release ``` The "New feature" will appear in the category...