Bump apache-log4j from 2.26.0 to 2.26.1

[dependabot]

Bumps apache-log4j from 2.26.0 to 2.26.1.
Updates org.apache.logging.log4j:log4j-api from 2.26.0 to 2.26.1

Updates org.apache.logging.log4j:log4j-core from 2.26.0 to 2.26.1

Updates org.apache.logging.log4j:log4j-layout-template-json from 2.26.0 to 2.26.1

Updates org.apache.logging.log4j:log4j-slf4j2-impl from 2.26.0 to 2.26.1

Updates org.apache.logging.log4j:log4j-web from 2.26.0 to 2.26.1

Updates org.apache.logging.log4j:log4j-1.2-api from 2.26.0 to 2.26.1

Dependabot 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[epugh]

@janhoy is this branch, main, not on the "clumping" routine of one big update per month?

[janhoy]

@janhoy is this branch, main, not on the "clumping" routine of one big update per month?

This is dependabot, not renovatebot. I think dependabot runs in a mode where it only bumps packages with known vulnerabilities in them, not any package with a newer version. So we could treat it as "more urgent" somehow? But I'd rather roll this feature into our solrbot - renovatebot has a feature where it can connect to dependency graph in github I think, but it is not setup.

[epugh]

@janhoy is this branch, main, not on the "clumping" routine of one big update per month?

This is dependabot, not renovatebot. I think dependabot runs in a mode where it only bumps packages with known vulnerabilities in them, not any package with a newer version. So we could treat it as "more urgent" somehow? But I'd rather roll this feature into our solrbot - renovatebot has a feature where it can connect to dependency graph in github I think, but it is not setup.

Yeah, I don't see value in this, I see another source of noise that will be ignored. Do we have to ahve dependabot? I would love to not see these and just see the same monthly updates.