Skip to content
This repository has been archived by the owner on Jun 13, 2020. It is now read-only.

Bump django from 1.8.14 to 1.11.29 #39

Open
wants to merge 71 commits into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jun 12, 2020

Bumps django from 1.8.14 to 1.11.29.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

rosskarchner and others added 30 commits November 18, 2016 15:40
This reverts commit 2554d1e.
update data set link to bypass new socrata "primer" page
Remove reference to google analytics
Update content on complaints landing page
Modifying api endpoints in js and html
As part of the first release of Mosaic, the CCDB landing page needs
several updates:

- Remove the self-updating complaint number
- Remove the complaint randomizer
- Remove the data downloader (and replace it with a few static links)
- Update some text in the about the data section
- Add a note about recent CCDB updates
The section on the recent CCDB changes needed to be more noticable, so
we've moved it into a well above the "About the data" section.
We had a few small content updates to make after the CCDB landing page
went through clearance.
Add links to CCDB crosswalk PDFs
rosskarchner and others added 28 commits August 2, 2017 13:55
allow technical issues banner to be enabled on-demand
It created a dependency on Socrata, and the results were no longer used
build wheels and attach them to new releases
Change the links for CCDB5 Release
Wrap the CCDB5 links in the CCDB5 flag
As part of cfpb/development#134 this PR aims to document the current level of browser support within this project.
The current logic for the complaint database landing page invokes a
format_narratives function that does some processing on narrative data
pulled down from S3.

That data currently causes the following error to be logged on every
single load of the landing page:

    format_narratives:KeyError
    There is problem accessing with the given key, which probably means the json has missing data
    'date_received'

This error gets printed because each narrative in the current JSON data
doesn't necessarily contain that key.

In practice, this doesn't matter at all because this narrative data is
never used on the landing page. It gets processed into a "narrative"
variable that gets passed into the template, but that variable isn't
used at all.

The JSON data is still used for stats to present the number of
complaints that were resolved in a timely manner, so we still need to
keep fetching of the JSON. But if the narrative data itself isn't
displayed at all, can this logic (and the frequently-appearing error) be
removed?

One other minor change: the formatting of .travis.yml has been changed
so that multiple environment variables are used globally, instead of
causing two separate Travis jobs.
Remove deprecated narrative formatting
Add noopener rel attribute to target blank links
Documenting browser support
Bumps [django](https://github.com/django/django) from 1.8.14 to 1.11.29.
- [Release notes](https://github.com/django/django/releases)
- [Commits](django/django@1.8.14...1.11.29)

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Jun 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file python Pull requests that update Python code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet