Repository navigation
chore(deps): refresh the dependency locks - #321
Closed
github-actions[bot] wants to merge 1 commit into
Closed
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Owner
|
Not merging this bulk refresh: its browser tests fail (the Markdown table test no longer finds the 'Aspect' header cell), so one of the 113 upgraded packages changed behaviour. The four Dependabot advisories are fixed by a narrow update in a separate pull request instead. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Monthly dependency refresh, opened by the Dependency refresh workflow.
requirements.lock.txtandrequirements-dev.lock.txt:uv pip compile --upgradewithin the ranges inpyproject.tomlfrontend/package-lock.json:npm update --package-lock-onlywithin the ranges inpackage.jsonDeclared ranges were not changed. This pull request was opened with the workflow token, so the Quality workflow did not start on its own: close and reopen it, or push to the branch, to run the checks before merging.