chore(deps): update docker non-major #332
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/docker-non-major"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v2.11.0→v2.37.23.10-slim→3.15-slim3.12-slim→3.15-slim1.85-bookworm→1.99-bookwormRelease Notes
binwiederhier/ntfy
v2.37.2Compare Source
Changelog
0510957Merge pull request #2169 from binwiederhier/release-2380v2.37.1Compare Source
This release fixes a database slowdown in v2.37.0 when using
visitor-subscriber-rate-limitingwith a user database: the subscriber activity of UnifiedPush topics was written far too often.Bug fixes + maintenance:
visitor-subscriber-rate-limitingand a user database, write a UnifiedPush topic's subscriber activity every one to two hours instead of every 5 minutes, spread over time, and not at all when a poll or reconnect only repeats the same subscriber; on ntfy.sh, v2.37.0's writes of ~45k topics every 5 minutes, all due in the same minute, slowed down the database (#2151)v2.37.0Compare Source
This release makes UnifiedPush work across several servers: the subscriber who pays for a topic's pushes is shared through the database, and app servers are told with
410 Gonewhen a subscription has been abandoned for 4 days. It also addsRetry-Afterand the draftRateLimitheaders to rate limit responses, and frees the memory of one-off visitors sooner.Features:
visitor-subscriber-rate-limiting, the subscriber of a UnifiedPush topic (who pays for its pushes) is kept in the user database and shared by all servers, so a push to any server is billed to the subscriber instead of answered with 507 (#2136; see subscriber-based rate limiting)Retry-Afterheader with HTTP 429 responses that are caused by a rate limit with a known wait, e.g. the request, e-mail or daily message limits (#2142; see rate limiting)RateLimit-PolicyandRateLimitheaders with publish responses (and with every 429 caused by a limit with a quota), for the request and daily message limits (#2143; see rate limiting)ntfy_topics_unifiedpush_total: the UnifiedPush topics whose subscriber state a server keeps in memory (#2136)Behavior changes:
visitor-subscriber-rate-limiting, a UnifiedPush push to a topic that has had no subscriber (subscribe, poll or open stream) for 4 days is answered with410(error code 41002) instead of507, so app servers like Mastodon remove the expired subscription (#664, #2136); a Matrix push to such a topic gets its pushkey rejected (before: after 12 hours without a subscriber on the server that got the push)visitor-subscriber-rate-limiting, UnifiedPush messages are counted against the subscriber's account only while it has a tier, and against the subscriber's IP address otherwise (also after the account lost its tier or was deleted); a tier change applies to the next message (#2136)0.001), auth failures (42909) now weigh 2 instead of 10, and a UnifiedPush push without a subscriber (50701) or to an abandoned topic (41002) weighs 0.05, so app servers pushing to many offline phones are not banned for it (#2147)visitorsstat and thentfy_visitors_totalmetric therefore count the visitors of roughly the last minute, not of the last day (#2126)visitor-topic-creation-limit-burst) (#2136)Bug fixes + maintenance:
ntfy_cluster_messages_wasted_total) and no longer keeps that idle topic in memory (#2140)v2.36.0Compare Source
This release keeps the daily limits across restarts and, with PostgreSQL, shares them between servers, so a visitor gets one daily allowance in total. Each visitor's day now starts at its own time instead of midnight UTC. It also adds an experimental local admin socket.
Features:
/v1/account(stats.reset_at) show when it resets (#2131, see message limits)experimental-listen-admin-unix, off by default) that serves the admin API without credentials to whoever can open it; the shipped systemd unit setsRuntimeDirectory=ntfyfor it (see admin socket)ntfy_db_upper PostgreSQL pool, and health-check the primary like the replicas (#2133)Upgrade notes:
stats_*columns of the user table are zeroed and no longer usedvisitor-email-limit-replenish)base-urlor amessage-size-limitabove 4K is set, so an invalid config that used to start now fails at startup (#1969, thanks to @mikejgray for the contribution)Bug fixes + maintenance:
ntfy pub --wait-pidnow waits for processes owned by other users instead of failing with "not running" (#1710, thanks to @bekoeppel for the contribution)v2.35.0Compare Source
This release keeps what a user already spent when their tier changes, and makes a tier's daily email limit a hard cap. It also fixes intermittent 403s under concurrent requests from the same IP, and the Matrix push gateway storing messages under a protected topic on SQLite.
Security:
/sec%00retwas authorized against an unmatched topic and then stored under the protected topicsecret(SQLite only; on PostgreSQL the request was denied; thanks to Efe Çam for reporting)Features:
Bug fixes + maintenance:
visitor-email-limit-burst)ip:<prefix>oruser:<id>, instead of in each visitor, which uses less memory per visitor and takes a global lock off the request path1T) in size settings such as attachment and tier limits, matching how sizes are displayed (#2078, thanks to @cangen185-sudo for the contribution)v2.34.0Compare Source
This release prepares the experimental cluster to run behind load balancers: nodes drain on shutdown instead of dropping all of their clients at once, ntfy can listen on several addresses, and access changes reach every node. It also fixes a revoked or deleted user keeping some of their subscriptions, on every server.
Features:
listen-http, so a load balancer can hold more than ~63k connections to one ntfy nodeexperimental-cluster-drain-delay,experimental-cluster-drain-duration), so its clients move to the other nodes without a reconnect storm (experimental, see draining on shutdown)Security:
ntfy accessCLI, and now runs every 67 seconds instead of 87Bug fixes + maintenance:
log-level-overridesis on: the subscriptions' topic stayed locked for goodlog-level-overrideschanges (e.g. on a config reload with SIGHUP) while the server logsv2.33.1Compare Source
This release builds ntfy with Go 1.27.3 (security fixes, including rejecting the compromised eMudhra intermediate CAs), and adds monitoring for the experimental cluster: each node's view of its peers, per-peer and database connection pool metrics.
The v2.33.0 release had an issue that made it crash on older CPU architectures. The v2.33.1 release fixes that (see #2092).
Features:
ntfy cluster status,/v1/cluster/statuson the cluster listener, and per-peer metrics, so a link that only works in one direction is visible (experimental clustering, see cluster status)ntfy_db_pool_*: connections in use, and queries that waited for a free connection, per pool), to sizepool_max_conns(see PostgreSQL)Security:
crypto/tls,net/http,html/templateand others) and 1.27.3 (crypto/x509: certificate chains through the compromised eMudhra intermediate CAs are rejected)Bug fixes + maintenance:
v2.33.0Compare Source
v2.32.0Compare Source
This release prepares ntfy.sh for a passive cluster node: jobs that write to the shared database run only on the cluster leader, and each database store now records the oldest schema version it works with. Streaming subscriptions also tell proxies not to buffer them.
Features:
Incremental: ?1header (RFC 10036) on streaming subscriptions, so proxies that support it forward messages without buffering (#2056, thanks to @bt90 for the suggestion)Bug fixes + maintenance:
?tpl=<name>) ignoring the priority sent with the request when the file has noprioritykey (#2045, thanks to @6801318d8d for reporting)auth-usersthrough the admin API (#2062, thanks to @daniloamiranda for reporting)v2.31.1Compare Source
This release fixes the database load that made us roll back ntfy.sh from v2.31.0: reconnecting with
since=<message ID>read every message of the topic from the database. A new index makes these reconnects cheap, cheaper than in v2.30.0. It also lets ntfy start with a warning on a newer database schema, so later rollbacks need no manual step.Bug fixes + maintenance:
since=<message ID>reading every message of the topic from the database, which overloaded ntfy.sh's database right after the v2.31.0 upgrade; the message cache gets a new index: (topic, published, id) on PostgreSQL, (topic, published, time) on SQLite (#2058)Upgrade notes:
since=<message ID>reconnects). Downgrading to v2.31.0 or earlier afterwards requires setting the version back by hand first:UPDATE schema_version SET version = 16 WHERE store = 'message'on PostgreSQL, orUPDATE schemaVersion SET version = 16 WHERE id = 1in the SQLitecache-file. From this release on, a newer schema only logs a warning (#2059)v2.31.0Compare Source
This release fixes messages that could be lost when a client reconnects, e.g. a phone switching networks, right when messages are published: every server now reads newly written messages from its message cache once a second and sends them to the subscribers that missed them. In load tests with server restarts and crashes, this brought lost messages down from 465 to 2 out of about 615,000. It also adds a
/v1/readyendpoint for load balancers, and continues the experimental clustering work with node roles.Features:
/v1/readyfor load balancers, and the node's role to/v1/health; with clustering, a node with no other active node leads right away instead of after a one-minute hold-off (#2050)experimental-cluster-roleto run apassivenode that never leads and never takes over another node's subscribers, e.g. one that is not behind the load balancer (#2049)Bug fixes + maintenance:
Upgrade notes:
since=<message ID>now also returns the messages published in the same second as that message, so none are skipped when several servers write out of order. The ntfy apps and web app drop these by ID; your own scripts may see a few duplicates (#2040)UPDATE schema_version SET version = 1 WHERE store = 'node_registry'(#2049)v2.30.0Compare Source
This release links attachments in email notifications, adds SMTP LOGIN auth (e.g. for OVH and Outlook), and fixes the PostgreSQL memory growth that came with v2.29.0. It also ships the first experimental version of clustering: several ntfy servers sharing one PostgreSQL database. Clustering is not ready for production yet.
Features:
experimental-cluster-listen; this is not ready for production yet (#2005, #2008, #2012, #2013)Bug fixes + maintenance:
Dockerfile-buildfailing to build: use Go 1.26 and add theclusterpackage (#1962, thanks to @ElectricTea for reporting)org.opencontainers.image.versionlabel on release Docker images (#1921/#1936, thanks to @Plazzmex for reporting and @w1977-0 for the fix)attachment-expiry-durationis longer thancache-duration, since attachments never outlive their message (#1053, thanks to @ctschach for reporting)INSERTfor any batch size (#2011)ntfy publishfailing with "invalid header field value" when sending a multi-line message or title along with a file (#1808, thanks to @quantenzitrone for reporting)Documentation:
v2.29.0Compare Source
This release fixes cache writes under load. On ntfy.sh, hourly cron bursts overwhelmed the batch writer: messages took up to 40s to reach the database (so
poll=1andsince=missed them) and publishes stalled. Batches are now written in one statement, publishes no longer wait on the writer, and PostgreSQL connections stay idle instead of reconnecting.Features:
X-Timezoneheader,timezonequery param or JSON field; the web app sends the browser's timezone (#1967/#1924, thanks @beemines)At: 2026-12-10T11:00:00-05:00(#1931, thanks @ALPHACOM-Brehmer)Bug fixes + maintenance:
INSERTper batch, non-blocking publishes (100-batch buffer), and no scheduled-message lookup unless a sequence ID is set (#2006)ntfy servehandlesSIGTERM/SIGINTgracefullypool_max_idle_connsnow defaults topool_max_conns, so PostgreSQL connections are reused instead of re-openedsince=<message-id>replaying a topic's full history when the ID wasn't on the read replica yet; it's now resolved on the primarymessages_cachedinstead of aCOUNT(*)every minuteContent-Typehas parameters or is uppercase (#1995, thanks @cipherprofessor)0001-01-01end time and merged start/end lines (#1946/#1940, thanks @justadityaraj and @deferred)time/tzdata) so named time zones work on ARM Docker images and minimal runtimesv2.28.0Compare Source
This is a hardening release. A single topic on ntfy.sh was polled continuously with
poll=1and nosincecursor, which replays a topic's entire cache on every request. The changes below bound what one replay can cost, close two fields that had no size limit at all, and fix an ordering bug found while digging into it.Bug fixes + maintenance:
/topic1,topic2/json?poll=1, #1297)40057and40058). Neither field had a size limit before, unlike the message body; on ntfy.sh the 99.9th percentile is 212 bytes for titles and 244 for tagssincecursor returns a topic's entire cache, which was previously unbounded and could reach tens of megabytes on a busy topic, so one request could allocate that much on the server. The newest messages that fit are kept and a truncated response carries anX-Messages-Truncated: 1headervisitor-attachment-daily-bandwidth-limitnow also covers messages replayed from the message cache by poll requests, not just attachment traffic. A poll without asincecursor returns a topic's entire cache, so a topic that is cheap to fill can be re-read for many times its own size; polls beyond the budget are rejected with HTTP 429 (error code 42905) before anything is written. Note that heavy pollers now consume the same budget as attachment downloads, so operators serving both may want to raise the limitv2.27.0Compare Source
This release lets you sign in with your verified email address instead of your username, which should help if you ever signed up with an email and then forgot which username you picked. It also hardens the message templating engine against a few ways a small template could eat a lot of memory, and it drops the "experimental" label from PostgreSQL support, which has been running ntfy.sh for a while now.
I also did a bunch of refactoring in, mostly in preparation for being able to cluster ntfy nodes and scale the service horizontally. It'll be a while until then, ... baby steps.
Security:
Template: yes) to 32 KB, limitprintfwidths and precisions to below 1000, and limitindent/nindentto 100 spaces, preventing excessive memory use from a single small templateFeatures:
Bug fixes + maintenance:
twiliopackagemetricspackageuser_phonetable in the SQLite user database referencing a dropped table after the v2.14 schema migration; repaired automatically by a new migrationv2.26.3Compare Source
This is a hotfix release, useful pretty much only for ntfy.sh. It was adds the ability to track abusive IPs mor efficiently, reducing the load on the IP banning services and preventing them from falling behind and leaving abusers unbanned for too long. It works by tracking HTTP errors, and writing out a ban file that fail2ban can read and ban offenders instantly. See ban-feed for details.
Features:
ban-file, ntfy tracks a weighted strike budget per visitor and appends abusive IPs to a file that fail2ban can tail and ban on sight (ban-file,ban-window,ban-threshold,ban-weights; see ban-feed)v2.26.0Compare Source
This release hardens message templates, which are now executed with a hard-capped execution timeout. This closes
a denial-of-service hole.
On the web app side, it adds configurable date and time formats, a smoother loading and page-transition experience,
and a fix that strips unsafe URL protocols from rendered Markdown.
Security:
Template: yes), #1826, thanks to @alanturing881 for reporting)Features:
Bug fixes + maintenance:
GET /accountnow reads from the primary database instead of a read replica, so the account view no longer shows stale data right after a change when replicas lag behindjavascript:,data:, ...) from links and images in Markdown-rendered messages, so they no longer trigger an uncaught "React has blocked a javascript: URL" error (thanks to @jvoisin for reporting)v2.25.0Compare Source
This release adds password reset via email, and reworks email verification to use durable, link-based magic links (replacing the old in-memory 6-digit codes). Email stays optional at signup; a user can reset their password only once they have a verified "primary" (recovery)email.
All of this work is probably not useful for self-hosters, but it hopefully will be useful for me, since I do have to reset accounts on a regular basis.
Security issues:
crypto/rand) instead of a clock-seeded PRNGFeatures:
ntfy user reset-passCLI command for adminsX-Email: yestarget) with verified/unverified state in the account UIBug fixes + maintenance:
X-Email: yes(alsotrue/1) now sends to your primary verified email regardless of thesmtp-sender-verifysetting (previously it was rejected unless verification was enabled); it requires being logged in with a verified addressst_...) so cross-device subscription sync works underauth-default-access: deny-all(#733, #1795, thanks to @lmorchard for the contribution)<,>, and&as\u003c/\u003e/\u0026in JSON responses (#1511, #1512, thanks to @wunter8 for the contribution)v2.24.0Compare Source
The main feature for this release is an in-memory ACL cache (
auth-access-cache) that can help bring down the read load on the production database. The topic authorization queries are consistently the highest ranking queries on the database, so this will help quite a bit. The current database load is quite low, but I'm expecting it to increase as more users join and use ntfy.Security issues:
secretno longer also matches a request forSECRET. SQLite'sLIKEis case-insensitive for ASCII by default. PostgreSQL was unaffected. It's honestly incredible that this issue remained undetected for so long, especially while ntfy.sh was running on SQLite (it now runs on PostgreSQL).Features:
auth-access-cache) that serves topic authorization without a database round-trip; off by default, intended for high-volume serversntfy --versionflag to the CLI (#1722, #1748, thanks to @sskender for the contribution, and @Saucy9607 for reporting)Bug fixes + maintenance:
relattribute on auto-linked notification URLs sonoreferrer/noopenerare actually applied (#1720, thanks to @dmitrylyzo for the contribution)ntfy.serviceunit (#1467, thanks to @Velocifyer for the contribution)cmdpackage build on macOS (darwin) so the server compiles from source (#1631, #1696, thanks to @ShipItAndPray for the contribution, and @XYenon for reporting)v2.23.0Compare Source
Features:
visitor-topic-creation-limit-burst/visitor-topic-creation-limit-replenish, defaults 100 burst / 1m replenish) to mitigate topic-enumeration / squatting attacks that inflate the in-memory topic mapBug fixes + maintenance:
stacktrace-js,stacktrace-gps,humanize-duration, andjs-base64from the web app to reduce dependency and security footprintv2.22.0Compare Source
Bug fixes + maintenance:
v2.21.0Compare Source
This release adds the ability to verify email addresses using the
smtp-sender-verifyflag. This is a change that is required because ntfy.sh was used to send unsolicited emails and the AWS SES account was suspended. Going forward, ntfy.sh won't be able to send emails unless the email address was verified ahead of time.Features:
smtp-sender-verifyconfig flag, allowing server admins to require emailaddress verification before sending email notifications (#1681)
v2.20.1Compare Source
This is a small bugfix release that only affects high volume S3 backends that struggle with HTTP/2.
Bug fixes + maintenance:
disable_http2=trueS3 URL option to work around HTTP/2 stream errors with DigitalOcean Spaces and other S3-compatible providers (#1678/#1679)v2.20.0Compare Source
This release is another step towards making it possible to help scale ntfy up and out 🔥! With this release, you can store attachments in an S3-compatible object store as an alterative to the directory. See attachment store for details.
Features:
attachment-cache-dirconfig option (#1656/#1672)Bug fixes + maintenance:
v2.19.2Compare Source
This is another small bugfix release for PostgreSQL, avoiding races between primary and read replica, as well as to further reduce primary load.
Bug fixes + maintenance:
v2.19.1Compare Source
This is a bugfix release to avoid PostgreSQL insert failures due to invalid UTF-8 messages. It also fixes
database-urlvalidation incorrectly rejectingpostgresql://connection strings.Bug fixes + maintenance:
database-urlvalidation rejectingpostgresql://connection strings (#1657/#1658)v2.19.0Compare Source
This is a fast-follow release that enables Postgres read replica support.
To offload read-heavy queries from the primary database, you can optionally configure one or more read replicas using the
database-replica-urlsoption. When configured, non-critical read-only queries (e.g. fetching messages, checking access permissions, etc) are distributed across the replicas using round-robin, while all writes and correctness-critical reads continue to go to the primary. If a replica becomes unhealthy, ntfy automatically falls back to the primary until the replica recovers.Features:
database-replica-urlsconfig option (#1648)Bug fixes + maintenance:
v2.18.0Compare Source
This is the biggest release I've ever done on the server. It's 14,997 added lines of code, and 10,202 lines removed, all from one pull request that adds PostgreSQL support.
The code was written by Cursor and Claude, but reviewed and heavily tested over 2-3 weeks by me. I created comparison documents, went through all queries multiple times and reviewed the logic over and over again. I also did load tests and manual regression tests, which took lots of evenings.
ntfy.sh was successfully upgraded to 2.18.0 (though not with Postgres backend yet, as per the rollout plan).
I'm kindly asking the community to test the Postgres support and report back to me if things are working (or not working). There is a one-off migration tool (entirely written by AI) that you can use to migrate.
Features:
database-urlconfig option (#1114/#1619, thanks to @brettinternet for reporting)Bug fixes + maintenance:
<br>line breaks in HTML-only emails received via SMTP (#690, #1620, thanks to @uzkikh for the fix and to @teastrainer for reporting)v2.17.0Compare Source
This release adds support for templating in the priority field, a new "copy" action button to copy values to the clipboard,
a red notification dot on the favicon for unread messages, and an admin-only version endpoint. It also includes several
crash fixes, web app improvements, and documentation updates.
❤️ If you like ntfy, please consider sponsoring me via GitHub Sponsors, Liberapay, Bitcoin (
1626wjrw3uWk9adyjCfYwafw4sQWujyjn8),or by buying a paid plan via the web app. ntfy will always remain open source.
Features:
GET /v1/versionendpoint returning server version, build commit, and date (#1599, thanks to @crivchri for reporting)Bug fixes + maintenance:
http: response.WriteHeader on hijacked connectionfor WebSocket errors (#1362, thanks to @bonfiresh for reporting)slices.Containsfrom stdlib to simplify code (#1406, thanks to @tanhuaan)clear=trueon action buttons not clearing the notification (#1029, thanks to @ElFishi for reporting)versionfield from docker-compose examples (#1333, thanks to @seals187 for reporting and @cyb3rko for fixing)v2.16.0Compare Source
This release adds support for updating and deleting notifications, heartbeat-style / dead man's switch notifications, custom Twilio call format, and makes
ntfy servework on Windows. It also adds a "New version available" banner to the web app.This one is very exciting, as it brings a lot of highly requested features to ntfy.
Features:
updating and deleting scheduled notifications (#1556, #1142, #954, thanks to @GamerGirlandCo for the initial implementation)
ntfy servenow works on Windows, including support for running it as a Windows service (#1104, #1552, originally #1328, thanks to @wtf911)v2.15.0Compare Source
This release adds a
require-loginflag to topics, which forces users to log in before they can use the web app. This is useful for self-hosters and will obviously not be enabled on ntfy.sh.Features:
require-loginflag to redirect to login page if not logged in (#1434/#238/#1329, thanks to @theatischbein for implementing most of this)Bug fixes + maintenance:
database lockederrors (#1397, #1391, thanks to @timofej673)nopayments,nofirebaseandnowebpushto allow excluding external dependencies, useful forpackaging in Debian (#1420, discussion in #1258, thanks to @thekhalifa for packaging ntfy for Debian/Ubuntu)
v2.14.0Compare Source
This release adds support for declarative users, declarative ACL entries and declarative tokens. This allows you to define users, ACL entries and tokens in the config file, which is useful for static deployments or deployments that use a configuration management system.
It also adds support for pre-defined templates and custom templates for enhanced JSON webhook support, as well as advanced template functions based on the Sprig functions.
❤️ If you like ntfy, please consider sponsoring me via GitHub Sponsors, Liberapay, Bitcoin (
1626wjrw3uWk9adyjCfYwafw4sQWujyjn8), or by buying a paid plan via the web app. ntfywill always remain open source.
Features:
v2.13.0Compare Source
This is a relatively small release, mainly to support IPv6 and to add more sophisticated
proxy header support. Quick reminder that if you like ntfy, please consider sponsoring us
via GitHub Sponsors and Liberapay, or buying a paid plan via the web app.
ntfy will always remain open source.
Features:
X-Client-IP,X-Real-IP,Forwardedheaders for rate limiting viaproxy-forwarded-headerandproxy-trusted-hosts(#1360 / #1252, thanks to @pixitha)ntfy publish(#1382, thanks to @srevn)Languages
v2.12.0Compare Source
This is mainly a maintenance release that updates dependencies, though since it's been over a year, there are a few new features and bug fixes as well.
Thanks to everyone who contributed to this release, and special thanks to @wunter8 for his continued user support in Discord/Matrix/GitHub! You rock, man!
Features:
ntfy webpush --output-file(#1138, thanks to @nogweii)latestsubscription param for grabbing just the most recent message (#1216, thanks to @wunter8)NTFY_PASSWORD_HASHinntfy usercommand instead of raw password (#1340, thanks to @Tom-Hubrecht for implementing)v1/usersAPI (#1267, thanks to @wunter8 for implementing)ntfy-client.service(#1002, thanks to @dandersch)Bug fixes + maintenance:
Dateheader to outgoing emails to avoid rejection (#1141, thanks to @pcouy)cacheandfirebasevia JSON publishing (#1119/#1123, thanks to @stendler)Documentation:
Languages
Configuration
📅 Schedule: (in timezone Europe/Amsterdam)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate CLI.
Title
chore(deps): update docker non-major
PR Type
Dependencies
Description
Update Python and Rust Docker base images to latest minor versions.
Upgrade ntfy service image from v2.11.0 to v2.37.2.
Align tooling environments across anatomy, motion, and macOS builds.
Diagram Walkthrough
File Walkthrough
Dockerfile
Upgrade Python base image to version 3.15 slimtools/anatomy/Dockerfile
python:3.12-slimtopython:3.15-slim.Dockerfile
Upgrade Python base image to version 3.15 slimtools/motion/Dockerfile
python:3.10-slimtopython:3.15-slim.docker-compose.yml
Upgrade ntfy notification service to version 2.37.2docker-compose.yml
v2.11.0tov2.37.2.Dockerfile.macos
Upgrade Rust base image to version 1.99 bookwormrelease/Dockerfile.macos
rust:1.85-bookwormtorust:1.99-bookworm./review
PR Reviewer Guide 🔍
Here are some key observations to aid the review process:
🧹 Lint report · ✅ all 25 checks clean
Errors below fail this check.
✅ Clean: black, checkstyle, djlint, editorconfig-checker, git_diff, gitleaks, grype, hadolint, htmlhint, isort, jsonlint, markdownlint, npm-groovy-lint, pmd, prettier, prettier, ruff, secretlint, shellcheck, shfmt, stylelint, trivy, trufflehog, xmllint, yamllint
MegaLinter on soucouyant · full logs in the Actions run · comment
/improvefor AI fix suggestions