Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update python-redmine to 2.5.0 #556

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

pyup-bot
Copy link
Collaborator

This PR updates python-redmine from 2.3.0 to 2.5.0.

Changelog

2.5.0

**Deprecations**:

- Requests version required >= 2.31.0

**New Features**:

- *Pro Edition:* RedmineUP [Products plugin](https://www.redmineup.com/pages/plugins/products) support
- Issue copying (see [docs](https://python-redmine.com/resources/issue.html#copying) for details) (Issue 203)

**Improvements**:

- Migrated CI to GitHub Actions, also we now test not only on Linux, but on macOS and Windows as well
- ``dir(resource)`` and ``list(resource)`` now also show properties of an object
- Support for ``issues_assigned`` and ``issues_authored`` relations in User object (Issue 317)
- Original filename will be used as a filename for all uploaded files if a path was provided and filename wasn't set
- *Pro Edition:* Added support for RedmineUP Contact avatar add/update operations (see [docs](https://python-redmine.com/resources/contact.html#create-methods) for details)
- *Pro Edition:* Added support for RedmineUP DealCategory ``create()``, ``update()``, ``delete()`` operations (see [docs](https://python-redmine.com/resources/deal_category.html#create-methods) for details)
- *Pro Edition:* RedmineUP CrmQuery resource now supports ``invoices`` and ``expenses`` relation attributes
- ``PerformanceWarning`` will be issued when Python-Redmine does some unnecessary redirects before the actual
request is made

**Changes**:

- *Backwards Incompatible:* API key is now being sent in the X-Redmine-API-Key header instead of the key GET parameter which makes things more secure in case of a failed connection, but it might created issues for servers that don't do custom request header forwarding by default, so be sure to check your web server before upgrading (Issue 328 and Issue 330) (thanks to [Tom Misilo](https://github.com/misilot) and [Ricardo Branco](https://github.com/ricardobranco777))
- *Backwards Incompatible:* User ``all`` operation now really returns all users, i.e. not only active, but locked, registered and anonymous as well instead of only returning just active users in previous versions due to the respect to Redmine's standard behaviour (Issue 327)

**Bugfixes**:

- Tests were failing on Windows OS
- Tests were failing on Python 3.12 (Issue 332) (thanks to [Michał Górny](https://github.com/mgorny))
- Some closed Issues weren't converted to Resource objects using ``redmine.search()``
- *Pro Edition:* RedmineUP Invoice resource ``order`` attribute was returned as a dict instead of being converted to Resource object
- *Pro Edition:* RedmineUP CrmQuery resource ``deals`` and ``contacts`` relation attributes didn't work
- *Pro Edition:* RedmineUP DealStatus resource ``deals`` relation attribute didn't work

**Documentation**:

- Mentioned support for ``author_id`` in Issue's resource filter operation

2.4.0

**Deprecations**:

- Requests version required >= 2.28.2
- Removed Python 2.7, 3.5, 3.6 support as it's not supported by Requests anymore
- Removed support for ``python setup.py test`` as it became deprecated by setuptools

**New Features**:

- *Pro Edition:* RedmineUP [Helpdesk plugin](https://www.redmineup.com/pages/plugins/helpdesk) support (Issue #116)
- *Pro Edition:* RedmineUP [Invoices plugin](https://www.redmineup.com/pages/plugins/invoices) support (Issue #301)
- Timezone support (see [docs](https://python-redmine.com/configuration.html#timezone) for details) (Issue 271)

**Improvements**:

- Added support for Python 3.10, 3.11 and latest PyPy
- Added support for `allowed_statuses` to ``include`` param and on demand includes for Issue resource (requires Redmine >= 5.0.0)
- Added support for `issue_custom_fields` to ``include`` param and on demand includes for Project resource (requires Redmine >= 4.2.0)
- Added support for `comments` and `attachments` to ``include`` param and on demand includes for News resource (requires Redmine >= 4.1.0)
- *Pro Edition:* Added support for RedmineUP Contact `projects` to ``include`` param and on demand includes for ``all()`` and ``filter()`` operations
- *Pro Edition:* Added support for RedmineUP Note ``create()``, ``update()``, ``delete()`` operations (see [docs](https://python-redmine.com/resources/note.html#create-methods) for details)
- Added support for Project ``close()``, ``reopen()``, ``archive()``, ``unarchive()`` operations (see [docs](https://python-redmine.com/resources/project.html#additional-methods) for details, requires Redmine >= 5.0.0)
- Added support for updating and deleting issue journals (see [docs](https://python-redmine.com/resources/issue.html#journals) for details, requires Redmine >= 5.0.0)

**Changes**:

- *Backwards Incompatible:* Switched to pytest instead of nose as nose project is dead (Issue 312)
- *Backwards Incompatible:* Removed usage of distutils.LooseVersion internally since it became deprecated and caused warnings, because of that all version info internally is now being represented as tuples and not strings as before

**Bugfixes**:

- Stop raising `ResourceAttrError` for attributes that actually exist, but their value is `None` (Issue 261)
- *Pro Edition:* RedmineUP Deal resource ``related_contacts`` attribute was returned as a list instead of being converted to ResourceSet object
- Project resource ``default_assignee`` attribute was returned as a dict instead of being converted to Resource object
- Project resource ``time_entry_activities`` attribute was returned as a list instead of being converted to ResourceSet object

**Documentation**:

- Document requirement of `project_id` param for `query_id` filter (Issue 285) (thanks to [Doezer](https://github.com/Doezer))
- Mentioned support for ``user_id`` in TimeEntry's resource create/update (Issue 298)
- Mentioned support for additional scopes for Search API
Links

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant