baserev update by copy to link target

• Files Changed
• Browse Source

- Delete migrate-to-pytest.patch
- Delete remove-mock.patch
- Add remove-icecream.patch
- Update to 2.1.1:
  * [Bug]: Fix up an internal utility which monkeypatches a
    Sphinx/docutils internal, so that it accepts arbitrary args/kwargs
    instead of exploding on newer Sphinxes.
- 2.0.1:
  * [Bug]: Fix up an internal utility which monkeypatches a
    Sphinx/docutils internal, so that it accepts arbitrary args/kwargs
    instead of exploding on newer Sphinxes.
- 2.1.0:
  * [Feature]: Allow controlling the name of your development branch
    for source code links (eg “Next 1.x feature release” section
    headers) via the new releases_development_branch config option.
  * [Feature]: Add a new configuration setting,
    releases_supported_versions, allowing you to limit how many “Next
    1.x feature release” (or bugfix, etc) sections appear at the top
    of your changelog.
- 2.0.0:
  * [Bug]: Don’t make tmpdirs in releases.util.make_app when being
    given explicit directory args.
  * [Bug]: Changelog transformation sometimes failed to occur when
    running under a ‘single HTML file’ Sphinx builder (eg singlehtml),
    which resulted in ‘unknown node’ errors. This has been fixed.
  * [Support]: Migrated the test suite to use pytest-relaxed (and thus
    pytest) instead of spec.
  * [Support]: Dropped support for Sphinx <4. We tried to support
    1.8+, but too many transitive dependencies have clearly “moved on”
    and cause various cells in the test matrix to fail hard.

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

SR for python stack proposal

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Add patch remove-mock.patch:
  * Use stdlib mock, not external mock. 
- Drop mock BuildRequires.

• Files Changed
• Browse Source

- refresh migrate-to-pytest.patch: remove pytest-relaxed

• Files Changed
• Browse Source

- Add patch migrate-to-pytest.patch:
  * Migrate to pytest, lightly rebased from upstream.

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

The patch was never merged and its lack now breaks our neck with python-semantic_version 2.8 out for some time

- Restore semanticversioning.patch to allow semantic_version >= 2.7 
  gh#bitprophet/releases#84
  gh#bitprophet/releases#86
- remove color printout in tests

• Files Changed
• Browse Source

- Update to 1.6.3:
  - :support:`87 backported` (via :issue:`88`) Our upper Sphinx version limit was
    mostly defensive and at this point is just too old to even build on
    ReadTheDocs successfully. Removed it for the time being. Thanks to José
    Sánchez-Gallego for the nudge and the patch.
  - :support:`84 backported` Pin us to ``semantic-version<2.7`` as they changed
    their APIs (...) in that version in a way that breaks us. We do not need
    anything they've added recently, so the conservative response is to just pin
    until we truly need to upgrade. Thanks to everyone who reported and submitted
    workarounds for this.
- Drop merged patch semanticversioning.patch

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Do not generate test subpackage

• Files Changed
• Browse Source

- Add patch to fix build with new semantic versioning:
  * semanticversioning.patch

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Move the Name definition above lua code to work on 42.3

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

• Files Changed
• Browse Source

- Enable testsuite in multibuild mode as it creates cycle otherwise

• Files Changed
• Browse Source

- Update to 1.6.1:
  * Support sphinx 1.7

• Files Changed
• Browse Source