Skip to content

docs(file-uploader): correct 2.5.0 changelog inaccuracies#2297

Open
yordan-st wants to merge 1 commit into
mainfrom
fix/file-uploader-changelog-2.5.0
Open

docs(file-uploader): correct 2.5.0 changelog inaccuracies#2297
yordan-st wants to merge 1 commit into
mainfrom
fix/file-uploader-changelog-2.5.0

Conversation

@yordan-st

Copy link
Copy Markdown
Contributor

What

Fixes two factual errors in the File Uploader 2.5.0 changelog (widget + module).

Line Was Now Source
Fixed "A message now appears below the dropzone" "...appears on the dropzone" Message replaces the dropzone's idle text (Dropzone.tsx), not a separate element below
Changed "The default behavior is now unlimited (no cap)" "The default remains 10" FileUploader.xmlmaxFilesPerUpload defaultValue="10"

Note

2.5.0 is already published. GitHub release notes + Marketplace notes are being corrected separately to match.

- Limit message appears on the dropzone, not below it
- Default max files remains 10, not unlimited
@yordan-st yordan-st requested a review from a team as a code owner July 1, 2026 13:59
@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

AI Code Review

✅ Approved — no issues found


What was reviewed

File Change
packages/pluggableWidgets/file-uploader-web/CHANGELOG.md Two factual corrections to the 2.5.0 entries
packages/modules/file-uploader/CHANGELOG.md Same two corrections mirrored

Skipped (out of scope): dist/, pnpm-lock.yaml


Positives

  • Both corrections are verifiably accurate against the source code: Dropzone.tsx confirms the message renders inside the dropzone (replaces the idle text in <p class="upload-text">), not below it; FileUploader.xml line 83 confirms maxFilesPerUpload defaultValue="10" — the default was never unlimited.
  • Both changelogs updated identically and consistently — module and widget stay in sync.
  • Changes are docs-only with no runtime, XML, or test impact; no CHANGELOG version bump needed.

Note: CI check results were unavailable in this environment. As this PR only modifies CHANGELOG.md files (no code, no tests, no XML), CI outcome does not affect correctness.

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.

2 participants