Prepare v0.28.1 maintenance release #265
No reviewers
Labels
No labels
code-review
correctness
dos
performance
security
severity/high
severity/low
severity/medium
tech-debt
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
h-dv/code-index!265
Loading…
Reference in a new issue
No description provided.
Delete branch "release/0.28.1"
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?
The fixes merged in #264 are not yet in the published v0.28.0 release. This prepares v0.28.1 by updating the workspace version, all four affected lockfiles, and the README’s release and pinned-installer links. Independently versioned guest packages and external dependencies are unchanged.
Validation: formatting and parsed lockfile comparison verify that only the 13 workspace packages and their three guest-lockfile references move. Linux workspace, daemon transport, corpus, Clippy, MSRV, ABI, dependency and documentation CI are green on
340a75a. Native Windows CI is green too, including the debug shipped-set smoke and release-profile worker smoke. A fresh build and Django index reproduce the #246 residual described below. Publication uses the existing required-CI gate and archive smoke checks.Issue closure follows verification of the published artifacts. Final source-site verification found that #246’s two real Django User.email false bindings survive: a local User rebinding in an unrelated function suppresses import evidence for the entire file. The smaller regression fixture passed without covering that shape. Release notes explicitly retain #246 for a follow-up, alongside #250’s remaining receiver chain and #263’s historical acceptance evidence.
answer_provenancewas byte-identical: nothing says which generation answered #245claim_domain_scalemoved ONE wall-clock ratio to#[ignore]and left its sibling live — the sibling is a FLOOR, which contention breaks in the direction a floor cannot survive #253answer_provenancenames a commit the INDEX has not reached, so a watcher-lag miss and a measured absence are indistinguishable #260install.shas a release asset, so an installer can be pinned to a release instead of tracking master #261code-index-plugin-hostcannot say which build it is — three of four shipped binaries answer--version, the fourth exits 21 with usage #262django/utils/{inspect,html}.py) #251