Skip to content

Conversation

@cesarcoatl
Copy link
Member

@cesarcoatl cesarcoatl commented Sep 29, 2025

Summary by Sourcery

Lock ignition-api and ignition-api-stubs dependencies to versions >=8.1,<8.3 and update corresponding lockfiles and hashes

Enhancements:

  • Constrain ignition-api<8.3,>=8.1 in setup.py, pyproject.toml, and tox.ini

Build:

  • Regenerate requirements.txt files for both incendium and incendium-stubs with updated ignition-api and ignition-api-stubs versions and hashes

@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Sep 29, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR locks ignition-api and ignition-api-stubs to version 8.1.x by downgrading from 8.3.0, updating hash values in generated requirements, and adding an upper bound of <8.3 across pyproject.toml, setup.py, and tox.ini.

File-Level Changes

Change Details Files
Regenerated ignition-api-stubs lock to 8.1.49
  • Downgraded ignition-api-stubs from 8.3.0 to 8.1.49
  • Updated SHA256 hashes for the new version
incendium-stubs/requirements.txt
Regenerated ignition-api lock to 8.1.49
  • Downgraded ignition-api from 8.3.0 to 8.1.49
  • Updated SHA256 hashes for the new version
incendium/requirements.txt
Added upper version bound for ignition-api-stubs
  • Constrained ignition-api-stubs to <8.3,>=8.1 in project metadata
incendium-stubs/pyproject.toml
Added upper version bound for ignition-api
  • Constrained ignition-api to <8.3,>=8.1 in setup.py
incendium/setup.py
Added upper version bound for ignition-api-stubs in test config
  • Constrained ignition-api-stubs to <8.3,>=8.1 in tox.ini
incendium/tox.ini

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey there - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@cesarcoatl cesarcoatl merged commit f9c23eb into main Sep 29, 2025
9 checks passed
@cesarcoatl cesarcoatl deleted the chore/lock-requirements branch September 29, 2025 17:04
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