This is the released version. It contains its own change plus the two entries below it,
v1.26.2170811 and v1.26.2170748, which were developed and deployed the same day and never got
releases of their own. Upgrading from v1.26.2141433 gets all three.
The report footer now credits Newsflasharr, the plugin that emails it. Newsflasharr already
wrote that credit into the body of the email; carrying it in the page as well means it survives
the page being saved, forwarded, or opened from disk with no mail around it. The sibling Lineuparr
plugin already did this and Channel Maparr did not.
The line reads "Emailed copies of this report are delivered courtesy of Newsflasharr". The wording
is about emailed copies rather than about the copy in front of you, on purpose: a report read
straight from the report directory was never delivered by anything, and a page thanking a
deliverer that had not run would be saying something untrue about itself.
The footer also now names the plugin and puts the source and issue links on one line.
Nothing else changed, and the page still fetches nothing from the network. The set of addresses
the page may link to is pinned by a test, so a link cannot be added to the footer without somebody
deciding to add it to that list as well.
v1.26.2170811 (August 5, 2026)
The HTML report looks different. It says exactly the same things. No column was added,
removed or renamed, and no number changed. This is presentation only.
- The rows now sit in a section that starts collapsed. The page opens as an index: the title,
the run summary, then one closed section headed with a coloured dot, the word Results and the
row count. Click the heading to expand it. The section uses the browser's own disclosure
element rather than JavaScript, so a mail client that does not support it shows everything
expanded instead of hiding it. Because a collapsed section is invisible to find-in-page in some
browsers, the section says so. - Every colour now comes from a named token, with a matching value for dark mode. Four
consequences you may notice: the light and dark themes are now consistent with each other;
zebra striping on table rows now appears in both themes, where before it was declared for
dark mode only and the two themes rendered visibly different tables; text that used to be faded
with transparency now uses a measured grey, which keeps its contrast readable whatever it sits
on; and spacing comes from one scale instead of fourteen hand-picked values. - The logo now appears beside the title, embedded in the page so it still shows when the
report is opened from disk or read as an email attachment. This adds one file to the plugin,
logo_report.png, which is a smaller copy made for this purpose. The plugin card's own logo
is unchanged. The report grows by about 16 KB; embedding the existing card logo would have
added 288 KB, which is seven times the size of a whole report. - A footer links to the project and its issue tracker. Nothing is fetched from the network:
the page requests no stylesheet, font or image from anywhere, exactly as before.
The report is still one self-contained file, still sortable by clicking a column heading, and
still carries the same note about what is and is not included in it.
v1.26.2170748 (August 5, 2026)
Channel Maparr now publishes a count of the reports it has built, so the Newsflasharr plugin's
Show Status action can display it. Newsflasharr already lists every plugin that sends it
reports; until now this plugin appeared in that list with no number beside it, because it did not
write the file the number comes from.
- New file:
/data/channel-mapparr/report_count.json, containing one key,reports_built,
holding one non-negative integer. It is written atomically, so a reader never sees a partial
file, and it is private to the account the plugin runs as. - The number counts report BUILDS, not emails and not deliveries. One increment means one HTML
file and one CSV file were both written to disk. Two consequences worth knowing: if the report
format is set to Both, one build sends two emails, so this number will be half the number of
emails you received; and a report that was built but whose email later failed still counts,
because the file was written. - A build that failed to write does not increment it. That is the point of the file. The
report writer reports a failure rather than raising, so without this rule a failed publish would
be indistinguishable from a successful one. - Nothing else changes. The counter cannot fail a report run: if it cannot be written, the
report is still built and the email is still queued, and the reason is written to the
Dispatcharr log as a warning.
Note for anyone verifying this by hand: do not create /data/channel-mapparr yourself.
docker exec runs as root by default, and a root-owned directory there can never be written by
the plugin afterwards. Let the plugin create it.