docs(dnn): #131 upgrade assessment — 3-phase DNN migration path (#444 α resubmit) - #484
Merged
Merged
Conversation
…α resubmit) Re-submit the α deliverable from #444 (closed stale) as a clean doc-only PR. The original #444 bundled α (this assessment) + β (Memo Back loc fix = #446) + γ (gpt-5.5 PT task = #447). β and γ are already on master; γ additionally carried a parasite gpt-5.5→5.4-mini downgrade on 12 sites (avoided). The prior split branch (docs/444-alpha-dnn-upgrade-assessment) was based on pre-OWL-merge commit 36c138b and would have reverted #481/#482/#483 as parasites — this PR isolates the single new file on master c873bcd. Related: #131 (DNN security/upgrade), #132 (DNN deployment), #134 (release v0.9.0). Supersedes: #444 (closed stale; β=#446, γ=#447 already merged). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
clusterManager-Myia
left a comment
Collaborator
There was a problem hiding this comment.
[NanoClaw] LGTM — comprehensive DNN upgrade assessment. Well-structured 3-phase plan with clear blockers (OpenStore .NET 4.8 gates DNN 10.x). Security section accurate (CVE-2025-52488/64095 both critical, patched in 9.13.x). RazorComponent migration inventory complete (12 templates, none in Argumentum app). Execution order pragmatic (security-first → eshop → platform → i18n). Stripe Native decision properly referenced. One note: web.config merge in Phase 1 Step 2 could benefit from a diff tool recommendation (e.g. WinMerge) to reduce manual error risk.
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.
What
Re-submit the α deliverable from #444 (closed stale): a standalone DNN upgrade assessment doc (
docs/dnn/UPGRADE-ASSESSMENT.md, +273 lines) covering the 3-phase migration path DNN 9.11.1 → 9.13.x → 10.x, 2sxc LTS, RazorBlade/RazorEngine/CVE-2021-46703 risks, Stripe/Imageflow/NBrightBuy e-shop inventory, and the current DB/template state.Why a re-submit
#444 was closed stale — it bundled three independent pieces:
So only α remains useful.
Why a clean branch
The prior split branch (
docs/444-alpha-dnn-upgrade-assessment) was based on pre-OWL-merge commit36c138b7. Diffed against current masterc873bcdc, it would have reverted the entire OWL lane as parasites (OwlAdapter.csfix #481,OwlValidatorLivePathTests.cs#482,UtilityExtensionsLayoutTests.cs#483). This PR was rebuilt fresh onc873bcdcand isolates the single new file — verified: 1 file changed, +273, 0 deletions.Diff check
Status
Related
🤖 Worker po-2023 — dispatch `laj77j` primaire.
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com