Skip to content

fix: correct eight stale changelog dates and sitemap lastmod - #181

Merged
nelsonduarte merged 1 commit into
mainfrom
fix/site-stale-dates-and-sitemap
Sep 13, 2026
Merged

nelsonduarte merged 1 commit into
mainfrom
fix/site-stale-dates-and-sitemap

Conversation

@nelsonduarte

Copy link
Copy Markdown
Owner

Mechanical content corrections to the public site. No code paths touched, no version change, no tags.

Changelog dates

Eight release dates on the public changelog had drifted from the actual git tags. Each was verified against the tag commit date and corrected:

Version Was Now Off by
v1.13.17 June 21 June 28, 2026 7 days
v1.13.15 June 14 June 5, 2026 9 days
v1.13.14 June 7 June 4, 2026 3 days
v1.13.13 May 31 June 4, 2026 4 days
v1.13.12 May 24 May 17, 2026 7 days
v1.13.11 May 17 May 10, 2026 7 days
v1.13.9 April 22 May 8, 2026 16 days
v1.8.3 April 6 April 5, 2026 1 day

The worst was v1.13.9, wrong by 16 days.

Chronological inversion fixed

The stale dates produced a visible ordering bug: v1.13.15 was dated June 14 while v1.13.14, listed below it, was dated June 7. An older release appeared to have shipped after a newer one. After the corrections the date column is monotonically non-increasing down the page across all 24 entries.

v1.13.13 and v1.13.14 share a date on purpose

Both now read June 4, 2026. This is correct and not an accidental tie: the tags are about 42 minutes apart on the same day, at 15:27:48Z and 16:10:02Z respectively.

Sitemap lastmod

Refreshed only where truthful. Home, download and changelog moved to 2026-09-12 because their visible content actually changed. The remaining three entries stay in July deliberately: their only edit was a footer link, which is not a content update worth re-advertising to crawlers.

Verification

  • Full suite: 746 passed, 2 skipped
  • Changelog footer remains v1.15.0; no version string touched anywhere
  • Line endings verified at byte level in working tree, index and committed blob: CRLF in tree, normalized to pure LF in the blob, zero bare CR

Identified debt, not addressed here

Recording this so it is not lost, none of it is in scope for a docs-only fix:

  • The app Help button opens a dead domain. app/window.py:240 points at nelsonduarte.github.io/PDFApps/#guide, which has not served since the migration to Cloudflare Pages. This is shipped in 1.15.0 and is app code, so it needs its own task.
  • The same dead domain survives in eight packaging manifests: aur/pdfapps/PKGBUILD:7, aur/pdfapps/.SRCINFO:5, aur/pdfapps-bin/PKGBUILD:8, aur/pdfapps-bin/.SRCINFO:5, snap/snapcraft.yaml:22, rpm/pdfapps.spec:7, winget/nelsonduarte.PDFApps.locale.en-US.yaml:9.
  • docs/download.html:77-78 contradicts what is actually published. It states Windows downloads are exclusive to the Microsoft Store, but PDFAppsSetup.exe ships as a release asset. Needs an editorial decision.
  • The OCR description claims five languages, but the app accepts any language the user has installed in Tesseract.
  • 24 tagged releases have no changelog entry.
  • Five packaging manifests still say "13 built-in tools" (actual count is 15).
  • No test covers sitemap.xml or the changelog dates. Two tests proposed for the backlog: validate lastmod format, and assert the changelog date column is monotonically non-increasing. The second would have failed on the old content, so it is demonstrably discriminative.

CI

This PR touches only docs/, served by Cloudflare Pages. Of the five workflows, only CodeQL triggers (pull_request to main, no path filter). security-deps.yml is path-filtered to requirements files and does not run. build.yml needs a v* tag, publish.yml needs a published release, and release.yml is workflow_dispatch only.

🤖 Generated with Claude Code

The public changelog carried hand-written release dates that had drifted from
the actual git tags. All eight were verified against the tag commit dates and
corrected:

  v1.13.17  June 21 -> June 28, 2026
  v1.13.15  June 14 -> June 5, 2026
  v1.13.14  June 7  -> June 4, 2026
  v1.13.13  May 31  -> June 4, 2026
  v1.13.12  May 24  -> May 17, 2026
  v1.13.11  May 17  -> May 10, 2026
  v1.13.9   April 22 -> May 8, 2026
  v1.8.3    April 6 -> April 5, 2026

The worst offender was v1.13.9, wrong by 16 days.

These errors also produced a visible chronological inversion: v1.13.15 was
dated June 14 while v1.13.14 below it was dated June 7, so an older release
appeared to have shipped after a newer one. With the corrections the date
column is monotonically non-increasing down the page across all 24 entries.

v1.13.13 and v1.13.14 now both read June 4, 2026. That is correct and not an
accidental tie: the two tags are roughly 42 minutes apart on the same day
(15:27:48Z and 16:10:02Z), so they genuinely share a release date.

Sitemap lastmod values were refreshed only where they are truthful. The home,
download and changelog pages moved to 2026-09-12 because their visible content
changed. The other three entries stay in July on purpose, since the only edit
they received was a footer link, which is not a content update worth
re-advertising to crawlers.

No version strings were touched; the changelog footer remains v1.15.0.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@nelsonduarte
nelsonduarte merged commit c6f98d3 into main Sep 13, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant