# renovate

Renovate is an open-source tool for automating software dependency updates, including pull requests to update dependencies and lock files.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Manage Java transitive dependencies with Lightwell rebuilds

DevFeed: [Manage Java transitive dependencies with Lightwell rebuilds](<https://devfeed.tech/articles/manage-java-transitive-dependencies-with-lightwell-rebuilds-115668.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/03/manage-java-transitive-dependencies-lightwell-rebuilds>)

Author: Matej Marušák

Published: 2026-11-03T15:14:34Z

Content type: tutorial

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [ibm red hat project lightwell](<https://devfeed.tech/topics/ibm-red-hat-project-lightwell.md>), [software composition analysis](<https://devfeed.tech/topics/software-composition-analysis.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [renovate](<https://devfeed.tech/topics/renovate.md>), [Dependabot](<https://devfeed.tech/topics/dependabot.md>)

Tags: [automated](<https://devfeed.tech/tags/automated.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [behind-the-scenes](<https://devfeed.tech/tags/behind-the-scenes.md>), [but](<https://devfeed.tech/tags/but.md>), [challenge](<https://devfeed.tech/tags/challenge.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [developer](<https://devfeed.tech/tags/developer.md>), [development](<https://devfeed.tech/tags/development.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [first](<https://devfeed.tech/tags/first.md>), [java](<https://devfeed.tech/tags/java.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [lightwell](<https://devfeed.tech/tags/lightwell.md>), [manager](<https://devfeed.tech/tags/manager.md>), [nested](<https://devfeed.tech/tags/nested.md>), [package](<https://devfeed.tech/tags/package.md>), [packages](<https://devfeed.tech/tags/packages.md>), [rebuilds](<https://devfeed.tech/tags/rebuilds.md>), [security](<https://devfeed.tech/tags/security.md>), [transitive-dependencies](<https://devfeed.tech/tags/transitive-dependencies.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Java's pinned Maven and Gradle versions make it difficult for direct-dependency update tools such as Renovate or Dependabot to remediate vulnerabilities deep in transitive trees. The article describes three ways to use Lightwell's security-focused Java rebuilds: select packages manually from its catalog or API for granular control, with poor scalability; analyze the full dependency tree and review a report of matching rebuilds, then copy coordinates into pom.xml; or generate a BOM that pins matching rebuilds for auditability and version control, at the cost of continuous pipeline runs and BOM maintenance. The example pin-transitives.mjs script is only a starting point and lacks advanced filtering and CVE tracking. The article discourages opaque proxy-based substitutions because they can make builds nonreproducible and unverifiable; visible Maven relocations still warrant caution.

### Source excerpt

Updating direct dependencies in Java is straightforward, but securing the hundreds of transitive libraries running beneath them is where many development pipelines stall. While automated tools simplify how teams upgrade direct dependencies--the packages your project explicitly declares--the Java ecosystem presents a challenge: pinned versions and deeply nested trees of transitive dependencies. Transitive dependencies are the libraries your direct dependencies rely on behind the scenes, which your package manager pulls in automatically. The post Manage Java transitive dependencies with Lightwell rebuilds appeared first on Red Hat Developer.

## Thirteen backlogs in a trenchcoat: Analysing Renovate's many requests

DevFeed: [Thirteen backlogs in a trenchcoat: Analysing Renovate's many requests](<https://devfeed.tech/articles/thirteen-backlogs-in-a-trenchcoat-analysing-renovate-s-many-requests-109802.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/10/30/renovate-buckets/>)

Author: Jamie Tanna

Published: 2026-10-30T17:45:56Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [renovate](<https://devfeed.tech/topics/renovate.md>), [open source maintenance](<https://devfeed.tech/topics/open-source-maintenance.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [request management](<https://devfeed.tech/topics/request-management.md>), [issue tracking](<https://devfeed.tech/topics/issue-tracking.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [2019](<https://devfeed.tech/tags/2019.md>), [agile](<https://devfeed.tech/tags/agile.md>), [ai](<https://devfeed.tech/tags/ai.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [contribution](<https://devfeed.tech/tags/contribution.md>), [contributions](<https://devfeed.tech/tags/contributions.md>), [cycle-time](<https://devfeed.tech/tags/cycle-time.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [features](<https://devfeed.tech/tags/features.md>), [lead](<https://devfeed.tech/tags/lead.md>), [llm](<https://devfeed.tech/tags/llm.md>), [mend](<https://devfeed.tech/tags/mend.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [process](<https://devfeed.tech/tags/process.md>), [product](<https://devfeed.tech/tags/product.md>), [project](<https://devfeed.tech/tags/project.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [sources](<https://devfeed.tech/tags/sources.md>), [story](<https://devfeed.tech/tags/story.md>)

### AI overview

Renovate's large workload comprises 13 distinct backlogs, so its maintainers plan to use clearer categories to prioritize incoming work. They classified requests by areas such as ecosystem support, workflow fit, bugs, security, performance, documentation, and dependency updates, alongside cross-cutting labels for rough edges, audience, and customer interest. The analysis found strong user demand for deeper ecosystem integrations and workflow fit, more community bug-fix contributions, and rising supply-chain-security requests. Community PRs have grown, with self-reported figures suggesting much of the recent increase involved substantive AI use; review response times have also slowed as the small team handles more work. Going forward, the project expects to favor reproducible bugs, rough edges, and customer requests, while acknowledging that its prioritization approach is still being refined.

### Source excerpt

🤖 This post includes some LLM-derived content 🤖 In 2019, I saw a talk called Building and Growing an Agile Team by Tom Hoyland, which has probably been one of the most impactful talks I've attended in my career. In the talk, Tom talks about how he worked with a team to build them into a high-performing team, which, among other things, involved measuring things like "cycle time", improving the way the team's deployment process worked by doing it for every story, and by discovering the sources of work coming into the team. In the latter case, by understanding the sources of work the team was being given, the team could then have full visibility into their different backlogs, which had always been present, but maybe not clearly thought of as a backlog, and make better choices going forwards. This is something that I've internalised quite deeply over the years, and have used to build teams that enjoyed working together across several companies. Most recently, this talk has come up as I've been thinking about how the Renovate project has quite a large backlog of work, in part due to increased contribution over the last ~18 months due to AI. As the Project Lead, I've been thinking about how we can approach this better in the future, and decided that one step towards this is to map out the different "backlogs" that we have as a project. This exercise will help us understand more generally what sources of work we have to help us better prioritise the existing backlog alongside new requests that come in. A brief summary of the project For those that don't know, Renovate is the excellent dependency update tool that's always been Open Source and very much open to contributions + extensions. I've been an avid user for years, and prior to joining Mend to work on Renovate last year, I'd been waxing lyrical about Why I recommend Renovate over any other dependency update tools which holds true to today - or maybe even more so, given the features we've been shipping ever since. Reno

## Security updates for Thursday

DevFeed: [Security updates for Thursday](<https://devfeed.tech/articles/security-updates-for-thursday-63127.md>)

Original publisher: [Read original article](<https://lwn.net/Articles/1098067/>)

Author: jzb

Published: 2026-10-01T13:12:52Z

Content type: news

Language: en

Sources: [LWN.net](<https://devfeed.tech/sources/lwn-net.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Firefox](<https://devfeed.tech/topics/firefox.md>), [Django](<https://devfeed.tech/topics/django.md>), [Composer](<https://devfeed.tech/topics/composer.md>), [Fable](<https://devfeed.tech/topics/fable.md>), [renovate](<https://devfeed.tech/topics/renovate.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [coding](<https://devfeed.tech/tags/coding.md>), [debian](<https://devfeed.tech/tags/debian.md>), [django](<https://devfeed.tech/tags/django.md>), [fedora](<https://devfeed.tech/tags/fedora.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [gdb](<https://devfeed.tech/tags/gdb.md>), [mozilla-thunderbird](<https://devfeed.tech/tags/mozilla-thunderbird.md>), [nodejs](<https://devfeed.tech/tags/nodejs.md>), [openvpn](<https://devfeed.tech/tags/openvpn.md>), [perl](<https://devfeed.tech/tags/perl.md>), [python](<https://devfeed.tech/tags/python.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [ruff](<https://devfeed.tech/tags/ruff.md>), [rust](<https://devfeed.tech/tags/rust.md>), [security](<https://devfeed.tech/tags/security.md>), [security-updates](<https://devfeed.tech/tags/security-updates.md>), [suse](<https://devfeed.tech/tags/suse.md>), [tegra](<https://devfeed.tech/tags/tegra.md>), [updates](<https://devfeed.tech/tags/updates.md>), [uv](<https://devfeed.tech/tags/uv.md>)

### AI overview

Security updates were issued by AlmaLinux, Debian, Fedora, Mageia, Red Hat, Slackware, SUSE, and Ubuntu for a range of packages, including browsers, development tools, libraries, and system components.

### Source excerpt

Security updates have been issued by AlmaLinux (corosync, gawk, gdb, nodejs24, and thunderbird), Debian (expat, firefox-esr, libsmpp34, mkvtoolnix, network-manager-l2tp, pgextwlist, python-django, ruby-oj, and tor), Fedora (apptainer, ckermit, ffmpeg, freerdp, librabbitmq, openbao, php, python-cssselect2, python-uv-build, ruff, rust-libcst, rust-libcst_derive, rust-salsa, rust-salsa-macro-rules, rust-salsa-macros, sos, ty, uv, weasyprint, and xdg-dbus-proxy), Mageia (python-pillow), Red Hat (acl, glib2, go-toolset:rhel8, golang, libxml2, mingw-sqlite, nodejs-nodemon, nodejs22, nodejs24, nodejs:22, nodejs:24, sqlite, tesseract, and vim), Slackware (libpng and mozilla-thunderbird), SUSE (alloy, chromedriver, emacs, gdb, gimp, gpsd, jawn, libpoppler-cpp3, libtesseract5, multipath-tools, netty, ntfs-3g_ntfsprogs, pcapplusplus-devel, pi-coding-agent, python-PyYAML, python-tornado, python-tornado6, python311, python313, and wicked2nm), and Ubuntu (designate, gst-plugins-bad1.0, gvfs, imagemagick, kdenlive, mlt, keystone, libauthen-sasl-perl, linux-aws, linux-aws-6.8, linux-nvidia-tegra, linux-nvidia-tegra-igx, linux-oracle-7.0, opensbi, openvpn, and python-django).

## Looking back at my first year as the Renovate Project Lead

DevFeed: [Looking back at my first year as the Renovate Project Lead](<https://devfeed.tech/articles/looking-back-at-my-first-year-as-the-renovate-project-lead-57514.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/09/21/renovate-1-year/>)

Author: Jamie Tanna

Published: 2026-09-21T15:58:39Z

Content type: opinion

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [renovate](<https://devfeed.tech/topics/renovate.md>), [Maintainers](<https://devfeed.tech/topics/maintainers.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Security](<https://devfeed.tech/topics/security.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [Claude](<https://devfeed.tech/topics/claude.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [charts](<https://devfeed.tech/tags/charts.md>), [claude](<https://devfeed.tech/tags/claude.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [lead](<https://devfeed.tech/tags/lead.md>), [llm](<https://devfeed.tech/tags/llm.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [security](<https://devfeed.tech/tags/security.md>), [security-vulnerabilities](<https://devfeed.tech/tags/security-vulnerabilities.md>), [supply-chain-attacks](<https://devfeed.tech/tags/supply-chain-attacks.md>)

### AI overview

A Renovate project lead reflects on a year working full-time on the project, combining a personal performance review with observations about changes in the software industry and Open Source ecosystem. The post discusses supply chain attacks, AI-generated contributions and security reports, dependency update tools, maintainer workload, and analysis produced with Claude Opus 5 and project data.

### Source excerpt

🤖 This post includes some LLM-derived content 🤖 A year ago on Thursday, I logged on for my first day joining Mend to work on Renovate full-time. Similar to what I did after my first 100 days, I thought now would be a good time to recap how this last year has gone. This is also a fun way of doing a public mini performance review! I'd planned to try and land this on my actual anniversary, but I know this is going to be a busy week - as they all seem to be, nowadays - so thought I'd pre-publish it (and because I don't like waiting to hit publish). Plus, publishing this now means that I don't have to keep re-writing this as the stats change! Note that below includes analysis from Claude Opus 5, based on data from our "maintainer dashboard" and commits on main over the last year. I've done some double-checking of some of these stats. Claude Opus 5 has created each of the charts on this page. I've got a really great team behind me on the project, so I'm not attempting to completely claim credit for everything - thanks for all you do! Changes in the industry Before I get into how things have gone with the Renovate project, I wanted to look at the wider industry's context. In the last year, we've seen: a significant rise in supply chain attacks, where malicious package releases are being used to compromise others and continue propagation as a worm (such as the "Shai Hulud"/"Sha1 Hulud"), or purely used to target specific users and organisations an overwhelming increase of contributions across the Open Source ecosystem using AI, swamping and burning out maintainers faster than ever a similar increase in reports of privately reported security vulnerabilities in code, with a high percentage of these being bogus (as far as I can tell) higher adoption in dependency update tools, while also seeing calls to disable (your dependency update tools) or to prune the dependencies you own I have a lot of thoughts on this, and had hoped to do a conference talk about this, but the talk pro

## Updating \`apk add\` and \`apt install\` definitions in Dockerfiles with Renovate

DevFeed: [Updating \`apk add\` and \`apt install\` definitions in Dockerfiles with Renovate](<https://devfeed.tech/articles/updating-apk-add-and-apt-install-definitions-in-dockerfiles-with-renovate-53102.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/09/18/renovate-regex-dockerfile-apk/>)

Author: Jamie Tanna

Published: 2026-09-18T17:30:05Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [renovate](<https://devfeed.tech/topics/renovate.md>), [APK](<https://devfeed.tech/topics/apk.md>), [apt](<https://devfeed.tech/topics/apt.md>), [Package Management](<https://devfeed.tech/topics/package-management.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>)

Tags: [apk](<https://devfeed.tech/tags/apk.md>), [apt](<https://devfeed.tech/tags/apt.md>), [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [chainguard](<https://devfeed.tech/tags/chainguard.md>), [chainguard-images](<https://devfeed.tech/tags/chainguard-images.md>), [dockerfiles](<https://devfeed.tech/tags/dockerfiles.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>)

### AI overview

This article explains how Renovate now natively updates pinned packages installed with apk add, apt install, and apt-get install in Dockerfiles. It discusses reproducible builds, support for Wolfi and Chainguard Images, and the temporary need to configure registry URLs explicitly.

### Source excerpt

If you're writing Dockerfiles that install packages using system package managers, such as apk or apt, you might be pinning your versions of packages, to make sure that you have more reproducible builds, or if you're on a rolling release distribution like Wolfi and Chainguard Images, you want to make sure you only get package versions you want. When these system package manager versions are pinned, it can then be a little cumbersome to keep them updated in an automated fashion, as most tools don't have a way to automagically parse your files and propose updates. So you're probably one one of two camps - "I'll get my AI agent to go and update it for me" or "we'll not update anything until things break". I've previously had this managed - at least for apk add updates - by using a Custom Regex Manager with Renovate to keep them updated, which required you break the install command over multiple lines: # ... RUN apk upgrade --no-cache && \ apk add --no-cache \ bash=5.2.37-r2 \ py3-pip \ python3 \ rsyslog=8.2412.0-r1 \ runit=2.2.0 ENV APP_HOST=0.0.0.0 ENV app_port=5000 ENV SNAPP_PORT 5000 This isn't that much of a problem - as it also improves readability - but you generally want the tools to work around you, not vice versa. As of earlier this morning, we've shipped inbuilt support in Renovate, so if you have a Dockerfile with apk add, or an apt install (or apt-get install) like below, you'll be able to receive package updates for them 🎉 For instance, with the following Dockerfile: # SPDX-License-Identifier: AGPL-3.0-only # Via https://docs.renovatebot.com/modules/manager/dockerfile/#run-apt-install-support FROM debian:trixie RUN apt-get update \ && apt-get install -y --no-install-recommends \ # newlines for readability only curl=8.14.1-2 \ git=1:2.47.3-0+deb13u1 \ && rm -rf /var/lib/apt/lists/* Renovate will detect that you have a package pin for curl and git, and if there are updates available, will propose them. Right now, we don't currently auto-detect the distributi

## Dependabot vs Renovate

DevFeed: [Dependabot vs Renovate](<https://devfeed.tech/articles/dependabot-vs-renovate-51622.md>)

Original publisher: [Read original article](<https://www.aikido.dev/blog/dependabot-vs-renovate>)

Author: Nicholas Thomson

Published: 2026-09-14T15:56:00Z

Content type: comparison

Language: en

Sources: [Aikido Security's Blog](<https://devfeed.tech/sources/aikido-security-s-blog.md>)

Topics: [Dependabot](<https://devfeed.tech/topics/dependabot.md>), [renovate](<https://devfeed.tech/topics/renovate.md>), [Security](<https://devfeed.tech/topics/security.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [monorepo](<https://devfeed.tech/topics/monorepo.md>), [open-source-security](<https://devfeed.tech/topics/open-source-security.md>)

Tags: [dependabot](<https://devfeed.tech/tags/dependabot.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [github](<https://devfeed.tech/tags/github.md>), [monorepo](<https://devfeed.tech/tags/monorepo.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [sast](<https://devfeed.tech/tags/sast.md>), [sca](<https://devfeed.tech/tags/sca.md>), [secrets-detection](<https://devfeed.tech/tags/secrets-detection.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

A comparison of Dependabot and Renovate covering setup, GitHub integration, monorepo support, platform reach, and security handling. It argues that automatic dependency updates can cause breaking changes or introduce vulnerabilities, and discusses reachability analysis and patching as alternatives.

### Source excerpt

Dependabot vs Renovate compared on setup, monorepos, platforms, and security, plus why auto-updating misses what's actually exploitable Category: DevSec Tools & Comparisons

## Performing per-environment staged rollouts of dependency updates with Renovate

DevFeed: [Performing per-environment staged rollouts of dependency updates with Renovate](<https://devfeed.tech/articles/performing-per-environment-staged-rollouts-of-dependency-updates-with-renovate-53101.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/09/08/renovate-staged-branches/>)

Author: Jamie Tanna

Published: 2026-09-08T22:00:11Z

Content type: tutorial

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [renovate](<https://devfeed.tech/topics/renovate.md>), [GitOps](<https://devfeed.tech/topics/gitops.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [forgejo](<https://devfeed.tech/topics/forgejo.md>), [nginx](<https://devfeed.tech/topics/nginx.md>)

Tags: [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [forgejo](<https://devfeed.tech/tags/forgejo.md>), [gitops](<https://devfeed.tech/tags/gitops.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [review](<https://devfeed.tech/tags/review.md>), [updates](<https://devfeed.tech/tags/updates.md>)

### AI overview

This tutorial explains how to use Renovate to stage dependency updates across environment branches such as dev, staging, and production. It covers base branch patterns and custom datasources and managers that keep versions aligned as updates are promoted.

### Source excerpt

🤖 This post includes some LLM-derived content 🤖 In a lot of organisations, you'll find a fairly consistent structure in teams' (GitOps) repositories, where they set up a branch per deployable environment, such as: * dev * staging * prod Within this structure, the approach for releasing upgrades would be to stage/promote upgrades through environments, starting with dev, through staging and up to prod. If you're using Renovate - which I have been recommending long before it became my job - you can handle this same workflow very nicely. Today, I learned a new couple of tricks to make this work even nicer from Renovate maintainer Michael Kriese, who's been working on this setup upstream with the Forgejo maintainers, where it's been working very well for the team. Prerequisites As a starting point, you would want to set up your repository with baseBranchPatterns to make Renovate manage each of the branches you use, i.e. { "$schema": "https://docs.renovatebot.com/renovate-schema.json", "baseBranchPatterns": ["$default", "dev", "staging", "prod"] } When you specify baseBranchPatterns, you'll start seeing that PRs raised by Renovate are i.e. titled chore(deps): update nginx docker tag to v1.27.3 (dev), which makes it easier to know which of your PRs are for which environment. This minimal config actually gets you quite far towards this setup, and you could probably stop here. But one thing you'll find is that - depending on how long your release pipelines take - in the time it takes for you to release a PR to dev and staging, when it comes to the release to prod, there may now be a new version of the dependency available. This is more of an issue with fast releasing packages - like with Renovate itself - but happens often enough that it can scupper your plans, as you go to review the PR for prod, and the PR updates to the new version, which restarts the release-and-testing flow. Ensuring that these versions can only be rolled out in a specific order is the key problem we're

## Week Notes 26#36

DevFeed: [Week Notes 26#36](<https://devfeed.tech/articles/week-notes-26-36-53149.md>)

Original publisher: [Read original article](<https://www.jvt.me/week-notes/2026/36/>)

Author: Jamie Tanna

Published: 2026-09-06T20:26:34Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [software-development](<https://devfeed.tech/topics/software-development.md>), [releases](<https://devfeed.tech/topics/releases.md>), [APK](<https://devfeed.tech/topics/apk.md>), [renovate](<https://devfeed.tech/topics/renovate.md>), [Website](<https://devfeed.tech/topics/website.md>), [CSS](<https://devfeed.tech/topics/css.md>)

Tags: [apk](<https://devfeed.tech/tags/apk.md>), [css](<https://devfeed.tech/tags/css.md>), [notes](<https://devfeed.tech/tags/notes.md>), [releases](<https://devfeed.tech/tags/releases.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [website](<https://devfeed.tech/tags/website.md>), [week-notes](<https://devfeed.tech/tags/week-notes.md>)

### AI overview

Personal week notes covering software work on Dev Platform releases, the APK datasource, and a planned Renovate feature, alongside personal activities, games, reading, and television.

### Source excerpt

A busy 4 day week On Monday, we had a chill bank holiday with a nice lunch at Mowgli It's been a very busy work week Thursday was releasing a few big bits, and a number of releases to Dev Platform as we closed off different pieces On Friday, with the APK Datasource available, I spent some time looking into solving a much-wanted feature of mine, where Renovate will automagically parse apk adds Was nice to catch up with Rhys after a bit, and then a good catch-up with Michael and Sebastian It's also been nice starting to onboard Michael Had a nice time at Lanzhou Noodles Had a nice chill pizza night just Carol, Chris and I It's also very nice to have Rakki Rakkas back 😋 Mezza is now officially closed - after a bit of limbo and uncertainty for a few months - but at least now we know We dog sat Stan this weekend - he's a little cutie, but it is interesting how much extra work it is having a second one running around 🐶 Morph was happy to be home and has been very meow meow Thinking about completely stripping back my website's CSS to something more simple (maybe even classless.de based) Had a nice walk with Carol and Alan today Cookie's been enjoying chilling in my office this week I got a much needed haircut this week, and feeling a lot better (and less top-heavy) Playing: Blue Prince Another good recommendation from Carol - very much enjoying it (only on day 8 so far) But this weekend I've been too tired to play, not thinking my sleep-lacking brain would be up to it (and a waste of enjoyment) On Wednesday night, I was playing a bit too late, so I had a very busy brain, and overnight my mind was working through some of the puzzles in the night Kingshot (per usual) Managed to trade ~300 stamina hams for >8 days of speedups, which was worth the trade ahead of KvK this week Apex Legends Reading: Leviathan Falls The Sins of Our Fathers Watched: (No Veep (Season 7)) We're not sure if we will finish it in the end Reacher (Season 4) Jeeves and Wooster (Series 3) Margo's Got Mone

## Week Notes 26#35

DevFeed: [Week Notes 26#35](<https://devfeed.tech/articles/week-notes-26-35-53148.md>)

Original publisher: [Read original article](<https://www.jvt.me/week-notes/2026/35/>)

Author: Jamie Tanna

Published: 2026-08-30T21:11:50Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [GitHub](<https://devfeed.tech/topics/github.md>), [renovate](<https://devfeed.tech/topics/renovate.md>)

Tags: [github](<https://devfeed.tech/tags/github.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [week-notes](<https://devfeed.tech/tags/week-notes.md>), [work](<https://devfeed.tech/tags/work.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

Personal week notes covering work on Renovate advisories, GitHub Stacked PRs and Merge Queues, website updates, a Micropub rewrite, and other personal activities.

### Source excerpt

A busy week at work, publishing 10 advisories for Renovate, and working on a number of other bits As GitHub Stacked PRs now support Merge Queues, I've been using them a fair bit this week, mostly simplifying a number of things And it'll be interesting to see how this will help with our next major release Also a very rainy week. A particularly big thunderstorm on Monday led to Morph coming upstairs too - he felt a lot safer, which is good, and Cookie was good with him, but he kept also jumping onto bed and meowing loudly in our faces 🫣 Alexa has been randomly playing music which has been weird - I noticed it a couple of times - one in the evening and one overnight 🤔 Given Elastic's stock has been doing well (highest for at least a year), I decided to sell the majority of my shares to get some money back, as I'm not certain they'll be getting any higher any time soon It was funny that after each time I sold stock, there was a bit of a dip in the market's view and the share price dropped I do wonder if I have the power to manipulate the markets and want to test it again 😹 On my website, made a few tweaks to styles, and added a page to list my published advisories Had a nice pizza night at Pizza Pilgrims Some twats are setting off fireworks right now, even though it's torrential rain right now, and they shouldn't be anyway, given the risk of wildfires Wrote about my workflow with tuicr Some interesting chatter on the Tech Nottingham Slack this week (quite meta, like, the Tech Nottingham Slack) Cookie got her claws trimmed at the vets and was very good about it, and they managed to really get on top of them! Spent the weekend doing some sorting out of finances, and getting mostly ready for tax return season Cookie enjoyed sleeping very comfortably with her head on a pillow I put down for her 🥰 Had a nice walk at Blidworth today with Carol and Alan Most of the way through finalising my Micropub rewrite 🤞🏼 The Tyrant event in Kingshot was a bit meh Reading: Leviathan Falls

## Should You Update an Existing Page or Publish a New One?

DevFeed: [Should You Update an Existing Page or Publish a New One?](<https://devfeed.tech/articles/should-you-update-an-existing-page-or-publish-a-new-one-87476.md>)

Original publisher: [Read original article](<https://prerenderbuddy.com/blog/update-existing-page-or-create-new>)

Author: Prerender Buddy

Published: 2026-08-26T00:00:00Z

Content type: article

Language: en

Sources: [Prerender Buddy](<https://devfeed.tech/sources/prerender-buddy-blog.md>)

Topics: [renovate](<https://devfeed.tech/topics/renovate.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>)

Tags: [content-strategy](<https://devfeed.tech/tags/content-strategy.md>)

### AI overview

The article presents a framework for deciding whether an AI visibility or content gap calls for updating an existing page, creating a distinct page, consolidating overlapping pages, or fixing technical delivery. It recommends starting from the audience's decision, checking page intent and technical health, and requiring evidence and a clear purpose before publication.

### Source excerpt

Use prompt intent, existing-page fit, overlap and evidence to decide whether an AI visibility gap needs an update, a new page or consolidation.

## Announcing some improvements to \`renovate-pretty-log-tui\`

DevFeed: [Announcing some improvements to \`renovate-pretty-log-tui\`](<https://devfeed.tech/articles/announcing-some-improvements-to-renovate-pretty-log-tui-53094.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/08/17/renovate-pretty-log/>)

Author: Jamie Tanna

Published: 2026-08-17T20:47:36Z

Content type: release

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [renovate](<https://devfeed.tech/topics/renovate.md>), [Text-based user interface](<https://devfeed.tech/topics/tui.md>), [releases](<https://devfeed.tech/topics/releases.md>), [debugging](<https://devfeed.tech/topics/debugging.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>), [Fable](<https://devfeed.tech/topics/fable.md>), [HTML](<https://devfeed.tech/topics/html.md>), [browser](<https://devfeed.tech/topics/browser.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [file](<https://devfeed.tech/topics/file.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [claude](<https://devfeed.tech/tags/claude.md>), [debug](<https://devfeed.tech/tags/debug.md>), [fable](<https://devfeed.tech/tags/fable.md>), [github](<https://devfeed.tech/tags/github.md>), [html](<https://devfeed.tech/tags/html.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [release](<https://devfeed.tech/tags/release.md>), [release-notes](<https://devfeed.tech/tags/release-notes.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [ux](<https://devfeed.tech/tags/ux.md>)

### AI overview

An update to renovate-pretty-log-tui and related utilities improves the experience of viewing Renovate debug logs. Version 0.6.0 adds a summary view, clearer error presentation, better support for smaller displays, and an option to export logs as a self-contained HTML page.

### Source excerpt

As I've blogged about before, I've written a tool for improving the experience of working with Renovate's debug logs, providing a more targeted experience for viewing the logs. While there are a few options out there at the moment, including part of our products at Mend, it's also nice having an agnostic tool I can use across different products, or where a customer or a user has provided logs to us. Last week, I finally sat down to listing out some of the key improvements I'd like to have completed on renovate-pretty-log-tui. As I'm not that familiar with Bubble Tea, which it's based on, I decided to set Claude Opus and Claude Fable on the work, as well as seeing if they could see any additional improvements. I've just shipped v0.6.0 of my renovate-pretty-log-tui and renovate-pretty-log utilities, including a whole host of changes - check out the release notes for more. Some of the key changes can be seen in this Asciicast: As you can see, there's now a summary view, and an improved UX for viewing the logs. I'm still working on how this works on smaller screens (i.e. in a Tmux pane) but it works nicely when it's rendered on a half-screen window size. In this, we also surface errors more clearly, i.e. Although I'd mostly completed this last week, I needed to put the last touches to the commit messages. With the GitHub outage today, I decided to finish getting these changes complete, as they've very useful for working with debug logs. I'd also decided to add renovate-pretty-log -html option, which allows converting a debug log into a single-page, self-contained HTML file that allows reviewing a very similar view of the local tools, but in the browser.

## Finding which PRs have been taken out of the Merge Queue due to failed status checks

DevFeed: [Finding which PRs have been taken out of the Merge Queue due to failed status checks](<https://devfeed.tech/articles/finding-which-prs-have-been-taken-out-of-the-merge-queue-due-to-failed-status-checks-53091.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/08/11/github-merge-queue-prs/>)

Author: Jamie Tanna

Published: 2026-08-11T14:23:30Z

Content type: tutorial

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [GitHub](<https://devfeed.tech/topics/github.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [renovate](<https://devfeed.tech/topics/renovate.md>)

Tags: [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [error](<https://devfeed.tech/tags/error.md>), [github](<https://devfeed.tech/tags/github.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [merge](<https://devfeed.tech/tags/merge.md>), [renovate](<https://devfeed.tech/tags/renovate.md>)

### AI overview

A practical guide to finding approved Renovate pull requests that were removed from GitHub's Merge Queue after failed status checks. It uses a GitHub GraphQL query to identify the affected pull requests and the removal reason.

### Source excerpt

🤖 This post includes some LLM-derived content 🤖 In the Renovate project, we use the Merge Queue to merge PRs. If a PR fails its status checks, it will be pulled out of the Merge Queue, and a maintainer will need to re-queue it, if it is a transient error. For those of you unaware, GitHub are having a pretty hard time recently with outages, which means that we're seeing an increase in the number of PRs being pulled out of the Merge Queue due to transient errors due to GitHub's instability (and in rare cases, due to flakiness in our test suite). For a number of these PRs, they're dependency updates that Renovate raises (:yo_dawg:) which means that a maintainer doesn't necessarily see they're unmerged. If we want to find out which PRs are approved, but not merged due to the merge queue un-queuing them, we can use the following GraphQL query: # via Claude Sonnet 5 $ gh api graphql -f query='query { search(query: "repo:renovatebot/renovate is:pr is:open review:approved", type: ISSUE, first: 50) { nodes { ... on PullRequest { number title reviewDecision timelineItems(itemTypes: [REMOVED_FROM_MERGE_QUEUE_EVENT], first: 5) { nodes { ... on RemovedFromMergeQueueEvent { createdAt reason } } } } } } }' { "data": { "search": { "nodes": [ { "number": 45225, "reviewDecision": "APPROVED", "timelineItems": { "nodes": [] }, "title": "chore(deps): update dependency @biomejs/biome to v2.5.7 (main)" }, { "number": 45223, "reviewDecision": "APPROVED", "timelineItems": { "nodes": [ { "createdAt": "2026-08-11T13:26:04Z", "reason": "failed_checks" } ] }, "title": "fix(deps): update ghcr.io/renovatebot/base-image docker tag to v13.84.2 (main)" }, { "number": 44971, "reviewDecision": "APPROVED", "timelineItems": { "nodes": [] }, "title": "fix(manager/mix): run mix commands from the lock file's directory" } ] } } } In this case, we can see that PR 45223 was taken off the Merge Queue and needs to be merged.

## How AI-generated contributions are affecting open-source maintainers

DevFeed: [How AI-generated contributions are affecting open-source maintainers](<https://devfeed.tech/articles/how-much-ai-can-a-maintainer-get-away-with-using-without-losing-their-humanity-53090.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/08/02/ai-maintainer/>)

Author: Jamie Tanna

Published: 2026-08-02T19:39:42Z

Content type: opinion

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [open source maintenance](<https://devfeed.tech/topics/open-source-maintenance.md>), [Maintainers](<https://devfeed.tech/topics/maintainers.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [Go Language](<https://devfeed.tech/topics/go-language.md>), [renovate](<https://devfeed.tech/topics/renovate.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [burnout](<https://devfeed.tech/tags/burnout.md>), [go](<https://devfeed.tech/tags/go.md>), [llm](<https://devfeed.tech/tags/llm.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [open-source-maintenance](<https://devfeed.tech/tags/open-source-maintenance.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [renovate](<https://devfeed.tech/tags/renovate.md>)

### AI overview

An open-source maintainer reflects on how AI-assisted contributions and feature requests are increasing maintenance pressure, while also improving adoption and engagement. The post considers sustainability, burnout, and how maintainers can preserve the human side of open-source work.

### Source excerpt

🤖 This post includes some LLM-derived content 🤖 I've been recently thinking about how Open Source maintenance seems to be becoming a little more a slog recently - largely with the increased amount of contributions possible with AI agents - and how it impacts being a maintainer. I'm very fortunate that my literal job is to be an Open Source project maintainer (among other things) and that it's a privilege not many others have. That being said, it still doesn't mean that undoes the amount of work that seems to be increasing every month. Mike McQuaid recently wrote an eloquent post about how Open Source needs to be fun, which naturally struck a chord - the work that we do needs to be sustainable and enjoyable. As someone who feels like they're consistently pushing the edges of burnout - possibly due to my ADHD - I've hit a bit of a wall several times, where the overwhelm of so many things to do unfortunately leads to needing to (often silently) take a step back from the project for my own mental wellbeing. This is moreso true with oapi-codegen and how we're trying to make it more sustainable. oapi-codegen is a widely used project with a difficult API surface: give me your arbitrary OpenAPI specs, and we'll convert the complex or straightforward spec to a form of Go that is generally nice to use. Being guided by our users' usage can be difficult at time, as well as Go's not-that-great type system. More recently, we've been feeling this pain with Renovate, and a significant uptick in contributions and feature requests that aren't really scaling with the team size we have, largely due to the usage of contributions with help from AI agents. (But at the same time, it's pretty great that we are seeing an increase in adoption and engagement, and the patterns in our codebase work quite well for AI agents to help with contributions!) This has been something on my mind for a bit - as the project lead, I'm looking at what we can do to make things more sustainable for us as a proj

## GitHub agentic workflows and Renovate

DevFeed: [GitHub agentic workflows and Renovate](<https://devfeed.tech/articles/github-agentic-workflows-and-renovate-18920.md>)

Original publisher: [Read original article](<https://blog.frankel.ch/github-agentic-workflow-renovate/>)

Author: Nicolas Fränkel

Published: 2026-08-02T00:00:00Z

Content type: tutorial

Language: en

Sources: [Nicolas Fränkel](<https://devfeed.tech/sources/nicolas-frankel.md>)

Topics: [renovate](<https://devfeed.tech/topics/renovate.md>), [GitHub Agentic Workflows](<https://devfeed.tech/topics/github-agentic-workflows.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-workflow](<https://devfeed.tech/tags/agentic-workflow.md>), [agentic-workflows](<https://devfeed.tech/tags/agentic-workflows.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [synchronization](<https://devfeed.tech/tags/synchronization.md>), [technical](<https://devfeed.tech/tags/technical.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

Renovate updates the generated lock file for an agentic GitHub workflow by bumping its pinned action SHA, but the lock file's inline scripts must match the action release. In the described case, the script body stayed unchanged while referring to a helper script absent from the new release, causing the workflow to fail. The author's attempted fix--recompiling whenever that file changed--also triggered on Renovate's Node.js pin update and overwrote it. The excerpt identifies the root cause: the compiler generates the whole lock file from a single release, so its action pin and inline scripts must stay synchronized. It cuts off before giving the correct solution.

### Source excerpt

I've been a big fan of Renovate for a couple of years already. Renovate scans your repositories, detects outdated package versions, and opens pull requests to automatically bump them. It's similar to Dependabot in that it keeps your dependencies up to date. If I had to compare them in one sentence, I'd say Renovate is less integrated in the GitHub ecosystem, but handles more ecosystems and, more importantly, is extensible.

## Reducing overly nested Vendir paths

DevFeed: [Reducing overly nested Vendir paths](<https://devfeed.tech/articles/reducing-overly-nested-vendir-paths-53088.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/07/21/vendir-nesting/>)

Author: Jamie Tanna

Published: 2026-07-21T08:30:35Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [renovate](<https://devfeed.tech/topics/renovate.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [GitHub Issues](<https://devfeed.tech/topics/github-issues.md>)

Tags: [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [claude](<https://devfeed.tech/tags/claude.md>), [github-issues](<https://devfeed.tech/tags/github-issues.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [renovate](<https://devfeed.tech/tags/renovate.md>)

### AI overview

A practical post explains how to use Vendir's `newRootPath` option to reduce overly nested directories when syncing OpenAPI specifications. The author describes combining Renovate and Vendir, then shows a configuration change that downloads the specification to a shorter path.

### Source excerpt

🤖 This post includes some LLM-derived content 🤖 I've recently been using the pattern I described to combine Renovate and Vendir to sync files in a number of repos, as a means to track OpenAPI spec dependencies. However, one thing I've found a bit painful is that when using Vendir to track these dependencies, the directory structure gets very nested. For instance, with config such as: # via https://github.com/rootlyhq/rootly-go/blob/61c86b8660b6f25d1e8d8638417de173350dfb61/vendir.yml apiVersion: vendir.k14s.io/v1alpha1 kind: Config directories: - path: .vendored contents: - path: rootly-api http: url: https://rootly-heroku.s3.amazonaws.com/swagger/v1/swagger.json This leads to .vendored/rootly-api/swagger.json being the full OpenAPI spec path. Getting rather frustrated about this - while working on ecosystems-go - I sought some help from Claude Sonnet 4.5 after digging through GitHub Issues to no avail, and noticed a config option newRootPath that I'd missed before. With this config, we can replace the above with: apiVersion: vendir.k14s.io/v1alpha1 kind: Config directories: - path: .vendored contents: - path: rootly-api.json newRootPath: swagger.json http: url: https://rootly-heroku.s3.amazonaws.com/swagger/v1/swagger.json This will now download the spec as .vendored/rootly-api.json which is a bit more reasonable.

## Week Notes 26#20

DevFeed: [Week Notes 26#20](<https://devfeed.tech/articles/week-notes-26-20-53133.md>)

Original publisher: [Read original article](<https://www.jvt.me/week-notes/2026/20/>)

Author: Jamie Tanna

Published: 2026-05-17T20:17:22Z

Content type: opinion

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [renovate](<https://devfeed.tech/topics/renovate.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [npm](<https://devfeed.tech/topics/npm.md>), [Job](<https://devfeed.tech/topics/job.md>), [Code generation](<https://devfeed.tech/topics/code-generation.md>)

Tags: [codegen](<https://devfeed.tech/tags/codegen.md>), [developer](<https://devfeed.tech/tags/developer.md>), [github](<https://devfeed.tech/tags/github.md>), [job](<https://devfeed.tech/tags/job.md>), [npm](<https://devfeed.tech/tags/npm.md>), [oapi-codegen](<https://devfeed.tech/tags/oapi-codegen.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [senior-developer](<https://devfeed.tech/tags/senior-developer.md>), [week-notes](<https://devfeed.tech/tags/week-notes.md>)

### AI overview

A personal weekly note covering a changed job title, work as a Senior Developer and Open Source Project Maintainer, Renovate project leadership, npm release support issues, webinar preparation, open-source writing, and work on oapi-codegen and rootly-go, alongside personal activities and media.

### Source excerpt

Got my job title changed at work, covering the role I do have and the work I'm doing (but no update to /salary/) which is cool! It's also a lot easier to say: -Senior Developer and Open Source Project Maintainer +Renovate Project Lead Another busy week with a lot of stuff going on, but some good bits done Preparing for a webinar I'm doing next-next week Still waiting for GitHub/npm support to help us unpublish a number of old npm releases so we can publish new package versions for Renovate Had a nice catch-up with Ellie and Linh Another episode of Fallthrough - still many things left unsaid! In Kingshot, excited for KvK against 521 (my old server) and hoping there's not much drama 😅 Finally wrote up why Libyears is a metric to be careful about Wayne came to patch up where the beasties have been 🐿 Did some bits on oapi-codegen and rootly-go this weekend Wrote a slightly clickbait post about the rise of using "open-source" - I'm still not super happy with the wording of the title as it feels a little clunky The Hacker News discussion was pretty standard for them, and was fun to get the thread flagged because of one of the commenters 🫠 Cookie had great fun time when she found a squirrel hiding behind the compost bin and getting very close to catching it - I stopped her and tried to get the squirrel to run away, but it ended up running towards me/through my legs, but decided to start climbing on me 😳😳😳 I yelped a little and it jumped off, and I got Cookie into the conservatory so it could try and get free. She spent a lot of the rest of the day being very detective-like in trying to find where it was Had a nice dinner at Myeong Dong - albeit it wasn't quite as DIY as when I'd been to a Korean BBQ place in London - and a very sweet Cookie Dough at Creams afterwards Booked flights for our holiday 👀 Reading: Persepolis Rising Watched: The Expanse (Season 4) Succession (Season 2) Succession (Season 3) Star Trek: Into Darkness (2013) Star Trek: Beyond (2016) Saturday Night

## Caveats around using Libyears

DevFeed: [Caveats around using Libyears](<https://devfeed.tech/articles/caveats-around-using-libyears-53084.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/05/14/caveat-libyear/>)

Author: Jamie Tanna

Published: 2026-05-14T08:52:17Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Dependency management](<https://devfeed.tech/topics/dependency-management.md>), [renovate](<https://devfeed.tech/topics/renovate.md>), [upgrade](<https://devfeed.tech/topics/upgrade.md>), [version](<https://devfeed.tech/topics/version.md>)

Tags: [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [changes](<https://devfeed.tech/tags/changes.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [dependency-management](<https://devfeed.tech/tags/dependency-management.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [ospo](<https://devfeed.tech/tags/ospo.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

This article examines caveats in using Libyears as a metric for dependency freshness. It explains that the metric can hide breaking changes, transitive upgrade work, and differences between software ecosystems, so organizations should avoid treating a lower score as automatically indicating less upgrade work.

### Source excerpt

Over the last few years, I've spent time working on projects like dependency-management-data with the intent that I could provide visibility into organisational usage of dependencies and insight into how outdated they are, which continues with working upstream on Renovate and Mend's enterprise offerings. Over the last few years of work, I've spent time looking at some of the great metrics the CHAOSS project work on, where I found the Libyear metric: Libyears gives a more tangible definition of "dependency freshness", and a more meaningful description of how outdated your dependencies are. At face value, Libyear is a really useful metric to discuss, but comes with a few caveats to be aware of. Renovate exposes information about Libyear calculations, but each time I end up discussing Libyears with someone, I end up sharing these caveats. Before finally writing official documentation about Libyears and the caveats, I wanted to flesh out my ideas on my blog, first. Breaking changes One key thing that isn't taken into account in Libyears is what changes you're taking into account. This is an intentional choice by the author, and I don't fault them for it - but it's something that isn't necessarily made as clear as it could be to users of the metric, especially if used by organisations who think "small number good". For instance, given two projects which have a "0.5 Libyears" and "1.0 Libyears", which of the two has more work to do to upgrade? Yes, that was a trick question, because: 0.5 Libyears: includes 1 major version (with breaking changes) bump, every month for 5 months 1.0 Libyears: includes 1 patch version (with no breaking changes), 12 months ago Looking at the number itself hides the fact that there is some nuance to take into account around what changes are included in those upgrades. This calculation often doesn't include transitive upgrades or indirect work required, so a major version bump (with a new package name) is different to a major version bump where

## Practical Package Security: The Unofficial Guide

DevFeed: [Practical Package Security: The Unofficial Guide](<https://devfeed.tech/articles/practical-package-security-the-unofficial-guide-53935.md>)

Original publisher: [Read original article](<https://www.wiz.io/blog/practical-package-security-the-unofficial-guide>)

Author: Rami McCarthy

Published: 2026-05-04T14:00:00Z

Content type: tutorial

Language: en

Sources: [Wiz](<https://devfeed.tech/sources/wiz-blog-rss-feed.md>)

Topics: [Package Management](<https://devfeed.tech/topics/package-management.md>), [Security](<https://devfeed.tech/topics/security.md>), [malicious packages](<https://devfeed.tech/topics/malicious-packages.md>), [npm](<https://devfeed.tech/topics/npm.md>), [renovate](<https://devfeed.tech/topics/renovate.md>), [Dependabot](<https://devfeed.tech/topics/dependabot.md>), [pnpm](<https://devfeed.tech/topics/pnpm.md>), [PyPI](<https://devfeed.tech/topics/pypi.md>)

Tags: [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [malicious-packages](<https://devfeed.tech/tags/malicious-packages.md>), [package-management](<https://devfeed.tech/tags/package-management.md>), [post](<https://devfeed.tech/tags/post.md>), [practical](<https://devfeed.tech/tags/practical.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

A practical guide to package security that explains how supply-chain compromises spread through maintainer accounts, build systems, and downstream dependencies. It recommends reducing dependency depth, delaying package updates to allow compromise detection, and using tools such as Renovate, Dependabot, pnpm, and uv while balancing security, developer experience, and maintainer sustainability.

### Source excerpt

Get actionable best practices to shrink your attack surface, protect execution environments, control package ingestion, and catch compromises early.

## Week Notes 26#18: Renovate and oapi-codegen maintenance, release, and publishing issues

DevFeed: [Week Notes 26#18: Renovate and oapi-codegen maintenance, release, and publishing issues](<https://devfeed.tech/articles/week-notes-26-18-53131.md>)

Original publisher: [Read original article](<https://www.jvt.me/week-notes/2026/18/>)

Author: Jamie Tanna

Published: 2026-05-03T20:57:20Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [renovate](<https://devfeed.tech/topics/renovate.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Go Language](<https://devfeed.tech/topics/go-language.md>), [releases](<https://devfeed.tech/topics/releases.md>), [npm](<https://devfeed.tech/topics/npm.md>), [Docker](<https://devfeed.tech/topics/docker.md>)

Tags: [docker-images](<https://devfeed.tech/tags/docker-images.md>), [go](<https://devfeed.tech/tags/go.md>), [npm](<https://devfeed.tech/tags/npm.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [releases](<https://devfeed.tech/tags/releases.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [week-notes](<https://devfeed.tech/tags/week-notes.md>)

### AI overview

A weekly personal update covering work on Renovate and oapi-codegen, including Go module update controls, maintainer support, a v2.7.0 release, maintenance, a Renovate configuration preset, and an npm publishing blockage. It also includes personal activities, reading, music, meals, and television.

### Source excerpt

A fairly busy week at work, and a mix of getting stuff done across the Open Source world In Renovate: Finished off the ability to make it so Renovate only provides updates to Go modules within your go directive, which we've wanted for oapi-codegen - already been very useful! With it being the start of Maintainer Month, I've been thinking about what we can do to support maintainers who use Renovate, as well as increase insight into the Renovate project itself We hit the "too many published versions" issue we hit late last year, and have been blocked from releasing for most of the week - still waiting on npm support at GitHub to take a look to help us unpublish a load of old releases so can continue shipping the npm package, but at least we have Docker images being published in the meantime In oapi-codegen: Marcin's work on the project culminated in the v2.7.0 release, and some interesting discussion on reddit I also helped out with a few bits of maintenance We now also have a Renovate config preset for our users, who may find it useful Was reminded of how great Tollef's music is, and it's hard not to listen to Sunshine without an instant mood boost Had a nice lunch yesterday at Local, with a very nice Korean fried chicken "sando" - although we'd hoped to get to Kushi-ya, arriving at 1208, there was over an hour's wait! Had a nice lunch today at The Windmill Inn with Anna's parents, and a very good (and lovely and rare) roast beef 😋 Morph's got a dodgy lip, where his recent canine removal is leading to his tooth pressing against the upper lip 🥺 He's doing OK (and the vets are happy with it while it's staying OK) but we're keeping an eye Had a nice catch-up with Rich on Friday Reading: Persepolis Rising Is so damn good - I've only read the final trilogy once before and there's so much happening Watched: The Expanse (Season 2) Taskmaster (Series 21) Succession (Season 1) Succession (Season 2) Celebrity Traitors (Series 1) Thought we'd get around to watching it, given th

## Configuring Renovate to only suggest updates that match your \`go\` directive

DevFeed: [Configuring Renovate to only suggest updates that match your \`go\` directive](<https://devfeed.tech/articles/configuring-renovate-to-only-suggest-updates-that-match-your-go-directive-53081.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/05/02/renovate-only-go-directive/>)

Author: Jamie Tanna

Published: 2026-05-02T18:24:27Z

Content type: tutorial

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Go Language](<https://devfeed.tech/topics/go-language.md>), [renovate](<https://devfeed.tech/topics/renovate.md>), [toolchain](<https://devfeed.tech/topics/toolchain.md>), [upgrade](<https://devfeed.tech/topics/upgrade.md>)

Tags: [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [go](<https://devfeed.tech/tags/go.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [toolchain](<https://devfeed.tech/tags/toolchain.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

This tutorial explains how Go's go and toolchain directives control language compatibility, toolchain selection, and standard-library security patches. It describes configuring Renovate to suggest updates that match the project's go directive, with different guidance for applications and libraries.

### Source excerpt

In the Go ecosystem, there are two key parts of the go.mod to note (aside from the dependencies themselves) which are the go and toolchain directives. The go directive allows specifying the minimum version of the Go language that needs to be used to work with this module. The toolchain directive allows specifying the minimum version of the Go toolchain that needs to be run to build the module, which also controls the version of Go's standard library that is used with the module (and therefore which security patches the standard library has applied). In Go 1.21, the Go team introduced toolchain, and moved the go directive from being a "suggested" minimum version to a mandatory version. Splitting the two of these allow you to use a newer version of Go (for instance on your local machine, or as part of your Docker image) while still being clear on what the compatibility of the code should be and allowing for code from a much older version of Go to be used, and it allows for two levels of control over how a given module is used. When building applications (such as command-line tools that users install separately, or when building web services), it's common to keep the go directive as high as the author would like, so you can take advantage of new features of Go, and the toolchain as high as possible, to make sure you're receiving security patches. When building a library (or tool that is a dependency in the project, for instance via go tool), the inverse is true - it is common to be quite reserved with the go directive, and not set the toolchain directive at all. This comes out of a "ripple effect" that can occur when a library updates its go directive, requiring each of its consumers to also update their own go directive. Because Go requires the go directive to be a minimum version, if a dependency was to require a new minor version of Go, it means each and every of its dependencies also need to do so, at the point they upgrade to the new version. For instance, with oa

## Week Notes 26#17

DevFeed: [Week Notes 26#17](<https://devfeed.tech/articles/week-notes-26-17-53130.md>)

Original publisher: [Read original article](<https://www.jvt.me/week-notes/2026/17/>)

Author: Jamie Tanna

Published: 2026-04-26T20:14:55Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [renovate](<https://devfeed.tech/topics/renovate.md>), [Go Language](<https://devfeed.tech/topics/go-language.md>), [Neovim](<https://devfeed.tech/topics/neovim.md>)

Tags: [github-actions](<https://devfeed.tech/tags/github-actions.md>), [go](<https://devfeed.tech/tags/go.md>), [neovim](<https://devfeed.tech/tags/neovim.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [week-notes](<https://devfeed.tech/tags/week-notes.md>)

### AI overview

A personal weekly note covering work on OpenAPI 3.1 support in oapi-codegen, Renovate updates, GitHub Actions versioning, limiting pull requests for Go projects, and a Neovim upgrade, alongside personal activities and media.

### Source excerpt

A pretty intense environment this week, so not too much else done outside of work Another episode of Fallthrough - this time a bit more random in what we covered, but good Tried making sweet and spicy Korean chicken - wasn't quite right in terms of measurements (and a little too little gochujang) but was good Listening to How Did This Get Made?'s episode on Master of Disguise reminded me of watching it many many years ago with the family - I remember them very much regretting letting me choose that film 😅 But I enjoyed it at least The weather's nice so we've been in the conservatory a little more, and the shorts are out Has science gone too far? It turns out my glasses do help me see better - both while in the car and watching TV! Begrudgingly I've accepted them and the sharper quality Had some good song radios on Spotify, finding some good new songs based on LEV, Marion Dahlskog - Body, like Jack Willard - Paragon Had Carol and Alan over for cheese and sticky toffee night on Saturday which was nice In oapi-codegen: OpenAPI 3.1 is finally coming! Pierre's done some great work upstream to get the first stab at 3.1 support in, and we're working towards making it available for our side too Given no one else seems to be putting their money where their mouth is, I'm going to give a chunk of our sponsorship pot to Pierre In Kingshot we had a good first KvK in the new server, smashing it, and I was ~40 overall Some good Renovate-y work this week (and finishing off the support for the new GitHub Actions versioning scheme), and continuing to get it possible to limit PRs for Go projects, based on the go directive in use My write-up about the intricacies of GitHub Actions tagging formats unfortunately didn't do as well as I'd hoped on Hacker News, but I'm glad I wrote it up, and finished off the support! On my work machine, had the upgrade to Neovim 0.12 and a few things breaking - but managed to get there in the end Morph chased off a fox! We heard a commotion as we'd gone to

## A deep dive into the wild world of GitHub Actions' tagging formats

DevFeed: [A deep dive into the wild world of GitHub Actions' tagging formats](<https://devfeed.tech/articles/a-deep-dive-into-the-wild-world-of-github-actions-tagging-formats-53079.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/04/24/github-actions-tagging/>)

Author: Jamie Tanna

Published: 2026-04-24T10:53:55Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [releases](<https://devfeed.tech/topics/releases.md>), [open-source-security](<https://devfeed.tech/topics/open-source-security.md>), [renovate](<https://devfeed.tech/topics/renovate.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [open-source-security](<https://devfeed.tech/tags/open-source-security.md>), [releases](<https://devfeed.tech/tags/releases.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

A deep dive into GitHub Actions tagging formats, prompted by Renovate and Dependabot failing to update Astral's setup-uv action after its move from mutable to immutable releases. The article explains why immutable releases improve open-source security and discusses the complexity and edge cases involved in handling these tags.

### Source excerpt

Last week, I was tagged in a LinkedIn post, where one of the Python Core developers was noting that Astral's setup-uv GitHub Action was not being updated by either Renovate or Dependabot, and a note to users that they would need to manually update. I was a bit surprised about this - as it was the first time I'd heard about it - and this is never the scenario I'd want Renovate users to be in - manual bumping a version in a file should be a thing of the past! After digging into a GitHub Issue about this on setup-uv, it was confirmed that was due to their move from mutable GitHub Actions releases to Immutable Releases, and that Renovate wasn't handling this upgrade in a reasonable way. I had a bit of time on my hands, and some unfounded hubris for the time of day, so I thought "huh, how hard could this be?", and felt that a speedy fix would be a positive for Renovate and our users. It turns out the way that tagging formats work with GitHub Actions is a little bit more complex than I'd first thought, and a few edge cases (as well as not-so-edge-cases) brought me back to reality. I was humbled by intermittently breaking things for folks for a couple of days, rolled it back, and started fresh. Because this wasn't straightforward, I thought this would be a great opportunity to document it as a form of blogumentation. Why Immutable Releases? Before we get into what happened with the tag formats, it's worth talking briefly about what Immutable Releases are and why they're useful. This could very well be a separate post, but I'll try and cover it briefly here. The folks over at Astral wrote about their approach to open source security which is worth a read as it includes how Immutable Releases protect them, as well as a tonne of other great practices. GitHub's launch of Immutable releases in October last year was a long awaited feature, allowing a repository's pushed GitHub Releases (and the tags that underpin them) to never be updated again. This key protection ensures that

## Week Notes 26#16

DevFeed: [Week Notes 26#16](<https://devfeed.tech/articles/week-notes-26-16-53129.md>)

Original publisher: [Read original article](<https://www.jvt.me/week-notes/2026/16/>)

Author: Jamie Tanna

Published: 2026-04-19T20:12:23Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [renovate](<https://devfeed.tech/topics/renovate.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [Go Language](<https://devfeed.tech/topics/go-language.md>), [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>)

Tags: [github-actions](<https://devfeed.tech/tags/github-actions.md>), [go](<https://devfeed.tech/tags/go.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [week-notes](<https://devfeed.tech/tags/week-notes.md>)

### AI overview

A personal weekly notes post covering work on Renovate updates, Go module version constraints, the Debug Adapter Protocol, and GitHub Actions, alongside podcasting, gaming, social activities, and media consumed.

### Source excerpt

A busy week at work Was pretty chuffed with myself when I saw a nudge about astral-sh/setup-uv not being updated by Renovate (since the move to Immutable Releases) and I was able to solve it pretty quickly, showing some good speed of reaction compared to alternative products But, alas, it ended up being a little more complicated and breaking a few things, and I probably could've taken a breath to make sure it was right Did end up getting a good solution in by Friday afternoon, and looking forward to turn it on this week (In my personal time) making some more progress with making it possible for Renovate to only suggest Go module updates within your Go minor version Had a fun Fallthrough recording, was good to chat with Kris and Ian and we covered a lot of stuff - kinda expected with ~4 hours of convo! In Kingshot it was Kingdom Transfer time for a few of us from 521, and it's been a good week so far in 511! Bear Hunt is a little bit more chaotic but very much in a good way! Very well organised and leading to some great scores Had a nice pizza Thursday Spent a lot of time fighting the Debug Adapter Protocol (DAP) but managed to get it working + blogged about Was a bit of a pain because I was trying to fix the GitHub Actions functionality, and fighting outdated docs and/or plugins not working as expected, but managed to get there! Had a nice Saturday out with Carol and Alan, with nice breakfast at Speciality then a mooch around the Contemporary's food + craft fair There were so many diddy dogs around that were 🥰🥺 Was lovely to catch-up with Ellie and Linh on Friday Was the 6-month checkin in the GitHub Secure Fund, and 🤞🏼 they're happy with progress Got some last-minute submissions into GopherCon UK's CFP, and I really would like to do the talk! Been enjoying listening to "How Did This Get Made?" Had a very dystopian moment in the car earlier - listening to a podcast and adding a note to myself to mention to the host about an issue with the audio - and Gemini (now tak

## Week notes: protecting users from malicious packages and maintaining developer tooling

DevFeed: [Week notes: protecting users from malicious packages and maintaining developer tooling](<https://devfeed.tech/articles/week-notes-26-15-53128.md>)

Original publisher: [Read original article](<https://www.jvt.me/week-notes/2026/15/>)

Author: Jamie Tanna

Published: 2026-04-12T19:54:40Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [malicious packages](<https://devfeed.tech/topics/malicious-packages.md>), [renovate](<https://devfeed.tech/topics/renovate.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>), [Go Language](<https://devfeed.tech/topics/go-language.md>), [releases](<https://devfeed.tech/topics/releases.md>), [software-development](<https://devfeed.tech/topics/software-development.md>)

Tags: [dev](<https://devfeed.tech/tags/dev.md>), [git](<https://devfeed.tech/tags/git.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [go](<https://devfeed.tech/tags/go.md>), [malicious-packages](<https://devfeed.tech/tags/malicious-packages.md>), [releases](<https://devfeed.tech/tags/releases.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [week-notes](<https://devfeed.tech/tags/week-notes.md>)

### AI overview

A weekly personal notes post covering work on protecting users from malicious packages, including a short-term fix using OSV data and a planned longer-term solution. It also discusses oapi-codegen, Renovate dependency updates, Renovate Cloud on GitLab.com, releases, and a git diff driver, alongside personal activities and media.

### Source excerpt

A 3 day week, with Easter Monday and a recharge day at work A busy week at work, continuing on protecting our users from malicious packages Including a short-term fix using OSV data, and a longer-term solution planned that I'm working through which will provide some strong extension points in the future Some oapi-codegen work Including some improvements to Renovate to allow not updating dependencies that will bump the go directive In renovate-graph: (Aren't you surprised to see me mention this? 👀) I'd got it approved a while back to be able to keep it updated, but not yet had a chance to sit down and do so Got Mend's Renovate Cloud on GitLab.com to keep it updated, and did a few releases up until I need to handle some breaking changes to our types I'll only be keeping the dependencies updated, at least for now A nice Friday night at Slice 'n' Brew, but the bar next door's music was so loud it made it quite hard to hear anything 😅 Lots more mental energy spent Wrote about how to make a git diff driver Almost got it done before we went out for pizza, but it was a little bit rushed And probably for the best, because when someone crossposted it to Hacker News, it did particularly well - a minimum of 18 hours on the front page! (And several hours as top 3) I was reminded of Are U Feelin Me (Mord Fustang 'Round 2' Remix) - Kock2, DEV, Mord Fustang and had that on repeat a fair bit this week I also had Slender People - Bob Mortimer stuck in my head for days after Last One Laughing Had a nice massage on Friday morning A pretty chill long weekend, which has been nice Noticed that a few posts from earlier hadn't been deployed, and it looked like there's some fun around timezones that I've not seemed to have hit in the past - maybe because my builder image is from 2022 A super disappointing turn of events is that Asda are stopping their create-your-own pizzas, which has been a staple of our Friday nights for ~10 years I'd missed a forewarning on /r/ASDA, but when I went on Mon

[Next page](<https://devfeed.tech/topics/renovate.md?cursor=WyIyMDI2LTA0LTEyVDE5OjU0OjQwKzAwOjAwIiwgImM1NmM3OGM0LTQ2YzItNDkzNy1iYzJjLTNhZTA5ZDY4YzYzYiJd>)