Skip to content

build: bump django-guid from 3.5.2 to 3.6.1 in /requirements - #751

Open
blaipr wants to merge 1 commit into
ctrliq:mainfrom
blaipr:build/bump-django-guid-3.6.1
Open

build: bump django-guid from 3.5.2 to 3.6.1 in /requirements#751
blaipr wants to merge 1 commit into
ctrliq:mainfrom
blaipr:build/bump-django-guid-3.6.1

Conversation

@blaipr

@blaipr blaipr commented Aug 26, 2026

Copy link
Copy Markdown
Contributor
SUMMARY

Bumps django-guid from 3.5.2 to 3.6.1 in requirements/requirements.txt. It stamps the correlation ID that ties a request's log lines together.

The Python requirements are outside Dependabot's scope on purpose: #675 turned on version updates for github-actions and for npm in /awx/ui and left this file out, because it is compiled by requirements/updater.sh rather than hand-pinned. So this was produced the same way make requirements produces it:

# requirements.in:  django-guid==3.5.2  ->  django-guid==3.6.1
requirements/updater.sh run

run inside the ascender_devel image, which is where that script insists on running. This one is pinned with == in requirements.in, so upgrade cannot move it: the pin is edited first and run recompiles against it. The result is 1 added / 1 removed in each of the two files.

ISSUE TYPE
  • Bug, Docs Fix or other nominal change
COMPONENT NAME
  • API
ASCENDER VERSION
25.5.1

Tests

Tested before opening, in the same image, with django-guid 3.6.1 installed into the AWX venv:

py.test awx/main/tests/unit awx/conf/tests/unit awx/sso/tests/unit
  1404 passed, 1 skipped in 10.36s

CI does not run on pull requests from a fork until a maintainer approves the workflow, so this is what stands behind the change until then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant