Repository navigation
fix(programs): restore public access to published legacy projects - #836
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Finished legacy programs with publication enabled could show a disabled projects-participants button, while their existing project list was restricted to managers. Add a separate read-only published-projects endpoint and a server capability in program details so the frontend can open that list safely.
The reader returns only public, non-draft linked projects after the program ends with publication enabled. It supports both existing link sources, search and bounded pagination. GET does not publish or modify projects. Private manager lists, filters and exports retain their existing permissions. No migrations or changes to existing program settings.
Validation: 9 tests passed on isolated PostgreSQL, covering the public reader, publication rules, both link sources, search/pagination, unchanged private permissions and existing publication behavior.
Deploy backend before the paired frontend correction.