Skip to content

OpenConceptLab/ocl_issues#2348 | Expansions newer repo version from resolved view - #26

Merged
snyaggarwal merged 1 commit into
mainfrom
issues#2348
Jun 18, 2026
Merged

OpenConceptLab/ocl_issues#2348 | Expansions newer repo version from resolved view#26
snyaggarwal merged 1 commit into
mainfrom
issues#2348

Conversation

@snyaggarwal

Copy link
Copy Markdown
Contributor

Linked Issue

Refs OpenConceptLab/ocl_issues#2348

Summary

Resolved Repo Updates Warning in Versions + Expansions Tab

What changed

  • Added a new API call to /<version>/expansions/<mnemonic>/resolved-repo-updates/ which returns a map of outdated repo versions to their latest available versions.
  • Eager fetch: On tab load, this API is called for all expansions of HEAD and the latest released version.
  • Lazy fetch: When any other version is expanded by the user, the API is called for all its expansions that haven't been fetched yet.
  • Both HEAD and latest released versions are auto-expanded on page load if any of their expansions have available updates.
  • A dismissible MUI Alert (warning/orange) is shown under each expansion that has updates, listing the outdated → latest version pairs as clickable links (open in new tab). A Compare link with an external icon is also shown for each pair.
  • All of the above is only visible to users with access to create expansions (currentUserHasAccess()), and the API call is also skipped for users without access.
  • [BUG FIX] Resolved repo version labels in the Explicit/Evaluated Repo Versions columns are now clickable links (open in new tab)

Screenshot:
Screenshot 2026-06-17 at 13 33 28

@jamlung-ri

jamlung-ri commented Jun 17, 2026

Copy link
Copy Markdown
Member

Testing notes — tested against local API (http://localhost:8000) using TESTORG/TestSource (5 released versions: concept renames, new concepts, new mapping) and TESTORG/TestCollection (expansion pinned to v1/v2).

Confirmed working:

  • resolved-repo-updates API returns {} when expansion is already at the latest released version ✓
  • Returns correct {old_version → latest_version} map after a new source version is released; updates accurately across successive releases ✓
  • Warning alert appears in Versions + Expansions tab and reflects current staleness on each page visit ✓
  • HEAD and latest released version auto-expand on page load when updates exist ✓
  • Lazy fetch fires when manually expanding other versions ✓
  • Alert is dismissible (Snooze) ✓
  • Resolved repo version labels in Explicit/Evaluated columns are now clickable links (bug fix) ✓
  • Compare link opens the correct version diff ✓

Pending:

  • Access control (alert + API call skipped for users without create-expansion access) — @snyaggarwal how about we deploy to QA and I'll test this there?

@jamlung-ri jamlung-ri left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm happy with this. My only untested feature is the permissions aspect e.g. seeing the banner as a non-author user. That'll be easier for me to test on QA or Prod. Otherwise, everything worked as expected!

@snyaggarwal
snyaggarwal merged commit 87df1bf into main Jun 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Implement collection dependency change notifications

2 participants