Skip to content

chore: update lock file #95

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

Closed
wants to merge 3 commits into from
Closed

chore: update lock file #95

wants to merge 3 commits into from

Conversation

dolfim-ibm
Copy link
Contributor

@dolfim-ibm dolfim-ibm commented Apr 23, 2025

Updating the minimum Python version to match the cryptography requirements. See https://github.com/orgs/python-poetry/discussions/10199#discussioncomment-12247511

Checklist:

  • Documentation has been updated, if necessary.
  • Examples have been added, if necessary.
  • Tests have been added, if necessary.

Signed-off-by: Michele Dolfi <[email protected]>
Copy link

mergify bot commented Apr 23, 2025

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?(!)?:

@dolfim-ibm
Copy link
Contributor Author

Actually, the dependency tree of cryptography is coming from python-semantic-release which is a dev dependency. I think we should try to still keep python=^3.9 as main dependency and just trigger the correct pinning with dev and constraints.

@dolfim-ibm dolfim-ibm marked this pull request as draft April 23, 2025 10:48
@dolfim-ibm
Copy link
Contributor Author

Superseded by #108

@dolfim-ibm dolfim-ibm closed this May 28, 2025
@dolfim-ibm dolfim-ibm deleted the chore-update-lock branch May 28, 2025 11:58
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.

2 participants