This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/pip/django-3.2.18
in repository https://gitbox.apache.org/repos/asf/airavata-custos-portal.git
omit 1e593be Bump django from 3.2.16 to 3.2.18
add eabab17 Fix Dockerfile build
add 148df01 Update names of CUSTOS environment variables
add 7677f53 Adding gunicorn dependency and freezing all others
add dd7ba07 Merge pull request #173 from apache:fix-django-dockerfile
add 6477853 Bump django from 3.2.16 to 3.2.18
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (1e593be)
\
N -- N -- N refs/heads/dependabot/pip/django-3.2.18 (6477853)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
Dockerfile | 6 ++++--
airavata_custos_portal/settings.py | 26 +++++++++++++-------------
docker-compose.yml | 11 +++++------
requirements.txt | 38 ++++++++++++++++++++++++++++++++++++--
4 files changed, 58 insertions(+), 23 deletions(-)
