pypi python-gitlab 4.8.0
v4.8.0

latest releases: 5.0.0, 4.13.0, 4.12.2...
3 months ago

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)

Documentation

  • docs: document how to use sudo if modifying an object

Add a warning about using sudo when saving.

Give an example of how to get an object, modify it, and then save
it using sudo

Closes: #532 (d509da6)

  • docs: variables: add note about filter for updating

Add a note about using filter when updating a variable.

Closes: #2835
Closes: #1387
Closes: #1125 (c378817)

Feature

  • feat(api): add support for project cluster agents (32dbc6f)

  • feat(api): add support for container registry protection rules (6d31649)

  • feat(api): add support for package protection rules (6b37811)

  • feat(api): add support for commit sequence (1f97be2)

Fix

  • fix: issues closed_by()/related_merge_requests() use http_list

The closed_by() and related_merge_requests() API calls return
lists. So use the http_list() method.

This will also warn the user if only a subset of the data is returned. (de2e4dd)

  • fix: Have participants() method use http_list()

Previously it was using http_get() but the participants API
returns a list of participants. Also by using this then we will warn
if only a subset of the participants are returned.

Closes: #2913 (d065275)

  • fix(files): CR: add explicit comparison to None

Co-authored-by: Nejc Habjan <hab.nejc@gmail.com> (51d8f88)

  • fix(files): make ref parameter optional in get raw file api

The ref parameter was made optional in gitlab v13.11.0. (00640ac)

  • fix(cli): generate UserWarning if list does not return all entries

Previously in the CLI, calls to list() would have get_all=False by
default. Therefore hiding the fact that not all items are being
returned if there were more than 20 items.

Added --no-get-all option to list actions. Along with the already
existing --get-all.

Closes: #2900 (e5a4379)

Refactor

  • refactor(package_protection_rules): add missing attributes (c307dd2)

Test

  • test(registry): disable functional tests for unavailable endpoints (ee393a1)

  • test(files): test with and without ref parameter in test case (f316b46)

  • test(files): omit optional ref parameter in test case (9cb3396)

  • test(fixtures): remove deprecated config option (2156949)

Don't miss a new python-gitlab release

NewReleases is sending notifications on new releases.