Skip to content

Bump weasyprint from 66.0 to 67.0 in /backend-agent #168

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

Merged
marcorosa merged 1 commit into from
Dec 8, 2025
Merged

Bump weasyprint from 66.0 to 67.0 in /backend-agent #168

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion backend-agent/pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ dependencies = [
'art==6.5',
'pandas==2.3.3',
'ollama==0.6.1',
'weasyprint==66.0',
'weasyprint==67.0',
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot Dec 7, 2025

Choose a reason for hiding this comment

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

Consider using version ranges instead of pinned versions for better dependency flexibility and security updates. While pinned versions ensure reproducibility, they can prevent automatic security updates and make maintenance more difficult.

'weasyprint>=67.0,<68.0',

Alternatively, if you need exact versions for production stability, consider using a separate requirements-dev.txt or lock file approach where the pyproject.toml specifies ranges and a lock file pins exact versions.

'pyrit==0.9.0',
'codeattack @ git+https://github.com/marcorosa/CodeAttack',
'gptfuzzer @ git+https://github.com/marcorosa/GPTFuzz@no-vllm',
Comment on lines 35 to 36
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot Dec 7, 2025

Choose a reason for hiding this comment

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

The dependencies are using Git repositories with specific branches/commits. Consider:

  1. Version pinning: Pin to specific commit hashes for better reproducibility
  2. Documentation: Add comments explaining why these forks are needed
  3. Monitoring: Set up alerts for when upstream repositories are updated
# Using specific commit for reproducibility
'codeattack @ git+https://github.com/marcorosa/CodeAttack@abc123def456',
# Fork needed for vllm compatibility issues - see issue #123
'gptfuzzer @ git+https://github.com/marcorosa/GPTFuzz@def789abc012',

Expand Down
14 changes: 7 additions & 7 deletions backend-agent/uv.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.