All packaged releases still print when earliest-release doesn't have new or changed release files

Bug #1670173 reported by Miguel Alejandro Cantu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
reno
Confirmed
Low
Unassigned

Bug Description

In my repo, I have serveral packaged releases i.e.:
14.0.1
14.0.2
14.0.3
14.0.4
14.0.5
14.0.6
14.0.7
14.0.8

When I checkout the tag 14.0.4, which has no new or changed release files, then run repo report like so:
git checkout 14.0.4
reno report --earliest-version 14.0.4 | grep '===' -B2

Reno still prints out the release notes before 14.0.4, which is not intended behavior when using the --earliest-version flag:
=============
Release Notes
=============

14.0.3
======
--

14.0.2
======
--

14.0.0
======
--

13.0.0
======

This works fine for tags that *do* have new or changed release files:
git checkout 14.0.3
reno report --earliest-version 14.0.3 | grep '===' -B2
=============
Release Notes
=============

14.0.3
======

Changed in reno:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Doug Hellmann (doug-hellmann) wrote :

The bug tracker for reno has moved to storyboard: https://storyboard.openstack.org/#!/project/933

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.