KinKudos

VERSIONS

Changelog

See what was added and fixed in every application version.

v26.4.7

What's new?

No new features in this release.

What's fixed?

  • Landing, parent sign-in, and password-reset screens now share a lighter, gradient-based visual design without additional image assets.
  • The GitHub README now offers a visual product overview, demo-first onboarding, concise deployment guidance, and an optional VPS recommendation.
  • The child lottery card and purchase dialog now use the clearer โ€œLottery ticketsโ€ label.
  • Backup provider detection now parses the configured S3 repository hostname instead of matching an arbitrary URL substring.

v26.4.6

What's new?

No new features in this release.

What's fixed?

  • The README now links to the public demo and provides its parent and child sign-in details.
  • Lithuanian feedback settings no longer imply a contrast between saving feedback and unavailable email notifications.

v26.4.5

What's new?

No new features in this release.

What's fixed?

  • Parents now receive a Web Push notification when a child requests a reward.
  • Web Push now also covers child suggestions and birthday-date change requests, along with the resulting parent decisions sent back to the child.

v26.4.4

What's new?

No new features in this release.

What's fixed?

  • Deployment documentation now covers preparing a fresh Ubuntu server with Docker Engine, Docker Compose, GitHub CLI, and a Caddy HTTPS proxy before running the KinKudos installer.
  • Disabled IP restrictions now use the red inactive-state treatment, while enabled restrictions remain green.
  • The feedback administration panel uses the same inner alignment as other settings panels and leaves consistent space below its explanation.
  • Feedback screenshot controls inherit the shared interface typography instead of using the browser's mismatched default button font.

v26.4.3

What's new?

No new features in this release.

What's fixed?

  • Child-device pairing links can now be confirmed in Safari without a CSRF 403 response. The pairing page preserves the same-origin referrer Django requires while keeping the one-time token in the URL fragment.