Bump weasyprint from 66.0 to 67.0 in /backend-agent #168
Conversation
Bumps [weasyprint](https://github.com/Kozea/WeasyPrint) from 66.0 to 67.0. - [Release notes](https://github.com/Kozea/WeasyPrint/releases) - [Changelog](https://github.com/Kozea/WeasyPrint/blob/main/docs/changelog.rst) - [Commits](Kozea/WeasyPrint@v66.0...v67.0) --- updated-dependencies: - dependency-name: weasyprint dependency-version: '67.0' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
backend
dependabot
bot
added
backend
|
The provided Walkthrough
Model: gpt-4o-2024-08-06 | Prompt Tokens: 318 | Completion Tokens: 136 |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Here's a supportive code review enhanced by AI assistance. These observations are suggestions and possibilities rather than definitive conclusions, so please take what resonates with your approach. You remain the expert decision-maker—AI simply offers additional perspective to complement your judgment.
Always critique what AI says. Do not let AI replace YOUR I.
Model: claude-sonnet-4-20250514 | Prompt Tokens: 868 | Completion Tokens: 436
| 'pandas==2.3.3', | ||
| 'ollama==0.6.1', | ||
| 'weasyprint==66.0', | ||
| 'weasyprint==67.0', |
There was a problem hiding this comment.
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.
| 'codeattack @ git+https://github.com/marcorosa/CodeAttack', | ||
| 'gptfuzzer @ git+https://github.com/marcorosa/GPTFuzz@no-vllm', |
There was a problem hiding this comment.
The dependencies are using Git repositories with specific branches/commits. Consider:
- Version pinning: Pin to specific commit hashes for better reproducibility
- Documentation: Add comments explaining why these forks are needed
- 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',
marcorosa
deleted the
dependabot/uv/backend-agent/develop/weasyprint-67.0
branch
1 participant
Bumps weasyprint from 66.0 to 67.0.
Release notes
Sourced from weasyprint's releases.
... (truncated)
Changelog
Sourced from weasyprint's changelog.
... (truncated)
Commits
94af598Version 67.04a682dbMerge pull request #2618 from different55/relative-flexgrid7639bfbUse the same code for all layouts to manage out-of-flow childrenc57a44eSupport the "x" resolution unitd004a3aCalculate relative offsets for grid and flex children.9cdbaf1Merge pull request #2599 from Kozea/split-gridd5230e1Take care of extra advancement when expanding to reach the bottom69c4848Simplify advancement calculus5566a7dFix last row detection for grid cells with span8cc2cbfOnly include children from skipped rows on broken gridsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)