Skip to content

Update changelog for deprecation marker cache #493

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thomashoneyman merged 1 commit into from
Jul 6, 2026
Merged

Update changelog for deprecation marker cache #493

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,6 +70,16 @@ the most up-to-date version of this file.
directory directly. Responses are now written to a temporary file and
renamed into place, which is atomic; the same flood now returns no errors.

- Avoid decoding the latest package version just to render deprecation badges
on old-version package pages (@thomashoneyman)

Package and module documentation pages display a deprecated badge when the
latest package version is marked with the `pursuit-deprecated` keyword.
Old-version pages previously decoded both the requested version and the
latest version's full docs JSON to compute that one boolean. They now cache
a tiny version-stamped deprecation marker per package, so after the first
marker miss these renders decode only the requested package version.

## v0.9.11

- Serialise decoding of large package files (@thomashoneyman)
Expand Down
Loading