Skip to content

fix: declare lxml as a runtime dependency (v1.6.1) #84

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.

Sign up for GitHub

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

Open
AleksandrSl wants to merge 2 commits into
base: development
Choose a base branch
from
Open

fix: declare lxml as a runtime dependency (v1.6.1) #84

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4a951dd
Delete issues-jira.yml
Aravind-Kumar-cstk Jun 30, 2026
4398221
fix: declare lxml as a runtime dependency (v1.6.1)
AleksandrSl Jul 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
118 changes: 0 additions & 118 deletions .github/workflows/issues-jira.yml
View file
Open in desktop

@AleksandrSl AleksandrSl Jul 9, 2026 •
edited
Loading

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The development branch is not up to the latest main, so this change is propagated, but is not mine

This file was deleted.

10 changes: 10 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,15 @@
# Changelog

## v1.6.1 (2026-07-09)

### Bug fix: Declare runtime dependency on lxml

- Added `lxml` to `install_requires` with environment markers: `>=6.1.0` on
Python 3.8+ (matching dev `requirements.txt`), `>=4.9.0,<5` on 3.6–3.7.
`contentstack_utils.utils` imports `lxml.etree` at module load time, but
previous releases shipped with an empty `install_requires`, so
`pip install contentstack-utils` did not install lxml.

## v1.6.0 (2026-06-22)

### New feature: Multi-region endpoint resolution
Expand Down
2 changes: 1 addition & 1 deletion contentstack_utils/__init__.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,6 @@
__title__ = 'contentstack_utils'
__author__ = 'contentstack'
__status__ = 'debug'
__version__ = '1.6.0'
__version__ = '1.6.1'

@AleksandrSl AleksandrSl Jul 9, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually I just though that patch version bump is not ideal, and major release is better, because thought people had to install lxml already they could install any version of it, since the library didn't restrict it. Now it's restricted, so people may get conflicts? Shouldn't be that bad, but I leave the decision on you

__endpoint__ = 'cdn.contentstack.io'
__contact__ = 'support@contentstack.com'
6 changes: 4 additions & 2 deletions setup.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,9 +34,11 @@ def run(self):
long_description_content_type="text/markdown",
url="https://github.com/contentstack/contentstack-utils-python",
license='MIT',
version='1.6.0',
version='1.6.1',
install_requires=[

# lxml 6.x requires Python 3.8+; keep 4.x for 3.6–3.7 (python_requires>=3.6).
"lxml>=4.9.0,<5; python_version<'3.8'",

@AleksandrSl AleksandrSl Jul 9, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It may make sense to drop support for python <3.9 already since even 3.10 is eol this October https://devguide.python.org/versions/
But that would be a major release

"lxml>=6.1.0; python_version>='3.8'",
],
setup_requires=['pytest-runner'],
tests_require=['pytest==4.4.1'],
Expand Down