This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/pip/django-3.2.19
in repository https://gitbox.apache.org/repos/asf/airavata-django-portal.git
discard fd00d63e Bump django from 3.2.18 to 3.2.19
add 1bebb7eb AIRAVATA-3696 instantiate output view providers in ready()
add eef9d7e5 AIRAVATA-3696 removing unused import
add f29a74da AIRAVATA-3697 log error if filesystemencoding isn't 'utf-8'
add a64264c1 AIRAVATA-3697 fix download of utf8 filename
add 984b2614 AIRAVATA-3694 Remove data retention message for now
add bd365382 Merge branch 'staging' into develop
add 7b92e6ff Bump django from 3.2.18 to 3.2.19
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 (fd00d63e)
\
N -- N -- N refs/heads/dependabot/pip/django-3.2.19 (7b92e6ff)
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:
django_airavata/apps/api/apps.py | 6 ++++++
django_airavata/apps/api/exceptions.py | 6 ++++++
django_airavata/apps/api/output_views.py | 11 +++++++----
.../js/components/storage/ExperimentStorageViewContainer.vue | 4 ++--
django_airavata/settings.py | 5 -----
requirements.txt | 2 +-
6 files changed, 22 insertions(+), 12 deletions(-)
