Bump python-gitlab from 4.7.0 to 4.8.0

[dependabot]

Bumps python-gitlab from 4.7.0 to 4.8.0.

Release notes

Sourced from python-gitlab's releases.

v4.8.0 (2024-07-16)

Chore

• chore(deps): update gitlab/gitlab-ee docker tag to v17.1.2-ee.0 (6fedfa5)

• chore(deps): update all non-major dependencies (4a2b213)

• chore(ci): specify name of "stale" label

Saw the following error in the log: #2618 Removing the label "Stale" from this issue... ##[error]#2618 Error when removing the label: "Label does not exist"

My theory is that the case doesn't match ("Stale" != "stale") and that is why it failed. Our label is "stale" so update this to match. Thought of changing the label name on GitHub but then would also require a change here to the "any-of-labels". So it seemed simpler to just change it here.

It is confusing though that it detected the label "stale", but then couldn't delete it. (44f62c4)

• chore(ci): stale: allow issues/PRs that have stale label to be closed

If a stale label is manually applied, allow the issue or PR to be closed by the stale job.

Previously it would require the stale label and to also have one of 'need info' or 'Waiting for response' labels added. (2ab88b2)

• chore(ci): use codecov token when available (b74a6fb)

• chore(deps): update python-semantic-release/upload-to-gh-release digest to fe6cc89 (3f3ad80)

• chore(deps): update all non-major dependencies (0f59069)

• chore: add show_caller argument to utils.warn()

This allows us to not add the caller's location to the UserWarning message. (7d04315)

• chore: use correct type-hint for die() (9358640)

• chore(deps): update gitlab/gitlab-ee docker tag to v17.1.1-ee.0 (5e98510)

• chore(deps): update python-semantic-release/upload-to-gh-release digest to c7c3b69 (23393fa)

• chore(deps): update all non-major dependencies (cf87226)

... (truncated)

Changelog

Sourced from python-gitlab's changelog.

v4.8.0 (2024-07-16)

Chore

• chore(deps): update gitlab/gitlab-ee docker tag to v17.1.2-ee.0 (6fedfa5)

• chore(deps): update all non-major dependencies (4a2b213)

• chore(ci): specify name of "stale" label

Saw the following error in the log: #2618 Removing the label "Stale" from this issue... ##[error]#2618 Error when removing the label: "Label does not exist"

My theory is that the case doesn't match ("Stale" != "stale") and that is why it failed. Our label is "stale" so update this to match. Thought of changing the label name on GitHub but then would also require a change here to the "any-of-labels". So it seemed simpler to just change it here.

It is confusing though that it detected the label "stale", but then couldn't delete it. (44f62c4)

• chore(ci): stale: allow issues/PRs that have stale label to be closed

If a stale label is manually applied, allow the issue or PR to be closed by the stale job.

Previously it would require the stale label and to also have one of 'need info' or 'Waiting for response' labels added. (2ab88b2)

• chore(ci): use codecov token when available (b74a6fb)

• chore(deps): update python-semantic-release/upload-to-gh-release digest to fe6cc89 (3f3ad80)

• chore(deps): update all non-major dependencies (0f59069)

• chore: add show_caller argument to utils.warn()

This allows us to not add the caller's location to the UserWarning message. (7d04315)

• chore: use correct type-hint for die() (9358640)

• chore(deps): update gitlab/gitlab-ee docker tag to v17.1.1-ee.0 (5e98510)

• chore(deps): update python-semantic-release/upload-to-gh-release digest to c7c3b69 (23393fa)

• chore(deps): update all non-major dependencies (cf87226)

... (truncated)

Commits

• 18f6be5 chore: release v4.8.0
• 32dbc6f feat(api): add support for project cluster agents
• ee393a1 test(registry): disable functional tests for unavailable endpoints
• c307dd2 refactor(package_protection_rules): add missing attributes
• 6d31649 feat(api): add support for container registry protection rules
• d509da6 docs: document how to use sudo if modifying an object
• 6b37811 feat(api): add support for package protection rules
• c378817 docs: variables: add note about filter for updating
• 6fedfa5 chore(deps): update gitlab/gitlab-ee docker tag to v17.1.2-ee.0
• 4a2b213 chore(deps): update all non-major dependencies
• Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[dryrunsecurity]

DryRun Security Summary

The pull request updates the python-gitlab library from version 4.7.0 to 4.8.0, but without more information about the changes, it's unclear if this addresses any security issues, and the large number of dependencies in the requirements.txt file should be carefully reviewed as part of the ongoing application security process.

Expand for full summary

Summary:

The code changes in this pull request involve an update to the python-gitlab library from version 4.7.0 to version 4.8.0 in the requirements.txt file. While library updates can sometimes include security fixes, without further information about the specific changes in the new version, it's difficult to determine if this update addresses any security-related issues.

However, it's important to note that the requirements.txt file contains a large number of dependencies, which can increase the attack surface of the application. As an application security engineer, it's crucial to carefully review all dependencies and ensure that they are necessary, up-to-date, and secure. Additionally, it's a good practice to periodically review the dependency tree and identify any transitive dependencies that may introduce security risks.

Overall, the code change appears to be a routine library update, but it's important to continue monitoring the application's dependencies and security posture as part of the ongoing application security review process.

Files Changed:

• requirements.txt: The only change in this file is an update to the python-gitlab library from version 4.7.0 to version 4.8.0. While library updates can sometimes include security fixes, without further information about the specific changes in the new version, it's difficult to determine if this update addresses any security-related issues. Additionally, the requirements.txt file contains a large number of dependencies, which can increase the attack surface of the application and should be carefully reviewed.

Code Analysis

We ran 9 analyzers against 1 file and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	1 finding

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[mtesauro]

Approved