chore: sync main into DEV (reconcile hotfixes #2081 + #2083) - #2084
Merged
Conversation
Release 1.20.1 → PROD
…lery/tags before Hugo bake The content rebuild only fetched a subset of build:all's feed chain (tutorials, advocates, homepage-shelves, verb/shelf-definitions), so the page-index BLOB was baked from the STALE committed data files. The homepage 'Explore' topic-clusters band rendered tutorials-only because the committed hugo/data/topic_clusters.json had empty items[] since 2026-07-25 and no rebuild path ever regenerated it. Add the four missing fetchers so every rebuild bakes from live backend data. Also refresh the committed topic_clusters.json snapshot (mixed items from the prod backend).
…age-feeds fix(rebuild-content): fetch topic-clusters/featured-topics/topics-gallery/tags so homepage bands bake fresh
…-action FQN The #2060 editable Feature Flags UI wired the enable/disable buttons as Action: 'AdminService.FeatureFlags/enable' — the <qualifier>/<name> slash form is OData v4 UNBOUND ActionImport syntax, but enable/disable are BOUND actions on the FeatureFlags entity. Fiori Elements throws 'Unknown action import' client-side and never sends the POST, so the buttons do nothing (shipped in 1.20.1). Use the bound-action FQN AdminService.enable / AdminService.disable.
…action fix(admin): Feature Flags Enable/Disable buttons (Unknown action import)
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
1 participant
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.
Why
Two fixes were merged directly to
main(wrong target — PRs should go to DEV) and are now live on PROD but absent from DEV, which currently sits strictly behind main:rebuild-content.ymlfetches topic-clusters/featured-topics/topics-gallery/tags + freshtopic_clusters.json(fixes homepage Explore clusters).Without this back-merge, the next DEV deploy would regress both (DEV's
rebuild-content.ymllacks the fetchers; DEV's admin annotations keep the broken action refs).What
Back-merges
origin/main(51ac0bc) into DEV. DEV has 0 commits main lacks, so this is a clean catch-up. Mirrors the #2059 reconcile pattern. No content/behavior changes beyond the two fixes.Going forward: feature/fix PRs target DEV; DEV→main promotion at release time.