<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  
  <title>Bill Seremetis, Blog</title>
  <subtitle>Notes on Drupal, DevOps and developer experience.</subtitle>
  <link href="https://bill.seremetis.net/blog/feed.xml" rel="self" />
  <link href="https://bill.seremetis.net/" />
  <updated>2026-11-04T00:00:00Z</updated>
  <id>https://bill.seremetis.net/</id>
  <author>
    <name>Bill Seremetis</name>
  </author>
  <entry>
    <title>Access log forensics with Claude Code</title>
    <link href="https://bill.seremetis.net/blog/access-log-forensics/" />
    <updated>2026-09-01T00:00:00Z</updated>
    <id>https://bill.seremetis.net/blog/access-log-forensics/</id>
    <content type="html">&lt;p&gt;Something is off with a site. It is slow, or it is throwing 503s, or someone
in a chat says &amp;quot;are we under attack?&amp;quot;. The answer is usually sitting in the
access log, somewhere between a few thousand and a few million lines.&lt;/p&gt;
&lt;p&gt;Reading it by hand means the usual dance: &lt;code&gt;awk&lt;/code&gt; for the top IPs, &lt;code&gt;sort | uniq -c&lt;/code&gt;
for the user agents, a dozen &lt;code&gt;grep&lt;/code&gt;s for the classic attack patterns, and then
squinting at all of it until a story appears. It works, but it is slow, and it
is exactly the kind of work you do not want to be doing while the site is down.&lt;/p&gt;
&lt;p&gt;So I packaged that dance into a
&lt;a href=&quot;https://github.com/bserem/access-log-forensics-skill&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Claude Code skill&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;What it does&lt;/h2&gt;
&lt;p&gt;Point it at a log in combined format:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;/access-log-forensics analyze /var/log/apache2/access.log
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Or just ask &amp;quot;can you check access.log for signs of an attack?&amp;quot; and Claude
picks it up on its own.&lt;/p&gt;
&lt;p&gt;The skill then:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Redacts the log.&lt;/strong&gt; Client IPs are replaced with stable pseudonyms
(&lt;code&gt;ip-042&lt;/code&gt;) before any log content enters the conversation.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Builds a baseline&lt;/strong&gt; with a bundled script: timeframe, status codes, top
IPs with error and URL counts, user agents, paths and requests-per-minute peaks.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sweeps for signatures:&lt;/strong&gt; SQL injection, path traversal, WordPress and
Drupal probing, secret hunting (&lt;code&gt;.env&lt;/code&gt;, &lt;code&gt;.git/&lt;/code&gt;), XSS and scanner user agents.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Applies judgement.&lt;/strong&gt; Raw counts are not findings. A distributed flood, a
scraper walking every URL, a brute force on &lt;code&gt;user/login&lt;/code&gt;, and the big one:
was an attack &lt;em&gt;attempted&lt;/em&gt;, or did it &lt;em&gt;succeed&lt;/em&gt;? A 404 is noise, a 200 with a
real response size is not.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Writes &lt;code&gt;forensics-report.md&lt;/code&gt;&lt;/strong&gt;, capped at one page and 400 words: a
verdict, key findings, notable sources and prioritized actions.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The word limit is on purpose. Nobody reads a ten-page report during an
incident. If the log shows nothing, the report says so in one paragraph and
does not invent findings.&lt;/p&gt;
&lt;h2&gt;Why the redaction&lt;/h2&gt;
&lt;p&gt;IP addresses in access logs are personal data under GDPR. Analyzing them for
security is perfectly legitimate, Recital 49 says so explicitly, but sending
raw logs to a cloud LLM turns the provider into a processor and, for US
processing, a third-country transfer. That is paperwork you do not want to
discover after the fact.&lt;/p&gt;
&lt;p&gt;Pseudonymizing first sidesteps most of it. The analysis works exactly the
same, &lt;code&gt;ip-042&lt;/code&gt; is as useful as the real address for spotting a pattern, and no
real IP leaves your machine. The mapping file stays local (&lt;code&gt;chmod 600&lt;/code&gt;), and
when you actually need to block someone you resolve the pseudonym yourself:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-bash&quot;&gt;grep -P &#39;&#92;tip-042$&#39; access.log.ipmap.tsv
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The README has a longer section on what is and is not fine under GDPR. It is
practical guidance, not legal advice, so involve your DPO if in doubt.&lt;/p&gt;
&lt;h2&gt;No magic required&lt;/h2&gt;
&lt;p&gt;The scripts only need &lt;code&gt;bash&lt;/code&gt;, &lt;code&gt;awk&lt;/code&gt;, &lt;code&gt;grep&lt;/code&gt;, &lt;code&gt;sort&lt;/code&gt; and &lt;code&gt;uniq&lt;/code&gt;. The baseline
script also runs on its own, without Claude:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-bash&quot;&gt;bash scripts/summarize.sh /path/to/access.log
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Install it by copying the folder into &lt;code&gt;.claude/skills/&lt;/code&gt; for one project, or
&lt;code&gt;~/.claude/skills/&lt;/code&gt; for all of them.&lt;/p&gt;
&lt;h2&gt;Resources&lt;/h2&gt;
&lt;p&gt;The skill, scripts and README are on
&lt;a href=&quot;https://github.com/bserem/access-log-forensics-skill&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;GitHub&lt;/a&gt;.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>Renovate for Drupal</title>
    <link href="https://bill.seremetis.net/blog/renovate-for-drupal/" />
    <updated>2026-11-04T00:00:00Z</updated>
    <id>https://bill.seremetis.net/blog/renovate-for-drupal/</id>
    <content type="html">&lt;p&gt;There was a time when keeping a Drupal site up to date meant checking the
&lt;a href=&quot;https://www.drupal.org/security&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;security advisories&lt;/a&gt; on Wednesday evening
to see if any were announced, running &lt;code&gt;composer update&lt;/code&gt; on the handful
of sites that needed it, and moving on.&lt;/p&gt;
&lt;p&gt;We would get Core security advisories every 2-4 months and contrib security
advisories that would actually affect sites (high usage modules) every couple
of months.&lt;/p&gt;
&lt;p&gt;That time is gone.&lt;/p&gt;
&lt;h2&gt;Every single week&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;FACT: Between March and September 2026, Drupal published 183 security advisories,
double the 92 of the same period in 2025. Core alone went from 1 advisory to 13.
From mid-May to the end of September, not a single week went by without one.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Every week now brings new security advisories, and lately they come by the dozen. Not because the code
got worse overnight, but because finding vulnerabilities got cheap, and fast.
AI-assisted tooling reads code faster and more patiently than any human reviewer,
and it is pointed at everything: core, contrib, the PHP libraries underneath, the
JavaScript on top. The people reporting issues use it. So do the people who do
not report them.&lt;/p&gt;
&lt;p&gt;The result is a steady stream of releases you actually need to ship, and a
window between &amp;quot;advisory published&amp;quot; and &amp;quot;exploit in the wild&amp;quot; that keeps
getting shorter.&lt;/p&gt;
&lt;p&gt;Contributed-project advisories in 2026 have reached 292 through October 28,
already the most of any year. The previous high was 175 in 2015.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://bill.seremetis.net/blog/renovate-for-drupal/renovate-for-drupal-contrib-advisories.png&quot; alt=&quot;The number of contributed project security advisories spiked from 113 in 2025 to 290 in 2026 so far.&quot;&gt;&lt;br&gt;
&lt;em&gt;Contributed-project advisories in 2026 (to 28 October).&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In just five months, from June through October 2026, Drupal published 256
security advisories. That five-month total exceeds the 250 advisories published
across the previous 30 months combined. This is the result of the
&lt;a href=&quot;https://www.drupal.org/association/blog/introducing-the-drupal-ai-security-initiative-the-first-six-weeks&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Drupal Security AI Initiative&lt;/a&gt;,
and by all means it is a good thing!&lt;/p&gt;
&lt;p&gt;Core shows a different picture. One could say there was a rise with Drupal 8
and 9 and a decline in Security Advisories when Core reached maturity levels,
&lt;em&gt;until the advent of AI agents.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://bill.seremetis.net/blog/renovate-for-drupal/renovate-for-drupal-core-advisories.png&quot; alt=&quot;Drupal Core advisories are currently sitting at 16 in 2026, up from 8 in 2025.&quot;&gt;&lt;br&gt;
&lt;em&gt;The number of Security Advisories for Drupal core from 2005 to 2026 (28 October).&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Updating all your projects by hand does not scale. One developer, one project,
one evening a week? Maybe.&lt;/p&gt;
&lt;p&gt;Twenty projects? What about more than 70, with different hosts, different
patches and different release cadences? You just can&#39;t keep up. Updates slip,
slipped updates pile up, and a pile of updates is exactly the kind of work
nobody wants to pick up on a Friday, and you can&#39;t wait until Monday anymore!
With vulnerabilities being actively exploited even before the fix is made you
just don&#39;t have that luxury.&lt;/p&gt;
&lt;p&gt;The answer to the problem isn&#39;t exactly a breakthrough: let a bot open the merge
requests, and let humans review them.&lt;/p&gt;
&lt;h2&gt;Why Renovate?&lt;/h2&gt;
&lt;p&gt;Renovate is an automated dependency update tool. We use it to check for Drupal
Core, contrib and private module updates, pack them and prepare Merge Requests
for our &lt;a href=&quot;https://www.annertech.com/support-and-optimisation&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Managed Services team&lt;/a&gt;
to test and rapidly deploy.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://docs.renovatebot.com/&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Renovate&lt;/a&gt; watches your dependency files, notices
new releases, and opens merge requests with the changes. It understands
Composer, runs on GitHub, GitLab, Bitbucket, Forgejo/Gitea and others, and can
be self-hosted. It also keeps a &lt;em&gt;dependency dashboard&lt;/em&gt; issue in each repo, so
you can see at a glance what is pending, what is blocked, and what was skipped.&lt;/p&gt;
&lt;p&gt;Out of the box it is a little too eager for Drupal. It took me weeks upon weeks to
come up with a sensible set of defaults. Below is the config I ended
up with for Annertech, after rolling it out across a set of Drupal projects, and the reasoning
behind each choice.&lt;/p&gt;
&lt;h2&gt;The config&lt;/h2&gt;
&lt;h3&gt;Centralised Config, Main Config&lt;/h3&gt;
&lt;p&gt;This is managed centrally and all projects inherit it and can extend it.
Rolling out a new version happens automatically to all projects.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/Annertech/renovate-configs&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;&lt;em&gt;You can find all config files and their latest versions in GitHub&lt;/em&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;default.json&lt;/code&gt;, publicly hosted:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-json&quot;&gt;{
    &amp;quot;description&amp;quot;: &amp;quot;Annertech shared Renovate preset for Drupal projects. Extend with local&amp;gt;anrt-tools/renovate&amp;quot;,
    &amp;quot;extends&amp;quot;: [&amp;quot;config:recommended&amp;quot;],
    &amp;quot;automerge&amp;quot;: false,
    &amp;quot;fetchChangeLogs&amp;quot;: &amp;quot;off&amp;quot;,
    &amp;quot;branchPrefix&amp;quot;: &amp;quot;renovate/&amp;quot;,
    &amp;quot;labels&amp;quot;: [&amp;quot;dependencies&amp;quot;],
    &amp;quot;rangeStrategy&amp;quot;: &amp;quot;update-lockfile&amp;quot;,
    &amp;quot;timezone&amp;quot;: &amp;quot;Etc/UTC&amp;quot;,
    &amp;quot;enabledManagers&amp;quot;: [&amp;quot;composer&amp;quot;],
    &amp;quot;prHeader&amp;quot;: &amp;quot;**Automated dependency update.** Please test on the dev site before merging and **check for configuration changes on production site.**&amp;quot;,
    &amp;quot;prConcurrentLimit&amp;quot;: 3,
    &amp;quot;prHourlyLimit&amp;quot;: 2,
    &amp;quot;major&amp;quot;: { &amp;quot;enabled&amp;quot;: false },
    &amp;quot;ignorePaths&amp;quot;: [
        &amp;quot;**/node_modules/**&amp;quot;,
        &amp;quot;**/bower_components/**&amp;quot;,
        &amp;quot;**/vendor/**&amp;quot;,
        &amp;quot;vendor/**&amp;quot;,
        &amp;quot;**/drush/**&amp;quot;,
        &amp;quot;drush/**&amp;quot;,
        &amp;quot;**/examples/**&amp;quot;,
        &amp;quot;**/__tests__/**&amp;quot;,
        &amp;quot;**/test/**&amp;quot;,
        &amp;quot;**/tests/**&amp;quot;,
        &amp;quot;**/__fixtures__/**&amp;quot;,
        &amp;quot;web/core/**&amp;quot;,
        &amp;quot;web/modules/contrib/**&amp;quot;,
        &amp;quot;web/themes/contrib/**&amp;quot;,
        &amp;quot;web/profiles/contrib/**&amp;quot;,
        &amp;quot;web/libraries/**&amp;quot;,
        &amp;quot;docroot/core/**&amp;quot;,
        &amp;quot;docroot/modules/contrib/**&amp;quot;,
        &amp;quot;docroot/themes/contrib/**&amp;quot;,
        &amp;quot;docroot/profiles/contrib/**&amp;quot;,
        &amp;quot;docroot/libraries/**&amp;quot;
    ],
    &amp;quot;postUpgradeTasks&amp;quot;: {
        &amp;quot;commands&amp;quot;: [&amp;quot;composer install --no-interaction --no-progress&amp;quot;],
        &amp;quot;fileFilters&amp;quot;: [
            &amp;quot;composer.json&amp;quot;,
            &amp;quot;composer.lock&amp;quot;,
            &amp;quot;composer-manifest.yaml&amp;quot;,
            &amp;quot;vendor/**&amp;quot;,
            &amp;quot;web/core/**&amp;quot;,
            &amp;quot;web/modules/contrib/**&amp;quot;,
            &amp;quot;web/themes/contrib/**&amp;quot;
        ],
        &amp;quot;executionMode&amp;quot;: &amp;quot;branch&amp;quot;
    },
    &amp;quot;packageRules&amp;quot;: [
        {
            &amp;quot;matchPackagePatterns&amp;quot;: [&amp;quot;.*&amp;quot;],
            &amp;quot;prBodyColumns&amp;quot;: [
                &amp;quot;Package&amp;quot;,
                &amp;quot;Update&amp;quot;,
                &amp;quot;Type&amp;quot;,
                &amp;quot;Change&amp;quot;
            ]
        },
        {
            &amp;quot;matchPackageNames&amp;quot;: [&amp;quot;php&amp;quot;],
            &amp;quot;enabled&amp;quot;: false
        },
        {
            &amp;quot;groupName&amp;quot;: &amp;quot;Drupal dependencies&amp;quot;,
            &amp;quot;groupSlug&amp;quot;: &amp;quot;drupal-deps&amp;quot;,
            &amp;quot;matchUpdateTypes&amp;quot;: [&amp;quot;minor&amp;quot;, &amp;quot;patch&amp;quot;]
        }
    ]
}
&lt;/code&gt;&lt;/pre&gt;
&lt;h3&gt;Per Project config&lt;/h3&gt;
&lt;p&gt;In the repository root add a &lt;code&gt;renovate.json&lt;/code&gt; file with a link to the above &lt;code&gt;default.json&lt;/code&gt;:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-json&quot;&gt;{
    &amp;quot;extends&amp;quot;: [&amp;quot;https://publicly.hosted/default.json&amp;quot;]
}
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;You can add more directives if you want, like:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-json&quot;&gt;    &amp;quot;assignees&amp;quot;: [&amp;quot;bserem&amp;quot;],
&lt;/code&gt;&lt;/pre&gt;
&lt;h2&gt;What it does, and why&lt;/h2&gt;
&lt;h3&gt;One merge request, not 40&lt;/h3&gt;
&lt;p&gt;All minor and patch updates, core and contrib, land in a single grouped merge
request (MR). Drupal projects have a lot of dependencies. One MR per package means
your merge request list becomes the new pile of work nobody wants to touch.
One combined MR is one review, one pipeline, one deploy.&lt;/p&gt;
&lt;h3&gt;Build artifacts stay consistent&lt;/h3&gt;
&lt;p&gt;Many Drupal projects commit &lt;code&gt;vendor/&lt;/code&gt; and the contrib code under &lt;code&gt;web/&lt;/code&gt;. Regardless
of how you feel about it, this keeps the project ready to deploy at all times,
minimizes deployment time and simplifies deployment pipelines (no build step).
It is quite neat for projects that have reached their adolescence and are not
undergoing rapid development.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;postUpgradeTasks&lt;/code&gt; does exactly that, runs real &lt;code&gt;composer install&lt;/code&gt; in the
codebase and then Renovate commits whatever composer wrote.&lt;/p&gt;
&lt;h4&gt;Don&#39;t want to commit contributed code? We&#39;ve got your back.&lt;/h4&gt;
&lt;p&gt;If you do not commit build artifacts, drop the &lt;code&gt;postUpgradeTasks&lt;/code&gt; block and let
the lock file be the only change.&lt;/p&gt;
&lt;p&gt;That is the lockfile-only setup, and it is simpler on every front. Each MR
contains a single changed file, &lt;code&gt;composer.lock&lt;/code&gt;, so reviews are short and easy to
read. Your pipeline runs &lt;code&gt;composer install&lt;/code&gt; at build time, which means the
lock file is the exact recipe for what ends up on the server. It also works on the
hosted Mend app, since there is no hook to skip. The only requirement is that
the runner can execute Composer, see below.&lt;/p&gt;
&lt;h3&gt;Majors stay with humans&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;major.enabled: false&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;A Drupal core major, a contrib 2.x to 3.x jump, a Symfony component major: these
need someone to read the release notes, check for deprecated APIs and run the
upgrade path. A bot should not be guessing.&lt;/p&gt;
&lt;p&gt;Anything outside Composer (npm, Docker images, CI templates) is off too, by
keeping &lt;code&gt;enabledManagers&lt;/code&gt; to &lt;code&gt;composer&lt;/code&gt;. Start narrow, widen later.&lt;/p&gt;
&lt;h3&gt;Nothing is automerged&lt;/h3&gt;
&lt;p&gt;Every MR gets a human review and a green pipeline before it lands. Renovate does
the tedious part, which is noticing and preparing. People do the part that needs
judgment.&lt;/p&gt;
&lt;p&gt;The idea is simple:
The dev wakes up in the morning, makes their coffee, opens their GitLab dashboards
and acts on them. Their job shifts from hammering &lt;code&gt;composer update&lt;/code&gt; commands to
reviewing Renovate&#39;s merge requests.&lt;/p&gt;
&lt;p&gt;Thanks to containerized environments every MR has an environment ready for
client QA too if deemed necessary.&lt;/p&gt;
&lt;p&gt;If a project has full test coverage then you will know in your pipeline if the
update is ready to merge without the need to self-test.&lt;/p&gt;
&lt;h3&gt;No grace period, on purpose&lt;/h3&gt;
&lt;p&gt;Renovate can hold back fresh releases with &lt;code&gt;minimumReleaseAge&lt;/code&gt;, which protects
you from the occasional broken release or compromised package. This also holds
back security releases, which is the exact opposite of what you want when an
advisory went out this morning.&lt;/p&gt;
&lt;p&gt;Right now security fixes arrive in the same MR as everything else, so fresh
beats delayed. Once security updates are handled on a separate track, adding a
grace period for regular updates becomes a sensible next step.&lt;/p&gt;
&lt;p&gt;I experimented a lot with having two different tracks, one for security and one
for everything else, but it quickly became painful. My tests coincided with
Symfony security updates and it was clear that under mixed circumstances you
can end up with composer (not renovate) refusing to update packages because
sub-dependencies were marked as insecure. One track for everything solves that.&lt;/p&gt;
&lt;h2&gt;Things to know up front&lt;/h2&gt;
&lt;h3&gt;You need a self-hosted runner for &lt;code&gt;postUpgradeTasks&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Running arbitrary commands is an admin-level setting. &lt;code&gt;composer install&lt;/code&gt; has to
be allow-listed on the runner, for example:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-bash&quot;&gt;RENOVATE_ALLOWED_COMMANDS=&#39;[&amp;quot;^composer install&amp;quot;]&#39;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;On the hosted Mend app the hook is silently skipped and you get MRs with a
stale &lt;code&gt;vendor/&lt;/code&gt;. If that is where you run Renovate, use a lock-file-only setup.&lt;/p&gt;
&lt;h3&gt;The runner needs PHP and Composer&lt;/h3&gt;
&lt;p&gt;With &lt;code&gt;update-lockfile&lt;/code&gt;, the only change is a regenerated &lt;code&gt;composer.lock&lt;/code&gt;. If
Composer cannot run, you get an MR with a nice description and no commits. Use
the full &lt;code&gt;renovate/renovate&lt;/code&gt; image (or &lt;code&gt;RENOVATE_BINARY_SOURCE=install&lt;/code&gt;), and
look for an &amp;quot;Artifact update problem&amp;quot; block in the MR body.&lt;/p&gt;
&lt;h3&gt;Validate before you ship config changes&lt;/h3&gt;
&lt;pre&gt;&lt;code class=&quot;language-bash&quot;&gt;npx --package renovate renovate-config-validator renovate.json
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;And do a local dry run against a real project before pushing it to a whole
fleet:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-bash&quot;&gt;LOG_LEVEL=debug GITHUB_COM_TOKEN=ghp_... &#92;
  npx renovate --platform=local --dry-run=full
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;em&gt;The GitHub token is only there so Renovate can read release notes without
hitting rate limits.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;What&#39;s next?&lt;/h2&gt;
&lt;p&gt;This setup is deliberately conservative. The obvious next steps are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A separate, faster track for security advisories, so you don&#39;t pack
regular updates on a security merge request&lt;/li&gt;
&lt;li&gt;A track for major updates, not necessarily in a ready to merge state, but
mostly as a visual representation of where things stand, to identify patches
that would become incompatible as other conflicts.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Conclusion&lt;/h2&gt;
&lt;p&gt;Security advisories are not going to slow down any time soon. As automated
tooling continues to uncover vulnerabilities at a rapid clip, relying on manual
maintenance schedules will only leave your sites exposed and your development
team overwhelmed.&lt;/p&gt;
&lt;p&gt;By putting Renovate to work, we have shifted the burden of dependency management
from human effort to automated pipelines. Instead of spending hours hunting down
updates and wrestling with Composer commands, our team can focus on what really
matters: reviewing clean, pre-made merge requests and keeping client sites
rock-solid.&lt;/p&gt;
&lt;p&gt;This conservative setup is just the beginning of our automated maintenance
journey. As we continue to refine our processes, the goal remains the same:
making sure that no matter how fast patch Wednesday arrives, applying updates
remains an easy part of our week.&lt;/p&gt;
&lt;h2&gt;Credits&lt;/h2&gt;
&lt;p&gt;It goes without saying that none of this would be possible without Mend Renovate
and the Drupal Security Team. It wouldn&#39;t be possible either without Annertech.&lt;/p&gt;
&lt;p&gt;This article was originally published on
&lt;a href=&quot;https://www.annertech.com/blog/how-we-use-renovate-automate-drupal-maintenance-and-keep-sites-secure&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Annertech&#39;s blog&lt;/a&gt;.&lt;/p&gt;
</content>
  </entry>
</feed>