Skip to content

October 2026 Release 3 - #7291

Merged
jmgasper merged 8 commits into
masterfrom
develop
Oct 21, 2026
Merged

jmgasper merged 8 commits into
masterfrom
develop

Conversation

@jmgasper

Copy link
Copy Markdown
Collaborator
  • PM-6066
  • PM-6583
  • PM-6601
  • PM-6628

What was broken
The Marathon Match Local Tester Parameters article displayed literal <
and > entity names in its javac and jar command examples.

Root cause
Community App still serves the public article. Its Markdown renderer passed
decoded text tokens through the HTML sanitizer before React escaped them
again, producing double-escaped angle brackets.

What was changed
Pass parsed text tokens directly to React so they are escaped exactly once.
Update the renderer documentation to explain text handling. Keep the fix
limited to Community App's text-token path and its regression tests.

Any added/updated tests
Add DOM and serialized-HTML regressions for the article's two commands,
literal entity names, and escaped script/image examples remaining text.
Verified the command regression fails before the fix.

Validation: npm test passed, including JavaScript/SCSS lint, the retired-CMS
target check, 456 tests, and 141 snapshots (23 existing test skips).
npm run build and git diff --check passed using Node v10.24.1 via nvm use.
What was broken
The previous fix restricted anonymous signing in community-app, while QA requires
signing to happen in platform-ui's Opportunities app going forward.

Root cause
Existing direct terms links still mounted community-app's signing container.

What was changed
Redirect legacy terms links to the environment-specific Platform UI Opportunities
terms page, preserving the term ID, query, and fragment. Retain the prior login
and unauthorized-response guards as defense in depth. Deploy the Opportunities
page before enabling this redirect.

Any added/updated tests
Add four legacy-route regressions and retain the nine authentication regressions
from the prior fix. npm run lint and npm run build passed. npm test passed with
170 suites, 466 tests, and 141 snapshots; four suites and 23 tests remain skipped.
PM-6066: Redirect legacy terms signing to Opportunities
PM-6601: Fix angle brackets in Marathon Match article
What was broken
The Veterans community page rendered without its styles and client scripts,
leaving unformatted content and oversized icons.

Root cause
The public CDN redirects static assets to community-app.topcoder.com, but
that destination was absent from the community Content-Security-Policy
script, style, font, and image source lists.

What was changed
Allow the configured community application's static-asset endpoint in those
four directives and document the server setup behavior. Preserve the
existing policy scope and other restrictions.

Any added/updated tests
Add eight middleware regression cases covering Veterans routes, the shared
TCO policy, unrelated pages, and the CMS example frame policy. The six
asset-policy cases failed before the fix and pass afterward.

Validation: yarn lint, yarn test (477 passed, 23 already skipped; 141
snapshots passed), and yarn run build passed under Node 10.24.1. Desktop
and mobile browser checks using the updated response policy restored the
page styling and confirmed that static-asset redirects are no longer
blocked by CSP.
PM-6583: Restore Veterans community asset loading
What was broken

MM submission history and artifact dialogs used legacy layouts. History lacked
working artifact navigation, Download all was unavailable, and Community App
modals used the old backdrop and container shadows.

Root cause

The dialogs retained separate legacy markup and styles, and the shared Modal
defaults had not been updated for the new design system.

What was changed

Add the MM history table with submission IDs, sortable dates, member handle,
score states, and artifact actions. Restyle artifacts with submission metadata,
example-only access before completion, and a single ZIP download after
completion. Reuse API authorization and the existing ZIP utility, surface
request failures, and apply a 50% black backdrop without shadows to shared
Community App modals. Document the shared defaults and download helpers.

Any added/updated tests

Add 17 regression tests covering artifact visibility, individual and bulk
downloads, failure handling, history sorting and navigation, and shared themes.
All 494 tests and 141 snapshots pass; 23 previously skipped tests remain skipped.
Lint and the production build pass. Headless browser checks with mocked API
responses verify desktop/mobile layouts, modal transitions, backdrop styles,
and an actual ZIP containing all four artifacts.
PM-6628: Refresh Marathon Match submission modals
@jmgasper
jmgasper requested a review from kkartunov as a code owner October 21, 2026 22:21
@jmgasper
jmgasper merged commit 43078aa into master Oct 21, 2026
10 of 12 checks 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.

1 participant