i18n(id): refresh Indonesian admin translations by ahliweb · Pull Request #83 · ahliweb/emdash-awcms

ahliweb · 2026-08-25T22:40:52Z

What does this PR do?

Refreshes the Indonesian admin catalog. The fork main is synchronized with upstream emdash-cms/emdash:main at 450057e46e0f5cb6300e5cad127fb3b2281e1ad1.

Since the last translation-compatible base dd325cb1629f77fdac7f6494be8b752322812024, upstream has added Media Library detail/usage UI changes, delegated release-service and security hardening, revision/concurrency safeguards, UX acceptance infrastructure, sandboxed content:beforeSave rejection support, publish/autosave race hardening, release-service test stabilization, and multiple generated locale-catalog extractions.

Translation scope

The current PR head still preserves the previously reviewed Indonesian translations. Deterministic reconciliation against current main remains required because several upstream extractions happened after this branch was created.

Previously identified strings still requiring reconciliation include Media Library and delegated-release/verification strings such as:

Move the focal point to choose what stays visible in cropped images.
No usage
No usage to show yet
See where this file is used.
This file isn’t used in any content.
Authorized approvers
Failed to verify plugin
Independent verification
Provenance optional
Provenance required
Publisher release policy
Release CID
Review Verified Plugin
Review Verified Update
Select a release before verifying it
We couldn't verify this publisher's identity
Plugin {pluginId} rejected the save: {reason}

Recommended Indonesian rendering for the newest identified message remains: Plugin {pluginId} menolak penyimpanan: {reason}.

Terminology refinements retained from the earlier review:

destructive Discard actions use Buang / Membuang...;
non-destructive Dismiss actions remain distinct;
Heading terminology is normalized to Judul, including Judul 4–6;
the technical UI term byline remains consistent with the existing Indonesian catalog.

Upstream watch notes

fix(admin): save editor state before publishing emdash-cms/emdash#2860 (fix(admin): save editor state before publishing) merged as afa81c5e.... Root cause: Publish could race the autosave debounce/in-flight autosave and promote stale draft state, dropping the editor's latest changes or regressing already-live fields. The fix serializes save/autosave/publish, cancels pending debounce before publish, flushes the exact current payload, propagates revision tokens, and stops publish on validation/save/revision failure. Upstream reports 1,805 admin tests, build, workspace typecheck, lint, formatting, and git diff --check passing.
fix(admin): save editor state before publishing emdash-cms/emdash#2860 explicitly adds no user-visible strings.
5cb3f73b... is the follow-up locale extraction. It changes generated source references across catalogs (79 additions / 79 deletions per catalog in the extraction commit) and does not introduce a new feature-level msgid from fix(admin): save editor state before publishing emdash-cms/emdash#2860. These generated references still need to be incorporated during deterministic PO reconciliation.
test(release-service): isolate encryption verification sweep emdash-cms/emdash#2868 (test(release-service): isolate encryption verification sweep) merged as 450057e.... Root cause: the exhaustive 256-shard encryption verification sweep and time-sensitive publication-coordination expiry test were contending inside the main Workers-pool suite, causing repeated unrelated CI failures on upstream PRs. The fix isolates the exhaustive sweep in its own Vitest invocation and makes lease expiry deterministic without reducing coverage. It changes release-service tests/test configuration only and introduces no locale or admin UI strings. Scoped release-service tests, typecheck, and pnpm lint:quick passed upstream; the PR notes a pre-existing repository-wide type-aware lint baseline of 42 unrelated diagnostics.
fix(admin): keep locale menus consistent with the admin theme emdash-cms/emdash#2870 (fix(admin): keep locale menus consistent with the admin theme) is open and currently mergeable. It replaces the native locale <select> with Kumo Select, preserves existing message IDs, and explicitly includes no messages.po changes. Root cause: the native menu did not inherit dark-mode/theming consistently and could interact poorly with unsaved byline state. If merged, it should not add translation debt beyond generated source-reference movement; upstream reports lint, typecheck, format check, 1,813 admin browser tests, focused locale/byline tests, and LTR/RTL visual checks passing on rerun.
Add media image cropping emdash-cms/emdash#2861 (Add media image cropping) is open and currently mergeable. It adds substantial localized Media Details crop UI (focal/crop modes, aspect-ratio controls, create-copy/replace-original actions and confirmation text). Because user-visible strings are wrapped for translation and catalogs are intentionally extracted after merge, this PR is a likely source of a future Indonesian locale delta if it lands before i18n(id): refresh Indonesian admin translations #83 is reconciled. Upstream reports build, typecheck, lint, 6,262 core tests, 1,841 admin tests, focused Playwright coverage, and docs build passing. Its head advanced to 1a7b9f38... and changeset-bot now reports release changes across 17 packages; it remains open and mergeable.
Issue Admin View published links ignore entry locale emdash-cms/emdash#2874 (Admin View published links ignore entry locale) is a newly reported i18n runtime bug: published-link construction ignores the entry locale while preview paths already support {locale}. It does not currently change the Indonesian catalog or PR i18n(id): refresh Indonesian admin translations #83 scope, but a future admin fix could move locale source references or add UI messaging.
Issue Visual Portable Text publish leaves key-only pending changes emdash-cms/emdash#2877 (Visual Portable Text publish leaves key-only pending changes) is newly opened against 0.36.0/current behavior. Root cause reported by the reproducer: pmToPortableText() regenerates random _key values on repeated getBlocks() calls, while the visual-editor Portable Text save is not part of the toolbar's pendingSavePromise. A pagehide/keepalive flush can therefore persist a semantically identical post-publish draft that differs only by generated keys. This is a runtime autosave/publish consistency bug, not caused by the Indonesian catalog, and currently adds no locale delta.
Issue Repeated (nested repeater sub-field) input reverts to a stale autosave payload if its response arrives after further edits emdash-cms/emdash#2878 (Repeated (nested repeater sub-field) input reverts to a stale autosave payload if its response arrives after further edits) is newly opened against 0.35.0. The reported root cause is a remaining stale-response race in patchAutosaveQueries: an earlier autosave response/request-time payload can patch observed query state after the user has continued editing a nested repeater field, reintroducing a narrower form of the stale autosave overwrite class previously addressed by Fix autosave form reset bug emdash-cms/emdash#302. This is also runtime state-management behavior outside PR i18n(id): refresh Indonesian admin translations #83's translation scope.
Issues Allow trusted content-editor panels to read and patch the live draft emdash-cms/emdash#2866 and Add a Block Kit placement for sandboxed content-editor actions emdash-cms/emdash#2867 remain future extension-surface work for live-draft editor panels and sandboxed Block Kit editor actions; they do not currently modify this PR's branch.
Clarify that Save creates a draft before publishing new content emdash-cms/emdash#2857 still proposes localized first-save guidance (Save draft or equivalent) but has not yet landed on main; it may create a future locale delta if merged.

Validation status

fork main and upstream main are synchronized at 450057e46e0f5cb6300e5cad127fb3b2281e1ad1;
current PR head remains b841cd537aa2f802360b2b63e0a879cab81183cd;
comparison with current main: 1 commit ahead / 31 commits behind, merge base dd325cb1629f77fdac7f6494be8b752322812024;
GitHub reports the PR as not mergeable;
PR scope remains 1 commit / 2 files (.changeset/bright-id-refresh.md and packages/admin/src/locales/id/messages.po);
the last validated head passed CI, Format, Query Counts, CodeQL, zizmor, Auto Format, and Visual Regression;
Preview Releases on that old head remains the only failed workflow; refreshed-head validation is still required after reconciliation;
no maintainer reviews, review requests, or unresolved review threads are present;
Lunaria still warns that localization source changed after PR creation;
contributor CLA remains incomplete and must be handled by the contributor; automation will not sign or accept it;
a refreshed-head zero-gap locale validation and complete CI run are required after deterministic PO reconciliation/rebase.

Type of change

Checklist

I have read CONTRIBUTING.md
latest upstream locale extraction reconciled
zero-untranslated Indonesian catalog guard passes on refreshed head
branch rebuilt atomically on current upstream main
translation-only runtime impact; no application source behavior changed
user-facing changeset added and reviewed
refreshed-head CI, lint, formatting, type-checking, tests, build, and visual regression checks complete successfully
contributor CLA requirement complete

AI-generated code disclosure

This PR includes AI-assisted translation review and catalog maintenance — model/tool: GPT-5.6 Sol; no runtime code changes.

Screenshots / test output

No visual component/source changes are intended. This PR changes translation catalog content only. The branch must be deterministically refreshed against the latest upstream extraction before final merge-readiness validation.

github-actions · 2026-08-25T22:41:01Z

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

_{You can retrigger this bot by commenting recheck in this Pull Request.}_{Posted by the CLA Assistant Lite bot.}

github-actions · 2026-08-25T22:43:15Z

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
packages/admin/src/locales/id/messages.po	Localization changed, will be marked as complete. 🔄️

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

ahliweb · 2026-09-03T15:10:49Z

Upstream watch update (2026-09-03): upstream main advanced to b06fc6361a88378a697f8d93f7b7718739dc0ed5 with emdash-cms#2852 (fix(core): keep the media-usage cleanup scan bounded when the lease is lost). The fork ahliweb/emdash-awcms:main has been fast-forwarded to the same SHA without force.

emdash-cms#2852 is performance/runtime-only and adds no admin UI strings or locale catalog changes. Root cause: the cleanup candidate scan embedded an uncorrelated lease EXISTS predicate inside a LIMITed keyset scan; once the lease was lost, no row could satisfy the predicate, so the limit was never reached and the query scanned the full media-usage range. The merged fix performs bounded admission (budget -> lease -> budget), distinguishes skipped scans (null) from empty scans ([]), retains mutation-time fencing, and aligns PostgreSQL plan tests with the SQL actually emitted. The PR reports 58 focused SQLite/PostgreSQL tests passing; two unrelated parallel-load 5s timeouts pass in isolation.

After synchronization, i18n/id-refresh-2026-08-26 remains 1 commit ahead / 42 behind main, with diff scope still limited to .changeset/bright-id-refresh.md and packages/admin/src/locales/id/messages.po. No new locale extraction landed in these upstream commits, so the translation branch was intentionally not rewritten yet.

Merge-horizon note: upstream emdash-cms#2891 has moved to head b8b34e92f267b52ec40430c477d3937a9d33dc92 and is currently mergeable. Its current Visual Regression run fails only at the final Fail on drift step after build, visual execution, result collection, and artifact upload succeed; CI is still queued, while Format, Query Counts, Auto Format, CodeQL, zizmor, and Preview Releases are green. Because emdash-cms#2891 contains substantial new Lingui publishing/scheduling strings, reconciliation should still target the actual extraction produced if/when it merges.

PR #83 itself still has no submitted maintainer reviews, requested reviewers, or unresolved review threads. Existing CLA/Lunaria requirements remain unchanged; no CLA or legal agreement was signed or accepted by automation.

ahliweb · 2026-09-03T16:12:12Z

Upstream watch update (2026-09-03): meaningful merge-readiness change.

emdash-cms/emdash:main advanced from b06fc6361a88378a697f8d93f7b7718739dc0ed5 to 264940dc522fd9938d86c67cbbd3fc9e786b0da8.
Add media image cropping emdash-cms/emdash#2861 (Add media image cropping) merged as 05d559625224fbfd23fc08608c44a46ef3735c3e at 15:41 UTC, followed immediately by locale extraction 264940dc... at 15:46 UTC.
The extraction modifies packages/admin/src/locales/id/messages.po by 451 additions / 272 deletions and introduces real new untranslated Indonesian entries from the cropping UI (not only source-reference churn), including crop/aspect-ratio/focal-point/destructive-confirmation strings. Deterministic Indonesian reconciliation is now required against this exact extraction.
Fork ahliweb/emdash-awcms:main has been fast-forwarded non-forced to 264940dc..., so fork main is synchronized with upstream again.
PR i18n(id): refresh Indonesian admin translations #83 remains open/not mergeable, head b841cd537aa2f802360b2b63e0a879cab81183cd, now 1 commit ahead / 44 commits behind main; scope remains only .changeset/bright-id-refresh.md and packages/admin/src/locales/id/messages.po.
No maintainer reviews, review requests, or unresolved review threads are present. CLA remains contributor-owned and was not signed or accepted by automation.
fix(admin): refine publishing and scheduling controls emdash-cms/emdash#2891 (refine publishing and scheduling controls) has advanced to b3af580e..., is mergeable, and its latest CI/Format/Query Counts/Visual Regression/CodeQL/zizmor/Preview Releases are green. It still contains additional localized publishing/scheduling strings that may create another locale delta if merged before i18n(id): refresh Indonesian admin translations #83 is refreshed.
New fix: include locale in admin published links emdash-cms/emdash#2895 (fix: include locale in admin published links) addresses Admin View published links ignore entry locale emdash-cms/emdash#2874 without changing visible labels; it does not currently add Indonesian msgids, but may move admin source references if merged.

Safest next technical step: reconcile the Indonesian catalog from the current extracted main catalog, preserve reviewed translations by msgid, translate every newly empty Indonesian msgstr, verify zero untranslated/fuzzy entries and translation-only diff scope, then refresh the PR head and run full CI. No legal/CLA action was taken.

ahliweb · 2026-09-03T17:08:03Z

Upstream watch update (2026-09-04): meaningful merge-horizon change; no new main commit or locale extraction since 264940dc522fd9938d86c67cbbd3fc9e786b0da8, and fork main remains synchronized.

New upstream PR Fix audit-log hooks skipped for missing capabilities and pass item id to content:beforeSave emdash-cms/emdash#2897 (Fix audit-log hooks skipped for missing capabilities and pass item id to content:beforeSave) opened at 16:30 UTC and is currently mergeable. Root cause: the audit-log plugin registered content:beforeSave and media:afterUpload without declaring the capabilities that gate those hooks, so runtime skipped them; additionally update hook events lacked the item id, preventing before-state lookup and producing incomplete update diffs. The fix declares the required content:write / media:read capabilities and adds an optional update id to ContentHookEvent. It explicitly changes no admin UI strings, so it creates no Indonesian locale debt. Its current head ee5a304c... has CI, Format, Query Counts, Visual Regression, CodeQL, zizmor, Auto Format, and Preview Releases all green.
fix(admin): refine publishing and scheduling controls emdash-cms/emdash#2891 (refine publishing and scheduling controls) remains open/mergeable on b3af580e...; maintainer ascorbic is now requested for review. An automated review already approved the current head with no blocking findings. Because fix(admin): refine publishing and scheduling controls emdash-cms/emdash#2891 contains substantial new Lingui-wrapped scheduling/publishing strings, maintainer review increases its probability of landing soon and triggering another locale extraction.
PR i18n(id): refresh Indonesian admin translations #83 remains open/not mergeable on b841cd537aa2f802360b2b63e0a879cab81183cd, 1 ahead / 44 behind current main, with only the changeset and Indonesian PO file in scope. No maintainer review, requested reviewer, or unresolved review thread exists on i18n(id): refresh Indonesian admin translations #83 itself; old-head CI is unchanged (all previously green checks remain green, Preview Releases remains the old failure).

No branch mutation is applied in this check: the deterministic PO reconciliation against 264940dc... is still required, and emdash-cms#2891 is now close enough to maintainer review that a second extraction may immediately supersede a refresh. CLA remains contributor-owned and was not signed or accepted.

ahliweb · 2026-09-03T17:53:26Z

Upstream watch update (2026-09-04): upstream and fork main remain synchronized at 264940dc522fd9938d86c67cbbd3fc9e786b0da8; no newer locale extraction has landed since the cropping extraction.

Meaningful upstream developments since the previous check:

Issue Returning visitors get stale pages forever after content-only publishes: build-time Last-Modified validator never advances and no ETag is emitted, so conditional revalidation always returns 304 emdash-cms/emdash#2883 received a detailed follow-up from contributor danielmlr that materially sharpens the cache diagnosis. The content dimension already exists through cacheHint.lastModified sourced from updated_at, but it is opt-in per page; templates that pass the hint advance the validator on publish, while pages that omit it are left with the build-time validator floor introduced by fix(core): fold the build into the route cache validator emdash-cms/emdash#2374. The contributor therefore agrees the diagnosis is valid for affected pages and does not expect Astro 7.2.10–7.3.1 or @astrojs/cloudflare 14.2.5 alone to fix this particular 304 loop. They also caution that a body-hash ETag should first be validated end-to-end for text/html, because downstream behavior may strip ETags set through Astro cache options. This is runtime cache correctness only and does not create Indonesian locale debt.
New upstream PR Persist rich text image settings as authors edit emdash-cms/emdash#2898 (Persist rich text image settings as authors edit) is open and currently mergeable at fe518727d252da44675ea9fb30001615c322a521. Root cause: image metadata edits were held in local panel state until an explicit Save action; leaving/re-entering the image could therefore discard caption/alt/title/size/alignment edits, and caption/title fallback logic conflated visible caption with tooltip title. The fix applies edits through onUpdate as they occur, persists caption and title independently through Portable Text/ProseMirror conversions, and removes the obsolete Save action. Its existing localized labels remain wrapped; the visible button change uses existing Close rather than introducing a new message ID in the inspected patch, so current translation impact is source-reference movement rather than a confirmed new Indonesian msgid. Changeset bot reports patch releases across 17 packages. Local verification reported typecheck/lint plus 6 admin, 9 converter/inline-editor, and 16 render tests; however the author's local Astro demo did not become ready, so no screenshot was produced. GitHub CI is still settling: Format, Auto Format, CodeQL, and zizmor are green; CI is queued and Visual Regression, Query Counts, and Preview Releases are still running. Do not treat Persist rich text image settings as authors edit emdash-cms/emdash#2898 as merge-ready until those complete.

PR #83 itself remains open/not mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewer, submitted review, or unresolved review thread. Its old-head CI state is unchanged: CI/Format/Query Counts/Visual Regression/CodeQL/zizmor/Auto Format passed, Preview Releases failed, and refreshed-head validation remains required after deterministic PO reconciliation. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-03T18:51:06Z

Upstream watch update (2026-09-04): upstream emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at 264940dc522fd9938d86c67cbbd3fc9e786b0da8; no new commit or locale extraction has landed since the media-cropping extraction. PR #83 remains open/not mergeable on b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewer, submitted review, or inline review thread. Its old-head workflow state is unchanged: CI, Format, Query Counts, Visual Regression, CodeQL, zizmor, and Auto Format pass; Preview Releases remains the existing failure.

New merge-horizon item: upstream emdash-cms#2899 (Add in-place media image replacement) opened after the previous watch and is currently open/mergeable at e81873b26b24fc5f665e105e0f2ce11a37ae71ec. Root cause/product need: replacing an image currently requires creating a new media object, which breaks the stable media identity/usage workflow. The PR adds same-format in-place JPEG/PNG/WebP replacement while preserving media ID, filename/storage key/URL, metadata, folder, and usage relationships; it clears the old focal point because the replacement dimensions/content can differ. It uses the existing storage abstraction for local/R2/S3-compatible providers.

This PR is directly relevant to the Indonesian catalog because it adds wrapped admin strings including Replace image, Choose replacement image, Replace original image?, Every place using this image will update to the selected version., and Replacing image.... If emdash-cms#2899 merges, the next extraction will therefore add real Indonesian msgids, not only source-reference churn. Changeset-bot currently reports release impact across 17 packages, including minor bumps for emdash and @emdash-cms/admin.

emdash-cms#2899 validation is not fully green despite its local verification report (typecheck, lint, format check, admin build, 1,871 admin tests, 6,304 core tests, and 88 focused media tests). GitHub Actions currently shows CI failed: both Tests and E2E Tests checks are failed, while Format, Query Counts, Visual Regression, CodeQL, zizmor, Auto Format, and Preview Releases are green. Connector metadata exposes the failed checks but not their log annotations, so the precise CI failure cause cannot be established safely from available evidence and is not being guessed.

No upstream issue was newly opened or updated in this interval, and no new Dependabot PR was detected. emdash-cms#2891 remains open/mergeable with maintainer ascorbic requested for review; it is still another likely source of substantial localized publishing/scheduling msgids if merged.

No translation-branch mutation was made in this check. A safe deterministic refresh still requires rebuilding/reconciling the branch against the extracted catalog on current main; the connected GitHub write primitives available in this run do not provide a safe rebase/merge-tree operation for the existing PR head, so forcing the ref or partially editing the PO file would risk an invalid catalog/history. CLA/legal acceptance remains contributor-owned and was not signed or accepted.

ahliweb · 2026-09-03T19:52:33Z

Upstream watch update (2026-09-04): upstream and fork main remain synchronized at 264940dc522fd9938d86c67cbbd3fc9e786b0da8; no new locale extraction has landed since the media-cropping extraction.

Meaningful merge-horizon change: upstream emdash-cms#2899 (Add in-place media image replacement) advanced from e81873b... to 6b3a768... after review feedback. The review identified two concrete issues: missing canonical Media Library documentation for the new Replace image action, and a stale thumbnail-fallback marker in FocalPointPreviews when src changes. Commit 6b3a768... addresses both atomically by adding the Media Library replacement guide, keying preview images by src, and adding a regression test for fallback after source changes. emdash-cms#2899 remains open/mergeable; the refreshed head has Format/Auto Format/zizmor green while CI is queued and Visual Regression/Preview Releases/Query Counts/CodeQL are still running.

This does not change PR #83's current catalog yet because emdash-cms#2899 has not merged, but its already-identified localized Replace image strings remain expected translation debt for the next extraction if it lands first. PR #83 itself remains open/not mergeable, 1 commit ahead / 44 behind current main, with no submitted reviews or requested reviewers. No CLA/legal action was taken.

ahliweb · 2026-09-03T20:50:44Z

Watch update (2026-09-04): upstream main and fork main remain synchronized at 264940dc522fd9938d86c67cbbd3fc9e786b0da8; no new locale extraction has landed since the media-cropping extraction. Upstream PR emdash-cms#2899 advanced to 55b30f9c6668ebc95043b8c8038eb9bfba4c2d71 and remains open/mergeable. All non-CI workflows on that head are green (Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, Auto Format); the CI workflow still fails, now specifically in the Smoke Tests job at pnpm --filter emdash exec vitest run --config vitest.smoke.config.ts, while sampled E2E shards pass. This narrows the current blocker from the prior broader Tests/E2E failures to the smoke suite, but the available Actions metadata does not expose the failing test assertion/log, so no root-cause claim or source mutation is safe yet. emdash-cms#2899 still introduces new translatable Media Details replacement strings, so if merged it will create another Indonesian catalog delta. PR #83 itself still has no maintainer reviews, requested reviewers, or unresolved review threads. No CLA/legal agreement was accepted or signed.

ahliweb · 2026-09-03T21:56:11Z

Upstream watch update (2026-09-04): upstream emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at 264940dc522fd9938d86c67cbbd3fc9e786b0da8; no new locale extraction has landed since the media-cropping extraction.

New merge-horizon item: upstream PR emdash-cms#2900 (editor media/picker foundation) is open and GitHub currently reports it mergeable at be8b096bb592625038eebce74f69a2656c23160a. It is a substantial Media Picker/Media Library refactor (21 files; 4,008 changed lines by the scope bot) that adds/changes wrapped admin strings, including Choose a file from the library or upload a new one., Choose an image from the library or upload a new one., Folder no longer exists. Returned to the main library., Use a URL ending in a recognized image extension, such as .jpg or .png., and picker/source/filter labels. If merged, the next extraction is expected to add Indonesian translation debt and source-reference churn.

emdash-cms#2900 is not merge-ready despite mergeable=true: the PR compliance bot failed because its description leaves the change summary empty, has no Type-of-change checkbox selected, and does not check the CONTRIBUTING acknowledgement. The scope bot also warns that the PR is large and may need splitting. Changeset-bot detects releases across 17 packages, including minor bumps for @emdash-cms/admin and emdash. Current Actions are still in progress/queued; Auto Format and zizmor are green, while CI/CodeQL and several other workflows have not completed.

PR #83 itself remains open/not mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, with no submitted maintainer review, requested reviewer, or unresolved review thread. Old-head CI remains unchanged; deterministic reconciliation against the current extracted catalog plus refreshed-head validation is still required. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-03T22:53:03Z

Upstream watch update (2026-09-04): upstream and fork main remain synchronized at 264940dc522fd9938d86c67cbbd3fc9e786b0da8; no newer locale extraction has landed.

Meaningful merge-horizon change: upstream emdash-cms#2900 (Improve admin media picker workflows) advanced from its initial head to 28657fdf70da5025ba36896a1ea61d2122457264 and fixed the PR-level compliance gaps noted in the previous watch. The description now explains the feature, selects the Feature type, links the maintainer-approved Discussion emdash-cms#990, checks the CONTRIBUTING/i18n/test/format/changeset requirements, and includes UI screenshots. The automated review is APPROVED and there are no inline review threads. Its remaining bot scope warning is advisory: 4,008 changed lines across 21 files.

emdash-cms#2900 remains directly relevant to this Indonesian PR because it introduces/changes localized media-picker UI strings; if merged, the post-merge extraction should be included in the deterministic Indonesian reconciliation rather than refreshing against 264940dc... alone.

Current emdash-cms#2900 head validation is still in progress: CodeQL, Query Counts, Preview Releases, and zizmor are green; CI is queued, Visual Regression and Format are still running, and Auto Format is still running. No current failed check is exposed on this head, so there is no safe source-level fix to apply yet.

PR #83 itself remains open/not mergeable on b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewers. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-03T23:55:31Z

Upstream watch update (2026-09-04): upstream emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at 264940dc522fd9938d86c67cbbd3fc9e786b0da8; no newer locale extraction has landed, so no fork sync or Indonesian catalog rewrite was appropriate in this run.

Meaningful merge-horizon change: upstream emdash-cms#2900 (Improve admin media picker workflows) advanced again to a68e741b887cc1885cba4d653dff2c88ba958ac5 (8 commits, 22 files) and remains GitHub-mergeable. The two commits since the prior watch further polish source controls and add E2E/admin-test coverage; the latest commit specifically normalizes segmented source-tab sizing/icons and URL-source layout.

Fresh validation is no longer all-green: Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, and Auto Format pass, but the main CI workflow fails. The failure is isolated to Playwright shard 4/8 in both E2E tests (4/8) and E2E Cloudflare (4/8); build/install steps and the full admin browser-test job pass. Because the same shard fails in both standard and Cloudflare fixtures, the current evidence points to a shard-specific E2E regression or flake rather than a platform-only Cloudflare failure. GitHub metadata available through the connector does not expose the failing assertion/log text, so no speculative source fix was applied.

emdash-cms#2900 remains directly relevant to PR #83 because it introduces/changes localized Media Picker strings. If it merges, deterministic Indonesian reconciliation should use the post-merge extraction rather than 264940dc... alone.

PR #83 itself remains open/not mergeable on b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewers, no submitted maintainer reviews, and no unresolved review threads. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-04T00:58:01Z

Upstream watch update (2026-09-04): upstream and fork main remain synchronized at 264940dc522fd9938d86c67cbbd3fc9e786b0da8; no newer locale extraction has landed, so no fork fast-forward is needed.

Two merge-readiness developments are material:

Upstream Improve admin media picker workflows emdash-cms/emdash#2900 (Improve admin media picker workflows) advanced from a68e741b... to 2c83bb69... with Fix media picker control clipping. The new commit only changes the media-picker UI/E2E coverage around responsive/control geometry, but the refreshed CI remains red: all non-CI workflows (Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, Auto Format) are green; the aggregate CI failure is now represented by the E2E Tests check while the main Tests check is green. The latest commit therefore did not clear the browser-test blocker. Because the available Actions metadata exposes only the failed E2E aggregate annotation and not the failing assertion/log body, no speculative source fix is safe. Improve admin media picker workflows emdash-cms/emdash#2900 still carries new localized media-picker strings, so if it merges it will add another Indonesian locale delta.
New high-priority upstream issue Media-usage cleanup scan reads the whole table to return a 250-row page emdash-cms/emdash#2901 reports a separate performance defect in MediaUsageRepository.findMediaUsageCleanupCandidates. Root cause: the production prepared-statement form of the keyset predicate (created_at > ? OR (created_at = ? AND id > ?)) makes SQLite/D1 choose MULTI-INDEX OR plus a blocking temp B-tree sort when cutoff and cursor are bound parameters. That defeats early termination by LIMIT: the report measures ~427,020 rows read to return 250 rows versus ~502 with literal values. A row-value predicate (created_at, id) > (?, ?) restores the composite-index range walk (~501 rows read). This is not a regression of Media-usage cleanup lease guard inside WHERE EXISTS turns a LIMITed scan into a full-table scan emdash-cms/emdash#2844 and does not affect locale scope directly, but it is a meaningful upstream performance/security-of-resources concern and may produce another core fix before the translation branch is rebuilt.

PR #83 itself remains open/not-mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, with no maintainer reviews, requested reviewers, or unresolved review threads. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-04T01:51:47Z

Upstream watch update (2026-09-04): upstream emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at 264940dc522fd9938d86c67cbbd3fc9e786b0da8; no newer locale extraction has landed, so no fork fast-forward or Indonesian catalog rewrite is appropriate in this run.

Three new upstream PRs are material to merge readiness:

fix(admin): let the editor recover from a save conflict instead of resending a refused token emdash-cms/emdash#2902 (fix(admin): let the editor recover from a save conflict instead of resending a refused token) is open/mergeable at b1fd2945c94455bffe18c0452f63c74fa9535124. Root cause: after a concurrency conflict, the editor retained the rejected revision token introduced by fix(admin): save editor state before publishing emdash-cms/emdash#2860, so every later save/autosave resent a token the server would continue rejecting. The fix refetches the current revision token, preserves the user's form state, pauses autosave while conflicted, and exposes an explicit overwrite path. It adds three new Lingui-wrapped UI strings — This entry changed somewhere else after you opened it., What you typed is still here. Saving replaces the newer version., and Save anyway — so if merged it will create real Indonesian translation debt in the next extraction. Its current CI, Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, and Auto Format workflows are all green.
fix(admin): keep locale menus consistent with the admin theme emdash-cms/emdash#2903 restores/supersedes accidentally closed fix(admin): keep locale menus consistent with the admin theme emdash-cms/emdash#2870 (fix(admin): keep locale menus consistent with the admin theme). It is currently a draft but GitHub reports the head mergeable. It retains existing message IDs and explicitly includes no messages.po changes, so expected locale impact is source-reference movement rather than new Indonesian msgids. The implementation replaces the native locale select with the themed Kumo Select and includes LTR/RTL/browser coverage.
fix(ci): skip CLA checks in forks emdash-cms/emdash#2904 (fix(ci): skip CLA checks in forks) is a new draft, currently GitHub-mergeable, and directly explains the CLA noise on this fork-local PR. Root cause: forks inherit the upstream CLA workflow, so a fork-local PR can run CLA Assistant and treat authors imported from upstream history as contributors to the fork PR. The proposed one-file fix guards both the CLA job and follow-up labeling job by the canonical upstream repository ID, while preserving CLA enforcement for PRs targeting emdash-cms/emdash. If merged upstream and then synchronized into this fork, future fork-local PR events should skip that CLA workflow. fix(ci): skip CLA checks in forks emdash-cms/emdash#2904 changes no published package or UI strings. Its CodeQL and zizmor checks are green; CI and several other workflows are still queued/in progress at this check. No CLA or other legal agreement was signed or accepted.

PR #83 itself remains open/not mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewers, submitted reviews, or unresolved review threads. The current technical refresh requirement remains deterministic reconciliation against the latest actual extracted catalog, zero-untranslated/fuzzy validation, translation-only diff verification, and full refreshed-head CI. Because emdash-cms#2902 would add new locale strings if it lands and emdash-cms#2903/emdash-cms#2904 are still draft/unmerged, no speculative branch mutation was made.

ahliweb · 2026-09-04T03:09:18Z

Upstream watch update (2026-09-04): upstream emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at 264940dc522fd9938d86c67cbbd3fc9e786b0da8; no newer locale extraction has landed, so no fork fast-forward or Indonesian catalog rewrite is appropriate yet.

Two meaningful merge-horizon developments:

Upstream fix(admin): let the editor recover from a save conflict instead of resending a refused token emdash-cms/emdash#2902 (fix(admin): let the editor recover from a save conflict instead of resending a refused token) advanced to de610f7f77f7cb8882a56278ddc803ddba6436dd after automated review found a real recovery bug. The initial Save anyway handler dismissed the conflict notice unconditionally even when submitSave() returned early (for example because another save was in flight or validation blocked the save). Because conflict recovery had already replaced the rejected revision token with the server's current token, dismissing the banner also lifted the autosave guard; once the blocking condition cleared, autosave could overwrite the newer server version without the writer explicitly choosing to do so. The follow-up commit fixes this by no longer dismissing the conflict state from the button handler at all: the existing mutation onSuccess path clears it only after a confirmed save. A regression test covers the early-return/invalid-URL case. The review thread is still technically unresolved but outdated because the addressed line moved. Current head CI, Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, and Auto Format are all green. fix(admin): let the editor recover from a save conflict instead of resending a refused token emdash-cms/emdash#2902 still carries the three previously identified new localized conflict-recovery msgids, so if merged it will create Indonesian translation debt in the next extraction.
New upstream stacked PR Add in-context media asset editing emdash-cms/emdash#2905 (editor media/asset editing) is open/mergeable at 141a872ef1b6fa9aa3091030251212a86884edfe, but it targets Improve admin media picker workflows emdash-cms/emdash#2900's feature branch (editor-media/picker-foundation) rather than main. It adds in-context Media Library asset editing from image fields, rich-text images, and galleries, including actions such as Edit asset, Choose another, and Remove, plus crop/replace flows. Edit asset does not exist on current main, so this is a real future msgid if the stack lands. Changeset-bot reports a minor @emdash-cms/admin release (and propagated release impact across 17 packages). The PR is not merge-ready despite GitHub mergeable=true: its template is still essentially blank/unacknowledged, the scope bot warns about 2,184 changed lines across 18 files, and CI currently fails at the aggregate E2E Tests check. Importantly, its base SHA 2c83bb69... (Improve admin media picker workflows emdash-cms/emdash#2900) already has the same aggregate E2E failure, so the current evidence cannot attribute the red check uniquely to Add in-context media asset editing emdash-cms/emdash#2905; it may be inherited from the stacked base. Typecheck, browser tests, integration tests, docs/preview deployment and other observed jobs are passing.

PR #83 itself remains open/not mergeable on b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewer. No safe branch mutation is available through the connected GitHub write primitives in this run: deterministic PO reconciliation still requires rebuilding against the extracted catalog and then validating zero untranslated/fuzzy entries plus full refreshed-head CI. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-04T05:06:07Z

Upstream watch update (2026-09-04): meaningful merge-horizon change; upstream and fork main remain synchronized at 264940dc522fd9938d86c67cbbd3fc9e786b0da8, with no newer locale extraction.

Upstream emdash-cms#2903 (fix(admin): keep locale menus consistent with the admin theme) advanced to d157250dd0a7ac40c2d0abf35e88300cd4499d27 and is now non-draft, open, and GitHub-mergeable. The previous automated review concern about brittle visual selectors using Kumo internal data-kumo-* attributes was fixed by adding the stable production class .emdash-locale-switcher-trigger; both associated review threads are resolved, and the latest automated re-review is APPROVED and explicitly calls the PR ready to merge.

Validation is not fully green yet: CI, Format, Query Counts, CodeQL, zizmor, Auto Format, and Preview Releases pass, but Visual Regression fails only at the final Fail on drift step after build, the visual-regression execution itself, result collection, and artifact upload all succeed. This strongly bounds the cause to detected screenshot drift / missing accepted Linux baseline rather than compile, test, lint, typecheck, or runtime failure. The PR description already notes that Linux visual baselines are intentionally not included and require maintainer approval via /accept-baselines, so no safe source mutation should be made from this fork to bypass that policy. emdash-cms#2903 retains existing Lingui message IDs and includes no messages.po changes, so its expected Indonesian impact remains generated source-reference movement only, not new translation debt.

PR #83 itself remains open/not mergeable on b841cd537aa2f802360b2b63e0a879cab81183cd; no maintainer reviews, requested reviewers, or unresolved review threads are present, and old-head CI remains unchanged (all prior green checks still green; Preview Releases remains the old failure). No upstream issues were newly opened or updated in this interval. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-04T07:02:38Z

Upstream watch update (2026-09-04): meaningful merge-readiness change; upstream emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at 264940dc522fd9938d86c67cbbd3fc9e786b0da8, so there is still no newer locale extraction or fork fast-forward to apply.

The directly relevant upstream emdash-cms#2904 (fix(ci): skip CLA checks in forks) has progressed from draft/in-flight validation to ready-for-review, open/mergeable at c3cd4739870f739415103490ea79ef2d5f970220. Its automated review is APPROVED, and all exposed validation on the current head is green: CI, Format, Query Counts, Preview Releases, CodeQL, zizmor, and Auto Format. Changeset-bot reports no changeset, which is consistent with this being workflow-only and not changing a published package.

Root cause remains the inherited CLA workflow: fork-local PRs execute the copied workflow and can make CLA Assistant treat authors of upstream-imported commits as contributors to the fork PR. emdash-cms#2904 guards both the CLA Assistant and follow-up labeling jobs with the canonical upstream repository ID. Fork-to-upstream PRs remain covered because pull_request_target runs in the base repository context. If emdash-cms#2904 merges, the CLA noise currently visible on fork-local PR #83 should stop on future workflow executions without weakening upstream CLA enforcement.

This does not authorize or complete the contributor CLA for any actual upstream contribution; no CLA or legal agreement was signed or accepted by automation.

emdash-cms#2903 remains open/mergeable and review-approved on d157250d...; its CI/Format/Query Counts/Preview Releases/CodeQL/zizmor/Auto Format checks are green, but Visual Regression remains failed on baseline drift requiring maintainer baseline acceptance. It still preserves existing message IDs and includes no messages.po, so its expected Indonesian impact remains source-reference movement rather than new msgids.

PR #83 itself remains open/not mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewer, submitted maintainer review, or unresolved review thread. Its old-head workflow state is unchanged: CI/Format/Query Counts/Visual Regression/CodeQL/zizmor/Auto Format pass and Preview Releases is the existing failure. No branch mutation is appropriate until deterministic Indonesian PO reconciliation is performed against the current extracted catalog (or a newer post-merge extraction if one lands first).

ahliweb · 2026-09-04T08:23:19Z

Upstream watch update (2026-09-04): upstream emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at 264940dc522fd9938d86c67cbbd3fc9e786b0da8; no newer locale extraction has landed, so no fork sync or Indonesian PO rewrite is appropriate in this check. PR #83 itself remains open/not mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewer, submitted review, or unresolved review thread. Its old-head Actions state is unchanged: CI, Format, Query Counts, Visual Regression, CodeQL, zizmor, and Auto Format pass; Preview Releases remains the existing failure.

Two new upstream runtime/accessibility issues were opened since the previous watch:

plugin-forms: the form has no novalidate, so the plugin's own validation never runs and its error spans stay empty emdash-cms/emdash#2908 (plugin-forms: the form has no novalidate, so the plugin's own validation never runs and its error spans stay empty). Root cause reported by the reproducer: browser constraint validation blocks the invalid form before the delegated submit handler executes, so the plugin's showErrors path never runs and rendered [data-error-for] elements remain empty. The issue also identifies missing aria-invalid/aria-describedby association and no focus transfer to the first invalid field. A likely implementation direction is to let the JS-enhanced plugin own validation after hydration while retaining native validation as a no-JS fallback, then wire field/message ARIA state explicitly.
plugin-forms: element ids collide when the same form is embedded more than once on a page emdash-cms/emdash#2909 (plugin-forms: element ids collide when the same form is embedded more than once on a page). Root cause: fieldId() is deterministic only from ${formId}-${name} and lacks a per-render-instance discriminator. Multiple embeddings of one form therefore generate duplicate DOM IDs, causing labels, ARIA references, test selectors, and password managers to resolve the wrong instance. The minimal fix class is an instance-scoped suffix/counter generated once per rendered form and reused consistently by both id and for attributes.

Neither issue currently changes packages/admin locale sources or introduces Indonesian msgids, and there is no corresponding upstream PR yet, so no translation-branch mutation is justified. No new/updated upstream PR was detected in this interval, and no new Dependabot PR was detected. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-04T08:55:16Z

Upstream watch update (2026-09-04): emdash-cms/emdash#2864 (chore(deps): update zod, remove use of deprecated APIs) advanced to head be1bfe8e1be82ceefb85eac0b30212830e105ea5 and remains open/mergeable. The latest commit, fix(ci): stabilize selector-based tests, pins nwsapi to 2.2.25 because 2.2.27 causes pathological selector performance in jsdom UI tests, and replaces several userEvent.click(...all()[0]) calls with direct selector clicks. This is dependency/test-infrastructure work, not a locale extraction or new user-facing admin message change, so no Indonesian catalog refresh is warranted yet. The PR's Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, and Auto Format workflows are green; CI is still in progress. Changeset bot reports patch releases across 24 packages, including @emdash-cms/admin, but there is no current evidence of translation delta. An older Copilot review thread about preserving stable error.details.issues remains unresolved but is outdated after subsequent changes. Fork main and upstream main remain synchronized at 264940dc522fd9938d86c67cbbd3fc9e786b0da8; PR #83 remains open/not mergeable on b841cd537aa2f802360b2b63e0a879cab81183cd. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-04T09:45:06Z

Upstream watch update (2026-09-04): upstream emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at 264940dc522fd9938d86c67cbbd3fc9e786b0da8; no new locale extraction has landed. PR #83 remains open/not mergeable on b841cd537aa2f802360b2b63e0a879cab81183cd, and the branch is still 1 commit ahead / 44 behind current main with the same 2-file translation-only scope.

Meaningful merge-horizon change: upstream emdash-cms#2899 (Add in-place media image replacement) is now maintainer-approved by ascorbic at head 55b30f9c6668ebc95043b8c8038eb9bfba4c2d71. Its previously identified RTL review thread is resolved, GitHub still reports the PR mergeable, and all current workflows are green: CI, Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, and Auto Format. This clears the earlier Smoke Tests/CI blocker rather than exposing a remaining code failure.

emdash-cms#2899 therefore moved materially closer to merge. It still introduces real wrapped admin msgids such as Replace image, Choose replacement image, Replace original image?, Every place using this image will update to the selected version., and Replacing image...; if it lands before #83 is rebuilt, the following locale extraction will create additional Indonesian translation debt and should be included in the deterministic reconciliation.

No branch mutation is appropriate yet because emdash-cms#2899 has not merged and main has not changed. CLA/legal acceptance remains contributor-owned; no agreement was signed or accepted.

ahliweb · 2026-09-04T11:23:34Z

Upstream watch update (2026-09-04): material change and one safe repository action applied.

Upstream emdash-cms/emdash:main advanced by 2 commits from 264940dc522fd9938d86c67cbbd3fc9e786b0da8 to a213afabf5d38652cd609f0888964f53fd41ee10.
595a6b12a11e67b89684bc5f5c14fbb6f0fc5e7f merged Add in-place media image replacement emdash-cms/emdash#2899 (Add in-place media image replacement). The merge adds in-place JPEG/PNG/WebP replacement while preserving media identity and introduces new Lingui-wrapped admin strings such as Replace image, Choose replacement image, Replace original image?, Every place using this image will update to the selected version., Replacing image..., Image replaced., Choose a non-empty {0} image., The selected image could not be read., and EmDash does not keep the previous image..
a213afabf5d38652cd609f0888964f53fd41ee10 is the bot-generated chore: extract locale catalogs [skip ci] follow-up. The Indonesian messages.po is modified in that extraction (143 additions / 109 deletions), so this is now a real locale delta, not only a future merge-horizon risk.
Root cause/product need of Add in-place media image replacement emdash-cms/emdash#2899: replacing an image previously required creating a new media object, which broke stable identity/usage relationships. The merged implementation replaces stored bytes in place, preserves ID/filename/storage key/URL/metadata/folder/usage, and clears the focal point because replacement dimensions/content can differ.
Safe action applied: fork ahliweb/emdash-awcms:main was fast-forwarded atomically to upstream a213afabf5d38652cd609f0888964f53fd41ee10; revalidation confirms fork and upstream main now match exactly.
PR i18n(id): refresh Indonesian admin translations #83 itself remains on b841cd537aa2f802360b2b63e0a879cab81183cd, open/not mergeable, with no requested reviewer, submitted review, or unresolved review thread. The branch now definitively needs deterministic reconciliation against the a213afab... extracted Indonesian catalog.
I did not force-update/rebase the PR branch or partially overwrite messages.po: doing so without a complete deterministic merge of the reviewed translations by msgid plus zero-untranslated/fuzzy validation would risk corrupting catalog history or silently losing translations. The next safe branch mutation is to rebuild/reconcile the PR head from a213afab..., preserve reviewed Indonesian msgstr values by msgid, translate every newly empty entry, then run translation completeness, diff-scope, format/typecheck/build/tests and full CI on the refreshed head.
No new upstream issue was opened or updated in the interval checked. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-04T12:01:39Z

Upstream watch update (2026-09-04): upstream emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at a213afabf5d38652cd609f0888964f53fd41ee10; no newer locale extraction has landed since the post-emdash-cms#2899 extraction.

Meaningful merge-horizon developments since the last check:

Upstream Improve admin media picker workflows emdash-cms/emdash#2900 (Improve admin media picker workflows) advanced to 0d09146230394779de9ce58e55dcf6610cf84cf5. The new commit, Stabilize Astro consumer smoke installs, addresses a separate but real smoke-install failure class: Astro 7.3.1 can discover astro/logger/console during Cloudflare dev cold start, invalidate prebundled server chunks, and break consumer smoke installs. The fix conditionally adds astro/logger/console to Vite optimization when the consumer project can resolve it, and makes isolated-install fixtures inherit the workspace minimumReleaseAge / exclusion policy so packed first-party packages are not blocked by release-age gating. It adds a patch changeset for emdash and no admin locale strings. On the refreshed head, Format, Query Counts, Preview Releases, CodeQL, zizmor, and Auto Format are green; CI is queued and Visual Regression is still running. Improve admin media picker workflows emdash-cms/emdash#2900 remains mergeable and still carries the previously identified Media Picker translation debt.
Upstream fix(admin): refine publishing and scheduling controls emdash-cms/emdash#2891 (fix(admin): refine publishing and scheduling controls) also advanced materially to c7b60d555422c64dc8b97314bdf41ea50e0037e6 (43 commits, 33 files) and remains mergeable with maintainer ascorbic requested for review. Two fresh source commits refine publishing metadata controls and byline-sidebar controls, followed by an emdashbot commit accepting requested visual baselines. The head therefore still has substantial localized publishing/scheduling UI changes that are likely to create another Indonesian extraction if merged. Its refreshed validation is not complete yet: Format and zizmor are green; Query Counts and Preview Releases are running; CI, CodeQL, and Visual Regression are queued.
Issue plugin-field-kit peer-dependency issue emdash-cms/emdash#2323 (plugin-field-kit peer-dependency issue) was touched again in this interval but has no new comment. Existing diagnosis remains that npm @emdash-cms/plugin-field-kit@0.1.0 publishes a stale @cloudflare/kumo ^1.0.0 peer while current source resolves Kumo 2.6.0; a fresh package release is required to repair registry metadata. This is dependency/release hygiene, not Indonesian locale scope.

PR #83 itself remains open/not mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewer, submitted review, or unresolved review thread. No branch mutation is applied in this check because current main has not moved beyond the extraction already synchronized to the fork, while the Indonesian branch still requires deterministic msgid-based reconciliation against that extracted catalog before a safe refreshed head can be produced. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-04T12:39:23Z

Upstream watch update (2026-09-04): upstream and fork main remain synchronized at a213afabf5d38652cd609f0888964f53fd41ee10; no newer locale extraction has landed since the emdash-cms#2899 extraction.

New merge-horizon item: upstream emdash-cms#2910 (fix(core): bound the media-usage cleanup scan with a row-value cursor) opened from current main and is currently mergeable. It closes emdash-cms#2901 by replacing the SQLite/D1 keyset predicate (created_at > ?) OR (created_at = ? AND id > ?) with the equivalent row-value comparison (created_at, id) > (?, ?). Root cause: with bound parameters SQLite planned the OR as MULTI-INDEX OR plus a temporary B-tree sort, making LIMIT 250 ineffective until the entire eligible backlog was scanned. The new plan can walk the composite index directly and stop at the page limit; the PR adds an EXPLAIN QUERY PLAN regression test using real bound parameters and a PostgreSQL portability guard. This is core/database-only and adds no admin msgids or messages.po changes.

emdash-cms#2910 has an automated APPROVED review with no review threads, and Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, and Auto Format are green. Aggregate CI is currently red because Browser Tests fails in the admin test step and Smoke Tests fails in the core smoke suite; the PR changes only .changeset/lucky-parrots-repeat.md, packages/core/src/database/repositories/media-usage.ts, and its cleanup-plan integration test, so the admin browser failure is outside the patch scope. The smoke failure still needs log-level confirmation before attributing it to the SQL change, so no speculative fix was applied.

PR #83 itself remains open/not mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, with no submitted reviews, requested reviewers, or unresolved review threads. The Indonesian branch still requires deterministic msgid-based reconciliation against a213afab...; no force rewrite or partial PO overwrite was performed. CLA remains contributor-owned and was not signed or accepted by automation.

ahliweb · 2026-09-04T14:25:47Z

Upstream watch update (2026-09-04): meaningful merge-readiness developments; no new main commit or locale extraction has landed since a213afabf5d38652cd609f0888964f53fd41ee10, and fork main remains synchronized at the same SHA.

New upstream issue Non-translatable fields never sync to sibling locales on collections that support revisions emdash-cms/emdash#2911 (Non-translatable fields never sync to sibling locales on collections that support revisions) was opened at 13:04 UTC against current main. Root cause: syncNonTranslatableFields is only reached from handleContentUpdate when the update carries data; revision-enabled collections stage drafts with data: undefined, and publish promotes the revision without passing through that sync path. The existing raw-SQL sibling sync also does not advance version or updated_at, so _rev can remain valid after sibling data has changed, allowing a stale editor to overwrite the synchronized value without a conflict. This is an i18n runtime/concurrency correctness issue, not an Indonesian catalog extraction change, and the reporter correctly notes the fix is architectural rather than a safe one-line patch because syncing on publish would mutate sibling live rows and affects updated_at semantics used by sitemap/dateModified.
Upstream Improve admin media picker workflows emdash-cms/emdash#2900 (Improve admin media picker workflows) is now fully CI-green on head 0d09146230394779de9ce58e55dcf6610cf84cf5: CI, Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, and Auto Format all pass. This removes the previous smoke/install validation uncertainty. Improve admin media picker workflows emdash-cms/emdash#2900 remains open/mergeable and still carries new localized media-picker strings, so a post-merge extraction would create another Indonesian locale delta.
Upstream fix(admin): refine publishing and scheduling controls emdash-cms/emdash#2891 (fix(admin): refine publishing and scheduling controls) advanced to 55e855ec874ecf5e7d37dfa01afa9fc896e4a26b, remains open/mergeable, and still has maintainer ascorbic requested for review. The latest commit (fix(admin): compact collapsed editor actions) is a 5-line layout-only change in ContentSettingsPanel.tsx and adds no new message ID. Bot review remains APPROVED with no review threads. Non-CI workflows are green, but the aggregate CI workflow on the latest head is currently reported as failed even though the published Tests and E2E Tests aggregate checks are green; therefore this looks like a remaining CI-job-level failure rather than a demonstrated source/test regression in the publishing UI, and no speculative fix is being applied from the translation branch.

PR #83 itself remains open/not mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewers, submitted reviews, or unresolved review threads. Its old-head checks remain unchanged: CI, Format, Query Counts, Visual Regression, CodeQL, zizmor, and Auto Format pass; Preview Releases remains the historical failure. No branch mutation is safe in this check: the Indonesian branch still needs deterministic msgid-based reconciliation against the extracted a213afab... catalog, and neither emdash-cms#2900 nor emdash-cms#2891 has merged yet. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-04T15:03:58Z

Upstream watch update (2026-09-04): upstream emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at a213afabf5d38652cd609f0888964f53fd41ee10; no new main commit or locale extraction has landed since the post-emdash-cms#2899 extraction.

New merge-readiness item: upstream emdash-cms#2912 (fix(core): require the revision token on MCP content writes) opened at 14:30 UTC and is currently open/mergeable on f370559ce83707654c6df4e126233fe0ba014e93. It closes a real optimistic-concurrency gap: MCP content_update, content_publish, content_unpublish, and content_discard_draft previously allowed _rev to be omitted, and status-only content_update transitions could bypass the revision check even when a token was supplied. The proposed fix makes _rev mandatory and forwards it through publish/unpublish transitions. It changes core/MCP protocol/docs rather than admin UI, so it does not create Indonesian locale debt by itself.

The current head is not merge-ready despite mergeable=true. Automated review found five needs_fixing items: stale unreleased changeset text still claims omitted _rev preserves old behavior, plus three validation.test.ts content_update calls missing _rev, which causes those tests to pass for the wrong reason because the new _rev is required error matches their loose validation regex. The review also requests the missing revOf import; one authorization-test comment is only a suggestion. GitHub Actions confirms Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, and Auto Format are green, while the aggregate CI workflow is currently failed. Typecheck, integration tests, browser/admin tests, and the final E2E aggregate exposed on the head are green, so the remaining CI failure should not be attributed to typecheck/admin/i18n without further job-level evidence.

PR #83 itself remains open/not mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewer or submitted review. No translation-branch mutation was made: deterministic msgid-based reconciliation against the extracted a213afab... catalog is still required, and the available GitHub primitives do not provide a safe in-place rebase of the existing PR history without reconstructing the branch. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-04T16:03:53Z

Upstream watch update (2026-09-04): upstream emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at a213afabf5d38652cd609f0888964f53fd41ee10; no new main commit or locale extraction has landed since the post-emdash-cms#2899 extraction.

Meaningful upstream changes:

fix(core): require the revision token on MCP content writes emdash-cms/emdash#2912 (fix(core): require the revision token on MCP content writes) advanced to df2fdd26ac6b447ab6cecc1c83a0f36b6bc8f049. The earlier review blockers are now fixed: stale changeset wording was corrected, all missed MCP validation tests now supply _rev, and the misleading authorization-test comment was corrected. Automated re-review is now APPROVED with no remaining blocking review findings. Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, and Auto Format are green. Aggregate CI still fails in the Smoke Tests job at the emdash smoke Vitest invocation, so the PR is not fully CI-green yet. This PR changes MCP/core behavior and docs, not admin locale strings.
New upstream fix(core): normalize scheduledAt to UTC in content.schedule() emdash-cms/emdash#2913 (fix(core): normalize scheduledAt to UTC in content.schedule()) is open and currently mergeable at a812c1981ee134bf4a6f94bfe4a981b08df0b393. Root cause: content.schedule() stored caller-provided offset timestamps verbatim while findReadyToPublish() compares scheduled_at lexicographically against a UTC toISOString() value. Inputs such as +09:00 therefore sort incorrectly and can publish hours late/early despite cron firing normally. The proposed fix stores the already-validated timestamp as UTC. Automated review agrees with the diagnosis but found two remaining needs fixing gaps: sibling write paths update() and replaceDraftRevisionForUpdate() still store raw scheduledAt, so UTC normalization should be centralized across every scheduled_at write. All Actions currently show action_required with no jobs because this external contributor's workflows require approval; the CLA bot also requests contributor signature. No CLA or legal agreement was signed or accepted by automation. fix(core): normalize scheduledAt to UTC in content.schedule() emdash-cms/emdash#2913 does not add admin locale strings.
Issue Visual editor image upload always reports "Upload failed" — response envelope not unwrapped in the site toolbar emdash-cms/emdash#2514 (Visual editor image upload always reports "Upload failed") was touched again by automation and labeled bot:reproduced. Its established root cause remains response-envelope parsing in the visual-editing toolbar ({ success, data } was read as if item/items were top-level). A bot candidate fix already exists on bot/fix-2514; this does not change the Indonesian catalog at present.

PR #83 itself remains open / not mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewers, no submitted reviews, and no review threads. Old-head checks are unchanged: CI, Format, Query Counts, Visual Regression, CodeQL, zizmor, and Auto Format pass; Preview Releases remains the historical failure. The branch still requires deterministic msgid-based reconciliation against the current extracted catalog before a safe refreshed-head validation. No branch mutation was performed in this check because upstream main has not advanced and none of the new developments changes the current Indonesian extraction.

ahliweb · 2026-09-04T18:17:02Z

Upstream watch update (2026-09-05): upstream emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at a213afabf5d38652cd609f0888964f53fd41ee10; no new main commit or locale extraction has landed since the post-emdash-cms#2899 extraction.

Meaningful merge-horizon changes:

fix(core): normalize scheduledAt to UTC in content.schedule() emdash-cms/emdash#2913 (fix(core): normalize scheduledAt to UTC in content.schedule()) advanced from a812c198... to 7f0b438b... and addressed the two correctness gaps raised in review. The fix now centralizes scheduledAt normalization and applies it not only in schedule() but also in update() and replaceDraftRevisionForUpdate(), preserving null for unscheduling and rejecting invalid timestamps. This closes the same string-ordering bug across all known write paths. Its Actions are still action_required because this external-contributor head has not been approved to run workflows; no CLA was signed or accepted by automation. The PR has no admin UI or locale-catalog changes.
fix(admin): scope Trash tab to the active locale emdash-cms/emdash#2807 (fix(admin): scope Trash tab to the active locale) was refreshed onto current upstream main with merge commit 83cf94b74f8c7237672dfba2d2dfc4ce2212fdbe. It remains open/mergeable, has automated approval and no review threads. Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, and Auto Format are green; aggregate CI is still in progress. The patch adds a localized Locale column to Trash, but the Locale msgid is already used elsewhere in the admin, so this should not create a new Indonesian translation string if merged; it may still move generated source references in the next extraction.
feat(core): add Unicode text normalization for search and sorting emdash-cms/emdash#2862 (feat(core): add Unicode text normalization for search and sorting) advanced to a7bb1560.... The latest round fixed Ukrainian й ordering, Turkish marked-i handling, and Greek final-sigma folding, and removed an unbounded locale-keyed collation cache in favor of bounded eager tailorings. The PR explicitly treats Indonesian with the invariant ordering and currently has no call sites, no public export, no admin strings, and no messages.po changes. Both prior review threads are resolved/outdated, so this is not a direct blocker for i18n(id): refresh Indonesian admin translations #83.

No upstream issue was newly opened or updated since the prior checkpoint. PR #83 itself remains open/not mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, with the same old-head validation: CI/Format/Query Counts/Visual Regression/CodeQL/zizmor/Auto Format green and Preview Releases failed historically. No translation-branch mutation was applied in this check because there is no newer extraction to reconcile against; deterministic msgid-based reconciliation against a213afab... is still the required next branch operation.

ahliweb · 2026-09-04T19:10:50Z

Upstream watch update (2026-09-05): upstream emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at a213afabf5d38652cd609f0888964f53fd41ee10; no new main commit or locale extraction has landed.

Meaningful merge-horizon changes since the previous check:

fix(admin): refine publishing and scheduling controls emdash-cms/emdash#2891 (fix(admin): refine publishing and scheduling controls) advanced to 90c03bf4cfcd485d188ac22b0c3eb286d5fbc905. The new commit test(core): retry transient injected route timeouts addresses a CI flake in the isolated-install smoke harness: startup polling previously let a single fetch timeout abort the whole injected-route readiness check. The helper now retries transient TypeError/abort/timeout failures inside a bounded overall deadline, uses a shorter per-request timeout, and adds a regression test that intentionally times out the first request before succeeding. On this refreshed head, CI, Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, and Auto Format are all green. The PR remains open/mergeable and ascorbic is still requested for review; automated review is approved and there are no review threads. This materially increases the probability that fix(admin): refine publishing and scheduling controls emdash-cms/emdash#2891 can merge and trigger a subsequent locale extraction containing its wrapped publishing/scheduling UI strings, but the latest smoke-harness commit itself adds no msgids.
fix(admin): scope Trash tab to the active locale emdash-cms/emdash#2807 (fix(admin): scope Trash tab to the active locale) completed the CI run that was still in progress at the last checkpoint. Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, and Auto Format are green, but aggregate CI concluded failure on head 83cf94b74f8c7237672dfba2d2dfc4ce2212fdbe. The exposed checks show aggregate Tests and E2E Tests succeeding, so there is no evidence that the locale-scoping patch or its existing Locale msgid caused the failure; the remaining failed CI subjob is not safely attributable from the currently exposed check summary, so no speculative source fix was applied.

PR #83 itself remains open / not mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewer. No branch mutation is appropriate in this check because main has not moved and the current Indonesian catalog still needs deterministic msgid-based reconciliation against the a213afab… extraction before a safe refreshed-head CI run. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-04T20:54:04Z

Upstream watch update (2026-09-05): upstream emdash-cms/emdash:main advanced from a213afabf5d38652cd609f0888964f53fd41ee10 to 108c753b9b266c1d050bdb40dba4f7a09517ee3d via merged emdash-cms#2900 (Improve admin media picker workflows) followed by chore: extract locale catalogs [skip ci]. I fast-forwarded fork ahliweb/emdash-awcms:main to the same 108c753b... commit.

This is a real Indonesian locale delta, not only source-reference churn: the generated packages/admin/src/locales/id/messages.po changed by 429 additions / 344 deletions. emdash-cms#2900 adds new wrapped media-picker copy, including upload-queue counts/failures, ordered selection actions, pagination/position copy, and task-specific add/select labels. The upstream extraction leaves new locale entries untranslated for translation PRs by design, so PR #83 now needs another deterministic msgid-based reconciliation against 108c753b... before it can be merge-ready.

Root cause: emdash-cms#2900 replaces the old modal-specific picker behavior with the Media Library-aligned picker (folders/search/type filters/grid-list pagination, inline bounded upload queue, persistent ordered selection, direct-URL source, task-specific confirmation labels). That necessarily changed the set and source locations of translatable messages. It also closes upstream issue emdash-cms#2784, whose core problem was that one shared Insert msgid could not correctly describe both field selection and URL insertion across locales; this could not be solved safely in translation catalogs alone.

Current PR #83 head remains b841cd537aa2f802360b2b63e0a879cab81183cd; comparison to refreshed fork main is now 1 commit ahead / 48 commits behind with merge base dd325cb1629f77fdac7f6494be8b752322812024, and GitHub still reports the PR as not mergeable. There are still no submitted reviews, requested reviewers, or review threads. Old-head CI remains green except historical Preview Releases; refreshed-head CI has not run because the translation branch has not yet been safely rebuilt.

I did not force-rewrite the translation branch or overwrite messages.po: the branch and current extracted catalog both modify the same generated file, and connected GitHub write tools do not provide a conflict-aware PO merge/rebase primitive. A safe refresh still requires preserving reviewed Indonesian msgstr values by msgid, adopting current extraction metadata/source references, translating all newly introduced msgids, then validating zero untranslated/fuzzy entries, translation-only diff scope, formatting/typecheck/tests/build, and full CI.

CLA remains contributor-owned. No legal agreement was signed or accepted by automation.

ahliweb · 2026-09-04T22:14:17Z

Upstream watch update (2026-09-05): upstream emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at 108c753b9b266c1d050bdb40dba4f7a09517ee3d; no newer main commit or locale extraction has landed since the post-emdash-cms#2900 extraction.

Meaningful merge-horizon change: upstream emdash-cms#2905 (Add in-context media asset editing) has been rebased onto current main and is now open/mergeable at f55ad62f7ee545333af462cfe2acf8b01a7be72c with the latest CI, Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, and Auto Format all passing. Its two automated review threads are resolved. The latest corrective commit fixes a real React state-synchronization regression in ImageDetailPanel by keying the sidebar attribute reset to image-node identity, and also applies the requested decorative-icon accessibility cleanup.

emdash-cms#2905 is directly relevant to the Indonesian extraction horizon because it adds/changes wrapped admin strings around in-context asset editing, including Edit asset, Edit dark mode asset, Replace dark mode image, and context-sensitive Replace ${label} / Replace dark mode variant for ${label}. If emdash-cms#2905 merges before #83 is reconciled, the subsequent extraction should be treated as the new reconciliation base rather than translating its candidate diff manually.

New upstream issue emdash-cms#2915 (Regenerate types immediately when the schema changes in dev) was opened by a maintainer. Reported behavior: schema edits during dev (for example through local MCP) leave emdash-env.d.ts stale until reload. The requested bot repro did not reach the product test: workspace preparation failed during dependency installation after a lockfile supply-chain policy check and an npm metadata fetch failure for @oxlint/binding-android-arm-eabi. Therefore bot:failed is an infrastructure/setup outcome, not evidence that the issue is unreproducible. It currently has no locale impact.

PR #83 remains open/not mergeable on b841cd537aa2f802360b2b63e0a879cab81183cd; comparison with current fork main is still 1 commit ahead / 48 behind with merge base dd325cb1629f77fdac7f6494be8b752322812024, and scope remains only .changeset/bright-id-refresh.md plus packages/admin/src/locales/id/messages.po. No maintainer review, review request, or unresolved review thread is present. Deterministic msgid-based PO reconciliation is still required before a refreshed-head CI run. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-04T22:55:46Z

Upstream watch update (2026-09-05): upstream emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at 108c753b9b266c1d050bdb40dba4f7a09517ee3d; no newer locale extraction has landed, so no fork sync or Indonesian branch rewrite is appropriate in this check.

Meaningful upstream development: issue emdash-cms#2916 (Inline Portable Text editor disappears in dev when Highlight.js fails to hydrate) was opened by maintainer ascorbic at 2026-09-04 22:23 UTC. Root cause is a dev-only module interop failure in the visual Portable Text editor: the inline editor statically imports the code-block path through lowlight, which default-imports the CommonJS deep entry highlight.js/lib/core; Vite can serve that deep import directly instead of pre-bundling an ESM interop wrapper, causing hydration to throw does not provide an export named 'default' and leaving the editor island empty even when the content contains no code block.

@emdashbot fix produced candidate branch bot/fix-2916. The candidate adds lowlight, highlight.js, and highlight.js/lib/core to client optimizeDeps.include for source- and dist-mode dev configs, adds a regression test for those entries, and reports focused core typecheck, root JSON lint, formatting, and vite-config.test.ts all passing. A preview package/playground is available, but the bot is explicitly awaiting maintainer/reporter confirmation before opening a draft PR. This change is core/Vite configuration plus tests/changeset only and introduces no admin UI msgids, so it creates no Indonesian locale debt.

PR #83 itself remains open/not mergeable on b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewers, no submitted reviews, and no unresolved review threads. Old-head workflow state is unchanged: CI, Format, Query Counts, Visual Regression, CodeQL, zizmor, and Auto Format pass; Preview Releases remains the historical failure. The Indonesian branch still requires deterministic msgid-based reconciliation against the extracted catalog on 108c753b..., followed by zero-untranslated/fuzzy validation, translation-only diff-scope verification, and refreshed-head CI. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-05T00:27:58Z

Upstream watch update (2026-09-05): upstream emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at 108c753b9b266c1d050bdb40dba4f7a09517ee3d; no newer main commit or locale extraction has landed, so no fork sync or Indonesian branch rewrite is appropriate in this check.

Meaningful developments since the previous watch:

Issue Regenerate types immediately when the schema changes in dev emdash-cms/emdash#2915 (Regenerate types immediately when the schema changes in dev) progressed from an infrastructure-blocked repro to a concrete candidate implementation on bot/fix-2915. The maintainer switched from @emdashbot fix (which was unavailable while the bot run was in failed state) to @emdashbot implement. The candidate adds a dev-only refresh hook, registers a debounced integration-side typegen refresh, and invokes it after successful SchemaRegistry mutations so REST/MCP/import mutation paths all regenerate emdash-env.d.ts without requiring reload. Reported validation is clean: lint/json lint/format/typecheck, 63 focused registry tests, and pnpm --filter emdash build all pass. The bot is now awaiting maintainer/reporter confirmation before opening a draft PR. Root cause is architectural: schema mutations were committed through the registry but development type generation was only driven by startup/reload behavior, leaving generated types stale during a live dev session. This candidate changes core/integration code and tests only; it introduces no admin msgids and therefore no direct Indonesian locale delta.
Upstream Add in-context media asset editing emdash-cms/emdash#2905 (Add in-context media asset editing) remains open/mergeable at f55ad62f7ee545333af462cfe2acf8b01a7be72c, and its latest CI, Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, and Auto Format runs are all successful. A new automated re-review at 2026-09-04 23:24 UTC found no blocking logic/security/convention regression. The previously blocking ImageDetailPanel state-synchronization issue remains resolved. The re-review raises only three accessibility suggestions: hide decorative Moon, ImageSquare, and Trash icons from assistive technologies. Existing review threads are resolved; these new suggestions are review-body findings rather than unresolved inline threads. They do not change the current locale extraction, but Add in-context media asset editing emdash-cms/emdash#2905 still carries wrapped media-editing strings and remains a likely source of the next Indonesian catalog delta if merged.

PR #83 itself remains open/not mergeable on b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewers, submitted reviews, or unresolved review threads. Old-head workflows remain unchanged: CI, Format, Query Counts, Visual Regression, CodeQL, zizmor, and Auto Format pass; Preview Releases is the historical failure. The branch still requires deterministic msgid-based reconciliation against the 108c753b... extracted catalog, then zero-untranslated/fuzzy checks, translation-only diff verification, and refreshed-head CI. No CLA or other legal agreement was signed or accepted.

github-actions Bot added area/admin size/M labels Aug 25, 2026

github-actions Bot added the review/needs-review No maintainer or bot review yet label Aug 25, 2026

ahliweb mentioned this pull request Aug 25, 2026

i18n(id): complete latest Indonesian translations #76

Closed

18 tasks

ahliweb closed this Aug 26, 2026

ahliweb force-pushed the i18n/id-refresh-2026-08-26 branch from 63fc195 to 5c7995f Compare August 26, 2026 12:21

github-actions Bot added size/XS cla: needed and removed size/M labels Aug 26, 2026

ahliweb reopened this Aug 26, 2026

github-actions Bot added size/M and removed size/XS labels Aug 26, 2026

ahliweb force-pushed the i18n/id-refresh-2026-08-26 branch from 74a2073 to c5180ea Compare August 28, 2026 10:47

github-actions Bot added size/L and removed size/M labels Aug 28, 2026

ahliweb force-pushed the i18n/id-refresh-2026-08-26 branch 2 times, most recently from 8573001 to a973c8d Compare September 1, 2026 07:05

github-actions Bot pushed a commit that referenced this pull request Sep 1, 2026

visual diffs for PR #83 @ a973c8d

9b25611

ahliweb force-pushed the i18n/id-refresh-2026-08-26 branch from a973c8d to 495e5be Compare September 1, 2026 07:57

github-actions Bot pushed a commit that referenced this pull request Sep 1, 2026

visual diffs for PR #83 @ 495e5be

9c063c8

ahliweb force-pushed the i18n/id-refresh-2026-08-26 branch from 495e5be to 77c9827 Compare September 1, 2026 10:08

github-actions Bot pushed a commit that referenced this pull request Sep 1, 2026

visual diffs for PR #83 @ 77c9827

420aacc

ahliweb force-pushed the i18n/id-refresh-2026-08-26 branch from 77c9827 to 37b323a Compare September 1, 2026 10:55

github-actions Bot force-pushed the i18n/id-refresh-2026-08-26 branch 2 times, most recently from beb72d1 to fef5ee1 Compare September 1, 2026 11:50

ahliweb force-pushed the i18n/id-refresh-2026-08-26 branch 3 times, most recently from 0a64dda to fd76946 Compare September 1, 2026 14:55

Conversation

ahliweb commented Aug 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What does this PR do?

Translation scope

Upstream watch notes

Validation status

Type of change

Checklist

AI-generated code disclosure

Screenshots / test output

Uh oh!

github-actions Bot commented Aug 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Aug 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Lunaria Status Overview

Tracked Files

Uh oh!

ahliweb commented Sep 3, 2026

Uh oh!

ahliweb commented Sep 3, 2026

Uh oh!

ahliweb commented Sep 3, 2026

Uh oh!

ahliweb commented Sep 3, 2026

Uh oh!

ahliweb commented Sep 3, 2026

Uh oh!

ahliweb commented Sep 3, 2026

Uh oh!

ahliweb commented Sep 3, 2026

Uh oh!

ahliweb commented Sep 3, 2026

Uh oh!

ahliweb commented Sep 3, 2026

Uh oh!

ahliweb commented Sep 3, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 4, 2026

Uh oh!

ahliweb commented Sep 5, 2026

Uh oh!

ahliweb commented Aug 25, 2026 •

edited

Loading

github-actions Bot commented Aug 25, 2026 •

edited

Loading

github-actions Bot commented Aug 25, 2026 •

edited

Loading