List view

• 0.9

  No due date
  0% complete0 open0 closed

• 0.8

  No due date
  0% complete0 open0 closed

• 0.7

  No due date

  •0/1 issues closed
  0% complete1 open0 closed

• 0.6

  No due date

  •0/4 issues closed
  0% complete4 open0 closed

• 0.5

  No due date

  •0/2 issues closed
  0% complete2 open0 closed

• 0.4

  Refresh of the stack Use `pyproject.toml` as configuration Fixes long standing issues

  Overdue by 4 year(s)

  •

  Due by December 12, 2021

  •1/11 issues closed
  9% complete10 open1 closed

• 1.0

  Target for first release with stable API is: - configuration in `pyproject.toml` file (`[tool.bumpr]`) - simpler config with sane defaults (default for a pep-* compliant project hosted on git(hub|lab)) - structured file formats (`yaml`, `toml`, `json` and `ini`) support (replace at key, use data in replacements...) - twine upload - pure PEP440 - changelog and any other file generation (jinja2) from: - any structured data - git commits (at least conventional commits 1.0) - modularized (afeatures as entrypoints as much as possible)

  Overdue by 3 year(s)

  •

  Due by June 1, 2022

  •2/2 issues closed
  100% complete0 open2 closed