fix: correct eight stale changelog dates and sitemap lastmod - #181
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
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
Identified debt, not addressed here
Recording this so it is not lost, none of it is in scope for a docs-only fix:
app/window.py:240points atnelsonduarte.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.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-78contradicts what is actually published. It states Windows downloads are exclusive to the Microsoft Store, butPDFAppsSetup.exeships as a release asset. Needs an editorial decision.sitemap.xmlor the changelog dates. Two tests proposed for the backlog: validatelastmodformat, 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_requesttomain, no path filter).security-deps.ymlis path-filtered to requirements files and does not run.build.ymlneeds av*tag,publish.ymlneeds a published release, andrelease.ymlisworkflow_dispatchonly.🤖 Generated with Claude Code