Release v1.4.0

Open
#358 0 comments 0 reactions 1 assignee View on GitHub

@miroslavpojer is already working on this.

Since Nov 19, 2026.

Assessment

This issue has not been assessed yet.

Description

epic
Background

The next minor release after v1.3.3. It has no single theme: it collects compatibility fixes, documentation bugs, tech-debt items and one small feature that do not depend on the larger roadmap epics (#300 v1.5.0, #301 v1.6.0, #302 v1.7.0).

The minor version bump comes from #332, which adds a new optional input. Everything else is backward compatible.

Goals
  • Bring back support for Python 3.11+ (raised to 3.14 in v1.1.0), keeping CI coverage on 3.14 (#355)
  • Replace pylint with ruff and add a make qa target for local and CI checks (#303)
  • Fix the README and example workflows that break when copied, and correct stale version comments on pinned actions (#356)
  • Make the Python fallback and the docs match the {progress} default that action.yml already sets (#297)
  • Make since-time mining robust: no crash on since=None, and no silently incomplete release notes when a GitHub API call fails (#338)
  • Let the action optionally create the git tag itself (#332)
Subtasks
  • #355 Lower minimum supported Python version to 3.11
  • #303 Introduce ruff and make qa
  • #356 Fix broken workflow examples and stale action version comments
  • #297 Progress placeholder is not present in default value
  • #338 Since-time mode: since=None can crash get_issues(), and API failures silently degrade to empty results
  • #332 Adding optional parameter - create annotated git tag
Suggested order of work
  1. #355 first. PR #357 is already open. It sets the Python 3.11 baseline and the CI matrix (3.11 + 3.14) that every later PR is tested against, and the target version the formatter and linter use.
  2. #303 next, before other code changes. Switching linters may touch many files. Doing it while no other PRs are open avoids merge conflicts, and every later PR then passes make qa. Only task 1 of #303 (adopt ruff in this repository) belongs to this release. The handbook tutorial and the issues for other repositories are tracked outside this epic.
  3. #356 and #297. Small, independent fixes that can run in parallel. Both touch release_notes_generator/action_inputs.py (unused cache attribute; fallback default of row-format-hierarchy-issue), so merge one and rebase the other.
  4. #338. Decide one thing up front: should a failed GitHub API call in since-time mode end the run with an error, as compare mode does, or log a warning and continue? Suggested: fail, as compare mode does. Today the run succeeds with incomplete release notes.
  5. #332 last. It is the only new feature and the reason for the minor bump. It builds on the corrected examples from #356, and can then remove the manual "Create and push tag" step from the README "Manual Release Dispatch" example. Decide the input name, what happens when the tag already exists, and how to document the contents: write permission it needs.
Related / References
  • Follows v1.3.3
  • Roadmap epics moved by one minor version: #300 → v1.5.0, #301 → v1.6.0, #302 → v1.7.0
  • #297 moved here from #300
Dominant language
Python
Stars
12
Forks
0
Avg merge
1m
Merged PRs (30d)
6

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AbsaOSS/generate-release-notes

All issues in AbsaOSS/generate-release-notes

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.