feat(ui): Add warning signpost for old snaps

[gajeshbhat]

Done

Adds a warning notification on snap detail pages for snaps that haven't been updated in over 2 years, helping users identify potentially outdated or unmaintained snaps.

Fixes #2988

Changes

• Backend Logic: Added is_snap_old() function to detect snaps older than 2 years
• Date Formatting: Added convert_date_month_year() for cleaner "Month Year" format
• UI Component: Added warning notification in snap details sidebar with orange left border
• Styling: Custom CSS for clean notification appearance (no borders except orange left border)
• Testing: Comprehensive test coverage for date logic and edge cases

Implementation Details

• Threshold: Configurable (default: 2 years)
• Message: "This snap in this channel hasn't been updated since [Month Year]. Contact the developer to ask for an update."
• Positioning: Appears after "Last Updated" section in sidebar
• Styling: Uses Vanilla CSS p-notification--caution with custom .old-snap-warning class

How to QA

Unit Testing

• All existing tests pass
• New tests added for is_snap_old() function
• New tests added for convert_date_month_year() function
• Manual testing completed on local development server

Prerequisites

• Checkout to my Branch: feat/signpost-old-snaps-2988
• Run the development server locally: dotrun

Test Cases

Snaps that SHOULD show the warning (2+ years old):

• Visit http://localhost:8004/mumble - Should show a warning
• Visit http://localhost:8004/hello - Should show a warning
• Visit http://localhost:8004/wekan - Should show a warning

Snaps that should NOT show the warning (recently updated):

• Visit http://localhost:8004/vault - Should NOT show warning
• Visit http://localhost:8004/microk8s - Should NOT show warning

What to Look For

1. Warning Appearance:

   • Orange left border (no other borders)
   • Warning icon
   • Clean, minimal styling
   • Horizontal line below for consistency

2. Message Format:

   • "This snap in this channel hasn't been updated since [Month Year]. Contact the developer to ask for an update."
   • Month and year only (no specific day)

3. Positioning:

   • Appears in right sidebar
   • After "Last Updated" section
   • Before "Contact" section (if present)

Edge Cases to Test

• Try snaps with different update dates
• Verify warning only appears for snaps 2+ years old
• Check that recent snaps don't show the warning

Screenshots

Screenshots are attached below showing:

Warning displayed on old snaps (mumble, hello, wekan)

No warning on recently updated snaps (vault, microk8s)

Notes

• The feature is backward compatible and doesn't affect existing functionality
• Uses timezone-aware datetime functions to avoid deprecation warnings
• Follows existing design patterns and styling conventions
• The message can be easily customized by modifying the template

[webteam-app]

gajeshbhat is not a collaborator of the repo

[bartaz]

Thanks again @gajeshbhat. I'll pass it through copilot first and we'll add it to our maintenance review list.

With feature requests like this, we usually get them through UX first, before even starting implementation. While your suggestion is OK, it hasn't been decided where such notification should be added, what should it say, how old snap needs to be for it to show up.

That said, we can use your PR to discuss these with UX during review.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (b8b6b55) to head (509c41a).
⚠️ Report is 638 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #5352       +/-   ##
==========================================
- Coverage   66.80%       0   -66.81%     
==========================================
  Files         113       0      -113     
  Lines        3714       0     -3714     
  Branches      965       0      -965     
==========================================
- Hits         2481       0     -2481     
+ Misses       1098       0     -1098     
+ Partials      135       0      -135     

see 61 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull Request Overview

This PR adds a warning notification system for snap packages that haven't been updated in over 2 years, helping users identify potentially outdated or unmaintained snaps.

• Added backend logic to detect old snaps and format dates appropriately
• Implemented UI notification component in the snap details sidebar
• Added comprehensive test coverage for the new functionality

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
webapp/store/snap_details_views.py	Integrates old snap detection into snap details context
webapp/store/logic.py	Implements core functions for detecting old snaps and date formatting
tests/store/tests_public_logic.py	Adds comprehensive test coverage for new date and old snap logic
templates/store/snap-details/_details.html	Adds warning notification UI component to snap details sidebar
static/sass/styles.scss	Adds custom styling for the old snap warning notification

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[gajeshbhat]

Thanks again @gajeshbhat. I'll pass it through copilot first and we'll add it to our maintenance review list.

With feature requests like this, we usually get them through UX first, before even starting implementation. While your suggestion is OK, it hasn't been decided where such notification should be added, what should it say, how old snap needs to be for it to show up.

That said, we can use your PR to discuss these with UX during review.

Thanks for taking a look @bartaz . Yes, I do remember seeing the Dev Ready label on some issues where the UX had been discussed, but as this is a minor change, I assumed that could be done during the PR review. Apologies for not checking early. Happy to work with UX to decide the place, the message and duration to display the warning. Will resolve other comments and wait for the suggestions on this. Thanks for pointing it out. Cheers.

[gajeshbhat]

Hey @bartaz , Hope you have been well. Any chance we can get a review from UI/UX for this PR ?

[gajeshbhat]

Retriggerd CI using git commit --amend --no-edit && git push --forceand the Inclusive naming check passes now.

[gajeshbhat]

@bartaz @edisile Any chance UI/UX can review this ? Happy to answer questions or help update the PR if required.

[edisile]

Hi there! Thanks for reaching out and sorry for taking so long to reply. Unfortunately we couldn't get a proper formal UX review, but we received some informal comments I reported here along with a few things I noticed

[gajeshbhat]

Hi there! Thanks for reaching out and sorry for taking so long to reply. Unfortunately we couldn't get a proper formal UX review, but we received some informal comments I reported here along with a few things I noticed

Thank you @edisile for taking the time to review this PR. I have made some changes based on the review feedback. As changes are not of larger scope, I think a minor UX comment should suffice instead of the full review. Please let me know if you have any question. Cheers.

1. CI check for test-python is failing. I ran this test locally on upstream/main and it is failing as well. Let me know if you folks fix it, I will rebase/
2. Inclusive naming check fails intermittently. I have raised a ticket for this before on this repo (Intermittent Failure in canonical/inclusive-naming@main Action #5531 (comment)) and the original repo that hosts this check
3. Black linter was throwing errors (https://github.com/canonical/snapcraft.io/actions/runs/21775757077/job/62831944315) on CI (after rebase, on files I did not touch), I ran the linter locally and updated the lint checks and now its passing.

On a side note, I also have similar smaller UI feature PR that's been waiting for a while now, if you can kindly take a look, that would be helpful : #5353 . Thanks again and Cheers.

[edisile]

@gajeshbhat thank you! The tests should work now if you rebase on main

[edisile]

Looks good!

[gajeshbhat]

Looks good!

Thank you.

requested change has already been addressed