You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add per-admin hide of latest features nav bar list item #987
Each admin should be able to hide and show the latest features which will automatically reenabled when the system is updated. > store in user settings.
Each user should be able to hide and show the latest features which will automatically reenabled when the system is updated. > store in user settings.
Implemented the versioned Latest Features navigation hide preference for this issue.
Summary:
Added per-user latestFeaturesHiddenVersion support so Latest Features nav entries stay hidden only for the current app version.
Applied the hide behavior to both user-facing Support > Latest Features entries and the admin sidebar Admin Settings > Latest Features entry.
Added Profile Settings restore controls and local static JS for the ellipsis hide actions.
Added is_development=true as a development-only env override that hides the nav entries when explicitly true; unset/false/non-true values do not affect normal behavior.
Bumped the app version to v0.250.058 and added release notes.
Validation:
Python compile passed for changed Python and test files.
ui_tests/test_latest_features_nav_hide_preference.py ran but skipped because local SIMPLECHAT_UI_BASE_URL and authenticated Playwright storage state were not configured.
Security notes:
No changed paths matched .env, secret, token, session, connection-string, storage-key, or generated local artifact patterns.
Route decorator/policy, XSS, and broken-access-control checks passed.
Closing as completed. This issue stayed open after the fix merged because pull requests target Development while the repository default branch is main, so GitHub never applied the Fixes # keyword automatically.
Activity
paullizer commentedon Jul 2, 2026
lol
Bionic711 commentedon Jul 20, 2026
Implemented the versioned Latest Features navigation hide preference for this issue.
Summary:
latestFeaturesHiddenVersionsupport so Latest Features nav entries stay hidden only for the current app version.is_development=trueas a development-only env override that hides the nav entries when explicitly true; unset/false/non-true values do not affect normal behavior.Validation:
node --check application/single_app/static/js/latest-features-nav.jspassed.functional_tests/test_latest_features_nav_hide_preference.pypassed.functional_tests/test_admin_latest_features_tab.pypassed.functional_tests/test_latest_features_action_links.pypassed.ui_tests/test_latest_features_nav_hide_preference.pyskipped cleanly when no authenticated Playwright storage state was configured.git diff --checkpassed.Bionic711 commentedon Jul 20, 2026
PR-readiness update for the Latest Features navigation hide preference work.
Summary:
feature/hide_latest_featurescontains the latestorigin/Development.config.pyversion0.250.059.docs/explanation/features/LATEST_FEATURES_NAVIGATION_HIDE_PREFERENCE.md.783db97c docs: align latest features PR readiness assets.Validation passed:
git diff --check origin/Development...HEADgit diff --checkapplication/single_appand changed testspython scripts/check_swagger_routes.pyfor changed Python route/application filesnode --check application/single_app/static/js/latest-features-nav.jsfunctional_tests/test_latest_features_action_links.pyfunctional_tests/test_latest_features_nav_hide_preference.pySkipped/gap:
ui_tests/test_latest_features_nav_hide_preference.pyran but skipped because localSIMPLECHAT_UI_BASE_URLand authenticated Playwright storage state were not configured.Security notes:
.env, secret, token, session, connection-string, storage-key, or generated local artifact patterns.paullizer commentedon Aug 19, 2026
Shipped in v0.250.059 via #1051.
Release note entries:
Full notes: https://microsoft.github.io/simplechat/explanation/release_notes/
Closing as completed. This issue stayed open after the fix merged because pull requests target
Developmentwhile the repository default branch ismain, so GitHub never applied theFixes #keyword automatically.