Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 1.6.4 #233

Closed
wants to merge 6 commits into from
Closed

Release 1.6.4 #233

wants to merge 6 commits into from

Conversation

oliverchang
Copy link
Contributor

No description provided.

calebbrown and others added 6 commits February 1, 2024 13:13
Signed-off-by: Caleb Brown <calebbrown@google.com>

Signed-off-by: Caleb Brown <calebbrown@google.com>
Signed-off-by: Caleb Brown <github@calebbrown.id.au>
Rationale: reduce the amount of false negatives in commits belonging to
branches forked in-between `introduced` and `fixed`/`limit`.

Closes #216.

Signed-off-by: Stefano Zacchiroli <zack@upsilon.cc>
Adds back the `as defined by the database` in the description of the
`range` object's `database_specific` field. This brings it into line
with the descriptions of the other two `database_specific` fields. I
suspect it was just a bad copy/paste operation as we were adding those
fields to other objects beyond the top level.

Signed-off-by: Chris Bloom <chrisbloom7@github.com>
Fixes #208.

---------

Signed-off-by: Oliver Chang <ochang@google.com>
Signed-off-by: Oliver Chang <oliverchang@users.noreply.github.com>
@oliverchang oliverchang changed the title Release 1.6.2 Release 1.6.4 Apr 5, 2024
@oliverchang oliverchang closed this Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants