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.3 #234

Merged
merged 7 commits into from
Apr 5, 2024
Merged

Release 1.6.3 #234

merged 7 commits into from
Apr 5, 2024

Conversation

oliverchang
Copy link
Contributor

No description provided.

calebbrown and others added 7 commits February 1, 2024 13:13
Signed-off-by: Caleb Brown <[email protected]>

Signed-off-by: Caleb Brown <[email protected]>
Signed-off-by: Caleb Brown <[email protected]>
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 <[email protected]>
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 <[email protected]>
Fixes #208.

---------

Signed-off-by: Oliver Chang <[email protected]>
Signed-off-by: Oliver Chang <[email protected]>
Signed-off-by: Oliver Chang <[email protected]>
@oliverchang oliverchang merged commit b4adcc1 into live Apr 5, 2024
1 of 2 checks passed
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.

6 participants