Repository navigation
chore(deps): bump lizard from 1.24.1 to 1.24.3 in /.github/impact-gate in the impact-gate-minor-patch group - #1464
Conversation
Bumps the impact-gate-minor-patch group in /.github/impact-gate with 1 update: [lizard](https://github.com/terryyin/lizard). Updates `lizard` from 1.24.1 to 1.24.3 - [Release notes](https://github.com/terryyin/lizard/releases) - [Changelog](https://github.com/terryyin/lizard/blob/master/CHANGELOG.md) - [Commits](terryyin/lizard@1.24.1...1.24.3) --- updated-dependencies: - dependency-name: lizard dependency-version: 1.24.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: impact-gate-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
Important Review skippedBot user detected. To trigger a single review, invoke the
 |
|
freshtonic
left a comment
freshtonic
left a comment
There was a problem hiding this comment.
Dependabot changed the lizard version to 1.24.3 but kept the 1.24.1 --hash lines. pip install --require-hashes refuses the wheel (Expected sha256 746060a3… Got f7fccd90…), so the Change impact job fails. This is the hash pin doing its job.
Regenerate the file with the command in its header, with lizard==1.24.3 in the printf line too (the header still says 1.24.1 there), and then restore the header. Before you commit the new hashes, check that f7fccd909719170e323a240cc6927bfea65984d77a8f9c0e6405be582e9861db is the sha256 that PyPI lists for lizard-1.24.3-py2.py3-none-any.whl.
…ve trigger Dependabot moved the lizard pin to 1.24.3 but kept the 1.24.1 hashes, so `pip install --require-hashes` refused the wheel. The new hashes are the ones PyPI lists for lizard-1.24.3 (wheel and sdist), from the command in the file's header, which now names 1.24.3 too. No other package moves. lizard 1.24.3 fixes the TypeScript misread the span tests used as their trigger (a ternary returning an object literal, lizard issue #523), so four tests failed: the fixture spans were read correctly. A `{` in a regex literal still makes 1.24.3 run a span on to the next `function`, over any top-level code between them. The four fixtures now use that trigger, and the driver comment names it.
Bumps the impact-gate-minor-patch group in /.github/impact-gate with 1 update: lizard.
Updates
lizardfrom 1.24.1 to 1.24.3Release notes
Sourced from lizard's releases.
Changelog
Sourced from lizard's changelog.
Commits
ba94d59Release 1.24.30012ca4Close balanced template scanning repair8c6d0c0End JavaScript template line comments at each line terminatorefcbdd7Restore balanced JavaScript template scanning37caa7fAdmit accepted work: SEED-009#balanced-template-scanning55c9c39Close SEED-008#review-issue-521123f6f3Admit accepted work: SEED-008#review-issue-5218149f77Close SEED-007#js-ts-function-boundariese17cb81Fix JS/TS function boundaries after return annotations and nested templatesfca7b1aPin CI Linux runner to Ubuntu 24.04 for Python 3.8Dependabot 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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions