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-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.

ahliweb · 2026-09-05T06:07:33Z

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.

Meaningful developments since the previous watch:

Upstream fix(core): add byline to generated collection interfaces (Fixes #2888) emdash-cms/emdash#2889 (fix(core): add byline to generated collection interfaces) advanced to 4d9f29b91b4c33ad1137860ff8c36ce76c5a3f53 with chore(types): regenerate template emdash-env types and refine changeset. This directly addresses the automated review findings: committed generated emdash-env.d.ts files in templates/demos/fixtures were stale and the changeset was implementation-focused rather than reader-facing. The PR now regenerates the tracked declaration files and refines the release note. GitHub reports the PR open/mergeable. Its latest Actions are action_required rather than technical failures, so the refreshed head has not yet received normal CI execution. The change is type-generation/generated declaration scope only and introduces no admin UI msgids, so it adds no direct Indonesian locale debt.
Upstream fix(core): add includeCounts opt-out to getTerm emdash-cms/emdash#2812 (fix(core): add includeCounts opt-out to getTerm) was merged/rebased with current main at head 6546727dccbb45fbe33d5dbe80b8c32d46792165 and remains open/mergeable. Its prior automated review found no logic regression; the only review suggestions were comment-discipline cleanups and are now outdated. The refreshed head's workflows are currently action_required, not failing. This PR changes taxonomy/query performance behavior and templates but no admin user-visible strings, so it does not change the Indonesian extraction horizon.

PR #83 itself remains open/not mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewer. No branch mutation was applied: fork main is already synchronized and there is no newer extraction to reconcile. Deterministic msgid-based reconciliation against 108c753b..., zero-untranslated/fuzzy validation, translation-only diff verification, and full refreshed-head CI are still required before merge readiness. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-05T08:26:44Z

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.

Meaningful change since the previous watch: upstream emdash-cms#2889 (fix(core): add byline to generated collection interfaces) was closed without merge at 2026-09-05 07:14 UTC. Its final head remained 4d9f29b91b4c33ad1137860ff8c36ce76c5a3f53. The PR had already corrected its stale generated emdash-env.d.ts files and release-note wording, but because it was closed unmerged, none of those type-generation changes can affect main, the locale extraction baseline, or PR #83 unless the work is revived in another PR. No maintainer closure rationale is visible in the PR conversation, so the safe conclusion is only that this candidate is no longer on the active merge horizon.

PR #83 itself remains open/not mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewers, submitted reviews, or review threads. Its old-head workflow state is unchanged: CI, Format, Query Counts, Visual Regression, CodeQL, zizmor, and Auto Format pass; Preview Releases remains the historical failure, and Dependabot Auto-Approve is skipped.

No branch mutation is appropriate in this check: fork main is current and there is no newer extraction. Deterministic msgid-based reconciliation against 108c753b..., zero-untranslated/fuzzy validation, translation-only diff verification, and full refreshed-head CI remain required before merge readiness. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-05T09:04:44Z

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

Material change: upstream PR emdash-cms#2889 (fix(core): add byline to generated collection interfaces) was reopened and now points at head 97966fd5ba2b98378fddf38284c9e8d4ff0e48a4. GitHub reports it open and mergeable. The latest head incorporates the earlier review fixes for stale committed emdash-env.d.ts files and the reader-facing changeset. The changeset bot now detects patch releases across 17 packages because those regenerated declaration files span templates/demos/fixtures and package surfaces.

The current head has not received normal Actions validation yet: CI, Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, Auto Format, and Dependabot Auto-Approve all show action_required, which is an execution-approval state rather than evidence of test failure. The PR does not add admin UI strings or messages.po changes, so it creates no direct Indonesian locale debt if merged; at most a post-merge extraction could move generated source references.

No action is required on the Indonesian branch in this check because main has not advanced. PR #83 remains blocked on deterministic msgid-based reconciliation against the current extracted catalog, refreshed-head validation, and contributor-owned CLA completion. No legal agreement was signed or accepted by automation.

ahliweb · 2026-09-05T13:34:49Z

Upstream watch update — 2026-09-05

Meaningful developments since the previous checkpoint:

Upstream emdash-cms/emdash:main remains at 108c753b9b266c1d050bdb40dba4f7a09517ee3d, and fork ahliweb/emdash-awcms:main matches it exactly. There is no newer merged locale extraction to synchronize.
New draft upstream PR feat(core): lock a content entry while someone is editing it emdash-cms/emdash#2919 (feat(core): lock a content entry while someone is editing it, head ec78032e6a97639e19d8c5ae7ffee5521a56d21a) is mergeable and introduces new Lingui-wrapped admin strings for edit locking/read-only/take-over flows (Edit locking, This entry is open somewhere else, Open read-only, Take over, etc.). Its locale catalogs are intentionally deferred until after merge, so refreshing this Indonesian branch from the draft would be premature.
feat(core): lock a content entry while someone is editing it emdash-cms/emdash#2919 is not CI-green yet. The aggregate CI failure has two distinct red jobs: Integration Tests fails during pnpm install --frozen-lockfile before tests execute, while Browser Tests completes install/build and then fails at pnpm --filter @emdash-cms/admin test. Other visible checks/subchecks including typecheck, lint, smoke, E2E, Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, and Auto Format pass. The scope guard also flags the PR as large (3,518 lines / 58 files). There are no submitted reviews or review threads yet.
Upstream issue Post entry not returning properly with fallback locale when Astro's i18n prefixDefaultLocale disabled. emdash-cms/emdash#1679 received a fresh reproduction confirming the fallback-locale defect is still present in 0.36.0. The fallback chain itself is computed correctly; the defect is that a first-locale miss becomes LiveEntryNotFoundError and resolveNormal returns on that error instead of continuing to the next locale. The serveDrafts path has the same early-return defect, making its intended continue unreachable. This affects runtime content i18n but does not change the admin locale catalog yet.
PR i18n(id): refresh Indonesian admin translations #83 remains on b841cd537aa2f802360b2b63e0a879cab81183cd, with no submitted reviews, unresolved review threads, or requested reviewers. Old-head checks remain unchanged: CI/Format/Query Counts/Visual Regression/CodeQL/zizmor/Auto Format pass; Preview Releases remains the historical failure. Existing CLA and Lunaria requirements remain; no legal agreement was signed or accepted.
No new Dependabot PR/update was found in this interval.

No branch mutation was applied: fork main is already synchronized, there is no new merged extraction, and applying candidate emdash-cms#2919 strings before merge would create avoidable churn. The Indonesian branch should still be reconciled deterministically by msgid against the latest merged extraction before refreshed-head CI.

ahliweb · 2026-09-05T19:26:09Z

Upstream watch update (2026-09-06): upstream and fork main remain synchronized at 108c753b9b266c1d050bdb40dba4f7a09517ee3d; no new merged commit or locale extraction has landed.

Meaningful merge-horizon change: draft upstream emdash-cms#2919 (feat(core): lock a content entry while someone is editing it) received an overlap warning. GitHub reports shared files with emdash-cms#2891 (5), emdash-cms#2799 (13), emdash-cms#1928 (13), emdash-cms#1844 (4), emdash-cms#1526 (3), emdash-cms#1365 (6), emdash-cms#2807 (3), emdash-cms#2864 (3), and emdash-cms#2352 (3). This does not itself create a conflict on main, but it materially raises the likelihood that emdash-cms#2919 will be rebased, split, or otherwise revised before merge. Because emdash-cms#2919 introduces new translatable entry-locking strings and intentionally leaves catalog extraction to post-merge automation, #83 should continue to reconcile against the extraction actually produced after any such merge rather than against emdash-cms#2919's current draft source positions.

No translation-branch mutation is appropriate in this check: fork main is current and there is no newer extraction. CLA remains contributor-owned; no legal agreement was signed or accepted.

ahliweb · 2026-09-05T22:12:25Z

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

Meaningful merge-horizon change: upstream draft PR emdash-cms#2921 (fix: pre-bundle lowlight and highlight.js for inline Portable Text editor hydration) was opened from issue emdash-cms#2916 after the reporter confirmed the preview candidate against their own site. Root cause: the inline Portable Text editor statically pulls in lowlight, which default-imports CommonJS highlight.js/lib/core; in affected Vite dev configurations that deep import is served without the ESM interop wrapper, so hydration fails even when the content contains no code block. The fix adds lowlight, highlight.js, and highlight.js/lib/core to optimizeDeps.include for both source-mode and dist-mode dev and adds regression coverage for both paths.

emdash-cms#2921 is currently draft but GitHub reports it mergeable. Head 5e946bec5b2b12cb5bf3117e8c5b202f67f39e06 has CI, Format, Query Counts, Visual Regression, Preview Releases, CodeQL, and zizmor passing; Auto Format and Dependabot Auto-Approve are skipped rather than failed. There are no submitted reviews or review threads yet. Changeset bot reports a patch release fan-out across 17 packages.

The patch changes only a changeset, Vite integration config, and focused tests; it contains no admin UI strings or messages.po changes, so it creates no direct Indonesian locale delta. No translation-branch mutation is appropriate until a newer extraction actually lands on main.

PR #83 itself remains open/not mergeable on b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviewer, submitted review, or unresolved review thread. Its old-head checks remain unchanged (CI/Format/Query Counts/Visual Regression/CodeQL/zizmor/Auto Format green; historical Preview Releases failure). CLA remains contributor-owned and was not signed or accepted by automation.

ahliweb · 2026-09-06T00:51:16Z

Upstream watch update (2026-09-06): meaningful translation-process signal, but no new main/locale extraction landed.

Upstream emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at 108c753b9b266c1d050bdb40dba4f7a09517ee3d (chore: extract locale catalogs [skip ci]). PR i18n(id): refresh Indonesian admin translations #83 remains open/not mergeable on b841cd537aa2f802360b2b63e0a879cab81183cd, now 1 commit ahead / 48 behind main, with the same 2-file translation scope.
New upstream draft PR i18n(de): complete the remaining German admin translations emdash-cms/emdash#2922 (i18n(de): complete the remaining German admin translations) was opened directly from the same 108c753b... extraction. It changes only a changeset plus packages/admin/src/locales/de/messages.po, fills 376 empty msgstr entries, and reports msgfmt --check-format plus pnpm --filter @emdash-cms/admin locale:compile clean. Its full current GitHub Actions set is green: CI, Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, and Auto Format; Dependabot Auto-Approve is skipped.
Root-cause/process significance for i18n(id): refresh Indonesian admin translations #83: i18n(de): complete the remaining German admin translations emdash-cms/emdash#2922 confirms that the expected merge-ready shape for a large translation refresh is still a 2-file translation-only PR based on the latest extracted catalog, with placeholder/ICU validation, locale compilation, terminology consistency, and UI/manual review. Its successful Preview Releases run also shows that i18n(id): refresh Indonesian admin translations #83's historical Preview Releases failure is not inherently caused by being a translation-only PR; i18n(id): refresh Indonesian admin translations #83 needs a refreshed-head rerun after reconciliation rather than treating that old failure as a structural blocker.
i18n(de): complete the remaining German admin translations emdash-cms/emdash#2922 triggered the scope guard at 757 changed lines / 2 files, but the bot explicitly says no action is required if the scope is intentional. Changeset-bot also reports the same broad 17-package patch fan-out seen elsewhere; that is release tooling behavior, not evidence of extra runtime scope.
No maintainer review/request or unresolved review thread has appeared on i18n(id): refresh Indonesian admin translations #83. CLA and Lunaria requirements remain unchanged; no CLA or other legal agreement was signed or accepted.
No new Dependabot PR/update was found in the checked interval.

No branch mutation was applied in this run: the fork is already synchronized and deterministic msgid-based reconciliation of the full Indonesian catalog is still the next safe mutation. That refresh should preserve reviewed msgstr values by msgid, fill every newly empty entry from 108c753b..., verify zero untranslated/fuzzy entries and ICU/placeholders, run msgfmt --check-format and locale:compile, confirm the 2-file diff scope, then rerun the complete CI suite.

ahliweb · 2026-09-06T02:03:17Z

Upstream watch update (2026-09-06): emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at locale extraction 108c753b9b266c1d050bdb40dba4f7a09517ee3d; PR #83 is still 1 commit ahead / 48 behind with merge base dd325cb..., scope limited to the changeset and Indonesian messages.po, and GitHub still reports it not mergeable.

Meaningful merge-horizon change: upstream emdash-cms#1944 (fix(i18n): localize invite, magic-link, and recovery emails) has had its stale label removed and is currently open, non-draft, and mergeable at bb84501424adaf232e70a4dc72f129b8da9afb18. Its current head has CI, Format, Query Counts, Preview Releases, CodeQL, zizmor, and Auto Format passing (Dependabot auto-approve skipped). If merged, Lingui extraction will add Indonesian debt: at minimum Jane Doe plus system-email descriptors such as You've been invited to {siteName}, You've been invited to join {siteName}., Accept Invite, Sign in to {siteName}, Sign in, expiry/instruction copy, and the safe-ignore notice.

Root cause: emdash-cms#1944 moves previously hardcoded English auth-email copy into admin-owned Lingui descriptors while keeping @emdash-cms/auth i18n-free through injected strings. This is architecturally relevant to #83 because those descriptors are intentionally extracted only after merge.

emdash-cms#1944 still has unresolved, non-outdated review threads. Several are already functionally addressed but not marked resolved; one substantive remaining suggestion notes that site option emdash:locale is returned verbatim, so a non-canonical BCP 47 value such as pt-br could miss the pt-BR catalog and silently fall back to English. Another thread disputes whether narrowing the locale import actually avoids the Vite/macro path. These may still cause a follow-up commit and source-reference movement before merge.

No speculative translation-branch mutation was applied in this check: current upstream main has not changed, and refreshing #83 immediately before an active i18n PR with unresolved threads lands would create avoidable churn. The next deterministic reconciliation should continue to use the extraction actually present on main, preserving reviewed Indonesian msgstr by msgid, then validate zero untranslated/fuzzy entries, ICU/placeholders, translation-only diff scope, and full refreshed-head CI.

No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-06T07:17:22Z

Upstream watch update (2026-09-06): meaningful review/readiness change on upstream emdash-cms#2921 (fix: pre-bundle lowlight and highlight.js for inline Portable Text editor hydration).

Upstream and fork main remain synchronized at locale extraction 108c753b9b266c1d050bdb40dba4f7a09517ee3d; no newer locale extraction has landed, so no fork sync or Indonesian catalog mutation is required in this check.
fix: pre-bundle lowlight and highlight.js for inline Portable Text editor hydration emdash-cms/emdash#2921 advanced from the previously reported candidate to head 226f3aa983c890d46c1ea1c80af434cef2804f4d, is now non-draft and mergeable, and has 2 commits / 4 changed files.
Maintainer ascorbic submitted CHANGES_REQUESTED on 2026-09-06. The substantive request was that the existing optimizeDeps unit assertion was too shallow and should include an E2E regression proving the inline Portable Text editor actually appears in visual editing mode; a second request asked to remove excessive inline comments.
Root cause of the requested revision: the first regression test only verified configuration entries and could pass without proving browser hydration behavior. The bot revised the branch by trimming the comments and adding a focused E2E hydration regression (fix: pre-bundle lowlight and highlight.js, add E2E regression for inline PT editor hydration). This closes the coverage gap rather than changing the underlying fix strategy.
Refreshed head validation is green: CI, Format, Query Counts, Visual Regression, Preview Releases, CodeQL, and zizmor all succeeded; Auto Format and Dependabot Auto-Approve are skipped. The Cloudflare preview build/deployment for 226f3aa also succeeded.
Review state still has one unresolved, non-outdated thread carrying the E2E request, even though the follow-up commit appears to implement it; the earlier comment-cleanup thread is unresolved but outdated. Therefore fix: pre-bundle lowlight and highlight.js for inline Portable Text editor hydration emdash-cms/emdash#2921 still needs maintainer re-review/approval before it is truly merge-ready.
fix: pre-bundle lowlight and highlight.js for inline Portable Text editor hydration emdash-cms/emdash#2921 changes core Vite config/tests/changeset only and adds no admin messages.po or user-visible msgids, so it creates no direct Indonesian translation debt.
PR i18n(id): refresh Indonesian admin translations #83 remains open/not mergeable on b841cd537aa2f802360b2b63e0a879cab81183cd, with the historical old-head Preview Releases failure and all other listed checks green. No CLA or other legal agreement was signed or accepted.

No translation-branch mutation was applied: current main has not moved, and #83 still requires the previously identified deterministic msgid-based reconciliation against 108c753b..., zero-untranslated/fuzzy validation, translation-only diff verification, and refreshed-head CI.

ahliweb · 2026-09-06T08:06:25Z

Upstream watch update (2026-09-06): material main-branch movement and one safe repository action applied.

Upstream emdash-cms/emdash:main advanced from 108c753b9b266c1d050bdb40dba4f7a09517ee3d to 67f676d1e8209d8885532f0f6114bc3686167d34 by merging fix: pre-bundle lowlight and highlight.js for inline Portable Text editor hydration emdash-cms/emdash#2921 (fix: pre-bundle lowlight and highlight.js for inline Portable Text editor hydration).
Root cause: the inline Portable Text editor statically imports lowlight, which default-imports CommonJS highlight.js/lib/core; in the affected Vite dev path the deep CJS module could be served without an ESM interop wrapper, causing the Astro island to fail hydration and collapse to empty content. The merged fix pre-bundles lowlight, highlight.js, and highlight.js/lib/core and includes both focused Vite-config coverage and an E2E assertion that the inline PT editor visibly hydrates with non-zero height/content.
This merge does not change packages/admin/src/locales/*/messages.po or add admin user-visible msgids. The changed files are the changeset, visual-editing E2E test, core Vite config, and its unit test. Therefore the latest Indonesian locale extraction remains the one at 108c753b...; there is no new translation delta caused by fix: pre-bundle lowlight and highlight.js for inline Portable Text editor hydration emdash-cms/emdash#2921.
Issue Inline Portable Text editor disappears in dev when Highlight.js fails to hydrate emdash-cms/emdash#2916 was closed as completed immediately after the merge and marked bot:done.
Safe action applied: fork ahliweb/emdash-awcms:main was fast-forwarded atomically to 67f676d1e8209d8885532f0f6114bc3686167d34; revalidation confirms fork and upstream main now match exactly.
PR i18n(id): refresh Indonesian admin translations #83 remains open/not mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, still 1 commit / 2 files, with no requested reviewer, submitted review, or unresolved review thread. Its old-head checks are unchanged: CI, Format, Query Counts, Visual Regression, CodeQL, zizmor, and Auto Format succeeded; Preview Releases remains the historical failure.
No PR-branch rewrite was applied in this run because fix: pre-bundle lowlight and highlight.js for inline Portable Text editor hydration emdash-cms/emdash#2921 does not alter the extracted catalog. The branch still needs the previously identified deterministic msgid-based reconciliation against the current extracted Indonesian catalog, zero untranslated/fuzzy validation, translation-only diff verification, and full refreshed-head CI.
A new upstream tooling PR Handle maintainer reviews on bot pull requests emdash-cms/emdash#2924 (Handle maintainer reviews on bot pull requests) opened in this interval, but it changes bot review-state handling and has no direct locale or PR i18n(id): refresh Indonesian admin translations #83 merge requirement at present.

No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-06T08:56:52Z

Upstream watch update (2026-09-06): upstream and fork main remain synchronized at 67f676d1e8209d8885532f0f6114bc3686167d34; no newer locale extraction has landed, so no fork sync or Indonesian catalog rewrite is required in this check.

Meaningful merge-readiness development: upstream emdash-cms#2924 (Handle maintainer reviews on bot pull requests) received a fresh automated review at 1816a74399303dd1c303d5b76558bbbb242c416e. The PR is still open/non-draft/GitHub-mergeable and all exposed workflows are green (CI, Format, Query Counts, Preview Releases, CodeQL, zizmor, Auto Format; Dependabot Auto-Approve skipped), but the review identified four concrete state-machine/orchestrator gaps and the PR is now labeled review/awaiting-author:

failed and awaiting_feedback accept the new revise transition but do not advertise revise in offeredCommands, so status/help output hides a valid command.
Deferred revise inbox entries can survive a pr.closed event and later restart revision work on a closed PR unless they are purged when the PR lifecycle ends.
outcomeFromResult does not explicitly handle revise mode, so enhancement revisions returning implemented: true can be misclassified as agent.failed unless fixed: true is also set.
pr.changes_requested is now dead state-machine surface because the webhook normalizer dispatches revise directly instead.

Root cause: emdash-cms#2924 adds the missing feedback loop for maintainer review of bot-generated PRs, but the new revise event was wired into transition handling without fully updating command discoverability, terminal-event queue cleanup, result classification semantics, and removal of the superseded event path. These are bot-orchestration correctness issues, not locale/catalog changes, so they do not justify mutating i18n/id-refresh-2026-08-26.

PR #83 itself remains open/not mergeable on b841cd537aa2f802360b2b63e0a879cab81183cd, with no submitted review and no requested reviewer. Its old-head Actions state is unchanged: CI/Format/Query Counts/Visual Regression/CodeQL/zizmor/Auto Format pass and Preview Releases remains the historical failure. The branch still needs deterministic msgid-based reconciliation against the latest extracted Indonesian catalog before a safe refreshed head can be produced.

No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-06T10:26:02Z

Upstream watch update (2026-09-06): upstream emdash-cms/emdash:main advanced from 67f676d1e8209d8885532f0f6114bc3686167d34 to 603062902369d9695608e85c2d034d4f66f7a1f1 via merged emdash-cms#2924 (Handle maintainer reviews on bot pull requests). The commit is confined to infra/emdash-bot state-machine/orchestrator/webhook code and tests; comparison shows no admin locale catalog or translation-source change.

Root cause addressed by emdash-cms#2924: the bot review-feedback flow had incomplete lifecycle wiring. revise was accepted but not advertised in some states, queued review revisions could survive a PR close/merge and later emit a stale noop response, and the obsolete pr.changes_requested event remained after webhook normalization moved directly to revise. The merged fix aligns offered commands with transitions, discards queued revisions on PR close/merge, and removes the dead event surface.

I fast-forwarded fork ahliweb/emdash-awcms:main atomically to 603062902369d9695608e85c2d034d4f66f7a1f1. Revalidation: PR #83 remains open/not mergeable at head b841cd537aa2f802360b2b63e0a879cab81183cd; comparison with current fork main is now 1 commit ahead / 50 behind, merge base dd325cb1629f77fdac7f6494be8b752322812024, with scope still limited to .changeset/bright-id-refresh.md and packages/admin/src/locales/id/messages.po. No submitted reviews, requested reviewers, or unresolved review threads are present. Old-head Actions remain unchanged: CI, Format, Query Counts, Visual Regression, CodeQL, zizmor, and Auto Format pass; Preview Releases is the historical failure; Dependabot Auto-Approve is skipped.

No Indonesian branch rewrite was applied because emdash-cms#2924 adds no locale delta. The branch still requires deterministic msgid-based reconciliation against the latest extracted catalog before refreshed-head CI. No CLA or other legal agreement was signed or accepted.

ahliweb · 2026-09-06T13:14:51Z

Upstream watch update (2026-09-06): upstream and fork main remain synchronized at 603062902369d9695608e85c2d034d4f66f7a1f1; no new locale extraction has landed since the previous check.

Two new draft bot PRs entered the merge horizon:

fix: align OpenAPI content terms spec with shipped route emdash-cms/emdash#2925 (fix: align OpenAPI content terms spec with shipped route, head 50a7672808e43570ec38595049aa60d487b9ca0f) corrects a stale OpenAPI contract: the spec documented PUT /_emdash/api/content/{collection}/{id}/terms, while the shipped implementation exposes GET/POST /_emdash/api/content/{collection}/{id}/terms/{taxonomy}. The candidate removes the nonexistent bare route from the spec, documents the nested taxonomy route, adds response schemas and a regression test. It is draft and currently mergeable. It does not touch admin UI strings or messages.po.
feat(mcp): add taxonomy definition CRUD tools and fix translationOf inheritance emdash-cms/emdash#2926 (feat(mcp): add taxonomy definition CRUD tools and fix translationOf inheritance, head fb50f88beb40500a0633124c0972eeb2b27f0f6f) adds MCP taxonomy-definition CRUD and fixes translated taxonomy definitions losing inherited hierarchical/collections defaults. Root cause: REST definition CRUD existed but MCP exposed only term-level writes, and the taxonomy-create schema defaulted omitted values before translationOf inheritance could distinguish omission from an explicit value. It is draft and currently mergeable. It also does not add admin locale strings.

Both new heads show the same CI pattern: Format, Query Counts, Visual Regression, Preview Releases, CodeQL and zizmor pass, while aggregate CI fails specifically at Smoke Tests; the dedicated Typecheck and Integration Tests checked on emdash-cms#2925 pass, and preview build/deployment succeeds. Because two independent bot PRs based on the same 6030629... base fail the same smoke job while their scoped changes are unrelated to smoke behavior, this currently points more strongly to a shared smoke-test/baseline or environment regression than to either PR's patch. It is still a blocker for those upstream PRs until upstream reruns or fixes it, but it does not create a translation-branch action.

PR #83 itself remains open/not mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, with no requested reviews or unresolved review threads. Its historical head checks remain unchanged: CI/Format/Query Counts/Visual Regression/CodeQL/zizmor/Auto Format pass; Preview Releases is the old failure. No branch rewrite is warranted until a new locale extraction actually lands. CLA remains contributor-owned and was not signed or accepted by automation.

ahliweb · 2026-09-06T18:32:39Z

Upstream watch update (2026-09-07): emdash-cms/emdash:main and fork main remain synchronized at 603062902369d9695608e85c2d034d4f66f7a1f1; no new locale extraction has landed.

Meaningful merge-horizon change: upstream PR emdash-cms#2891 (fix(admin): refine publishing and scheduling controls) is now reported as not mergeable and carries needs-rebase, overlap, and review/needs-rereview; maintainer ascorbic is requested for review. Its current head remains 90c03bf4cfcd485d188ac22b0c3eb286d5fbc905, and all workflows on that head are still green (CI, Format, Query Counts, Visual Regression, Preview Releases, CodeQL, zizmor, Auto Format; Dependabot Auto-Approve skipped). There are no unresolved review threads.

Root cause is branch divergence / merge conflict risk rather than a failing implementation: the candidate has not been refreshed onto the current main, while it overlaps heavily with other admin/core work. Because emdash-cms#2891 adds localized publishing/scheduling UI strings, a rebase or conflict resolution can still shift or revise extraction inputs before merge. Therefore the Indonesian branch should continue to reconcile only against the locale extraction that actually lands on main, not against emdash-cms#2891's current candidate diff.

No change to i18n/id-refresh-2026-08-26 is required in this check. CLA remains contributor-owned; no legal agreement was signed or accepted by automation.

ahliweb · 2026-09-06T20:06:46Z

Upstream watch update (2026-09-07): emdash-cms/emdash:main and fork ahliweb/emdash-awcms:main remain synchronized at 603062902369d9695608e85c2d034d4f66f7a1f1; no new locale extraction has landed since the previous check.

Meaningful merge-horizon change: upstream PR emdash-cms#2891 (fix(admin): refine publishing and scheduling controls) has been reconciled with current main. Its head advanced from 90c03bf... to 3b889aa2f6b8f586d775f06b8d4c41561b169ca1 via a direct merge of main, and GitHub now reports it mergeable again. This resolves the earlier needs-rebase/conflict state. Root cause of the previous non-mergeability was branch divergence/overlap rather than a failing implementation: the refreshed branch now has current upstream history while retaining the localized publishing/scheduling work.

Maintainer ascorbic remains requested for review; the bot review on the PR is approved and there are no unresolved review threads. The fresh head has zizmor and Auto Format already passing; CI is queued and Format, Query Counts, Visual Regression, Preview Releases, and CodeQL are still in progress at the time of this check. Dependabot Auto-Approve is skipped. Therefore emdash-cms#2891 is no longer conflict-blocked, but its refreshed-head CI is not yet fully complete.

This matters to the Indonesian refresh because emdash-cms#2891 contains Lingui-wrapped user-facing publishing/scheduling strings and is now materially closer to merge. If it lands before #83 is reconciled, the post-merge extraction may add/move msgids that should be included in the deterministic Indonesian PO refresh. No speculative translation-branch rewrite was performed because upstream main itself has not changed and no new catalog extraction exists yet.

PR #83 remains open and not mergeable at b841cd537aa2f802360b2b63e0a879cab81183cd, with the historical old-head Preview Releases failure and otherwise green old-head checks. No maintainer review, review request, or unresolved review thread has appeared on #83. No CLA or other legal agreement was signed or accepted by automation.

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 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 Sep 5, 2026

Uh oh!

ahliweb commented Sep 5, 2026

Uh oh!

ahliweb commented Sep 5, 2026

Uh oh!

ahliweb commented Sep 5, 2026

Upstream watch update — 2026-09-05

Uh oh!

ahliweb commented Sep 5, 2026

Uh oh!

ahliweb commented Sep 5, 2026

Uh oh!

ahliweb commented Sep 6, 2026

Uh oh!

ahliweb commented Sep 6, 2026

Uh oh!

ahliweb commented Sep 6, 2026

Uh oh!

ahliweb commented Sep 6, 2026

Uh oh!

ahliweb commented Sep 6, 2026

Uh oh!

ahliweb commented Sep 6, 2026

Uh oh!

ahliweb commented Sep 6, 2026

Uh oh!

ahliweb commented Sep 6, 2026

Uh oh!

ahliweb commented Sep 6, 2026

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