patchwork:pyup-pin-psycopg2-binary-2.8.5

Last commit made on 2020-04-06
Get this branch:
git clone -b pyup-pin-psycopg2-binary-2.8.5 https://git.launchpad.net/patchwork

Branch merges

Branch information

Name:
pyup-pin-psycopg2-binary-2.8.5
Repository:
lp:patchwork

Recent commits

4859d0e... by pyup-bot <email address hidden> on 2020-04-06

Pin psycopg2-binary to latest version 2.8.5

c073c1a... by pyup-bot <email address hidden> on 2020-04-06

Pin psycopg2-binary to latest version 2.8.5

cafd953... by Stephen Finucane <email address hidden> on 2020-04-05

docs: Remove 'earliest_version' config

This is unnecessary and was disabling reno's built-in ability to detect
a base branch.

Signed-off-by: Stephen Finucane <email address hidden>

2cb70d1... by Stephen Finucane <email address hidden> on 2020-04-05

tox: Pass positional arguments to 'docs' job

Signed-off-by: Stephen Finucane <email address hidden>

448d708... by Stephen Finucane <email address hidden> on 2020-04-05

docs: Update reno for stable/2.2

Signed-off-by: Stephen Finucane <email address hidden>

c71a79f... by Stephen Finucane <email address hidden> on 2020-04-05

Post-release version bump

Signed-off-by: Stephen Finucane <email address hidden>

027de4b... by Stephen Finucane <email address hidden> on 2020-04-05

Release 2.2.0

Signed-off-by: Stephen Finucane <email address hidden>

b44a77d... by Stephen Finucane <email address hidden> on 2020-03-19

trivial: Feed 'patchwork.migrations' through black

Include migrations in the flake8 checks, which should catch some simple
undefined variables errors.

Signed-off-by: Stephen Finucane <email address hidden>

271d913... by Daniel Axtens on 2020-03-17

REST: Add release note for faster queries

Didn't quite seem like it fit anywhere else in the series. I want
the release note mostly because I hope to backport this to stable.

Signed-off-by: Daniel Axtens <email address hidden>
Reviewed-by: Stephen Finucane <email address hidden>

046aa15... by Daniel Axtens on 2020-03-17

REST: extend performance improvements to other parts of the API

We can trivially extend what we've just done to other parts of the API.

I haven't done much by way of benchmark but we're seeing multiple 'x's
pretty much across the board when filtering.

Signed-off-by: Daniel Axtens <email address hidden>
Reviewed-by: Stephen Finucane <email address hidden>