Renovate: Update all non-major dependencies #54
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate-all-minor-patch"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
2.45.3-r0->2.45.4-r0v8.26.0->v8.28.04.2.0->4.3.0==6.0.2->==6.0.36.0.1->6.0.3Note: The
pre-commitmanager in Renovate is not supported by thepre-commitmaintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.Release Notes
gitleaks/gitleaks (gitleaks/gitleaks)
v8.28.0Compare Source
Changelog
4fb4382cant countb1c9c7eComposite rules (#1905)72977e4feat: add Anthropic API key detection (#1910)7b02c98fix(git): handle port (#1912)2a7bcffdont prematurely calculate fragment newlines (#1909)bd79c3efeat(allowlist): promote optimizations (#1908)7fb4edaFix: CVEs on go and go crypto (#1868)a044b81feat: add artifactory reference token and api key detection (#1906)bf380d4sillyf487f85Update gitleaks.yml958f55aadd just like that, no leaksOptimizations
#1909 waits to find newlines until a match. This ends up saving a boat load of time since before we were finding newlines for every fragment regardless if a rule matched or not.
#1908 promoted @rgmz excellent stopword optimization
Composite Rules (Multi-part or
requiredRules) #1905In v8.28.0 Gitleaks introduced composite rules, which are made up of a single "primary" rule and one or more auxiliary or
requiredrules. To create a composite rule, add a[[rules.required]]table to the primary rule specifying anidand optionallywithinLinesand/orwithinColumnsproximity constraints. A fragment is a chunk of content that Gitleaks processes at once (typically a file, part of a file, or git diff), and proximity matching instructs the primary rule to only report a finding if the auxiliaryrequiredrules also find matches within the specified area of the fragment.Proximity matching: Using the
withinLinesandwithinColumnsfields instructs the primary rule to only report a finding if the auxiliaryrequiredrules also find matches within the specified proximity. You can set:withinLines: N- required findings must be within N lines (vertically)withinColumns: N- required findings must be within N characters (horizontally)Here are diagrams illustrating each proximity behavior:
v8.27.2Compare Source
Changelog
c7acf33Merge branch 'master' of github.com:gitleaks/gitleaks9faaa4aAdd experimental allowlist optimizations (#1731)79068b3Detect Notion Public API Keys #1889 (#1890)v8.27.1Compare Source
Changelog
80468efMerge branch 'master' of github.com:gitleaks/gitleaksef82237fix(atlassian): reduce false-positives for v1 pattern (#1892)2463f11Fix log suppresion issue (#1887)6f251eeAdded Heroku API Key New Version (#1883)20f9a1dAdd Platform Bitbucket (#1886)722ce82Add Platform Gitea (#1884)79780b8Merge branch 'master' of github.com:gitleaks/gitleaksc5683caprevent default warn message when max-archive-depth not set (#1881)0357c3cprevent default warn message when max-archive-depth not setv8.27.0Compare Source
Changelog
782f310Archive support (#1872)489d13cUpdate README.mdd29ee55Reduce aws-access-token false positives (#1876)611db65Setpass_filenamestofalsefor Docker hook (#1850)0589ae0unicode decoding (#1854)82f7e32Diagnostics (#1856)f97a9eechore: include decoder in debug log (#1853)Got another @bplaxco release. Cheers!
Archive Scanning
Sometimes secrets are packaged within archive files like zip files or tarballs,
making them difficult to discover. Now you can tell gitleaks to automatically
extract and scan the contents of archives. The flag
--max-archive-depthenables this feature for both
dirandgitscan types. The default value of"0" means this feature is disabled by default.
Recursive scanning is supported since archives can also contain other archives.
The
--max-archive-depthflag sets the recursion limit. Recursion stops whenthere are no new archives to extract, so setting a very high max depth just
sets the potential to go that deep. It will only go as deep as it needs to.
The findings for secrets located within an archive will include the path to the
file inside the archive. Inner paths are separated with
!.Example finding (shortened for brevity):
This means a secret was detected on line 4 of
files/.env.prod.which is inarchives/files.tarwhich is intestdata/archives/nested.tar.gz.Currently supported formats:
The compression
and archive
formats supported by mholt's archives package
are supported.
pre-commit/pre-commit (pre-commit)
v4.3.0Compare Source
==================
Features
language: docker/language: docker_image: detect rootless docker.language: julia: avoidstartup.jlwhen executing hooks.language: dart: support latest dart versions which require a higher sdklower bound.
yaml/pyyaml (pyyaml)
v6.0.3Compare Source
What's Changed
Full Changelog: https://github.com/yaml/pyyaml/compare/6.0.2...6.0.3
woodpecker-plugins/docker-buildx (woodpeckerci/plugin-docker-buildx)
v6.0.3Compare Source
❤️ Thanks to all contributors! ❤️
@woodpecker-bot, @xoxys
📦️ Dependency
Misc
v6.0.2Compare Source
❤️ Thanks to all contributors! ❤️
@joeky888, @woodpecker-bot
📚 Documentation
📦️ Dependency
Misc
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.
Renovate: Update pre-commit hook gitleaks/gitleaks to v8.27.0to Renovate: Update pre-commit hook gitleaks/gitleaks to v8.27.2eca35a1874toa412ab1261Renovate: Update pre-commit hook gitleaks/gitleaks to v8.27.2to Renovate: Update all non-major dependenciesa412ab1261toed1a69508aed1a69508ato4e8f4ef2d74e8f4ef2d7toa6fea7b5ffa6fea7b5ffto2bfa83a4b22bfa83a4b2to8ebc2254328ebc225432tof0d8ab818aView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.