contributions/cities/MY.json: Record 3 ("Ampang"): "created_at" must not be included (auto-managed)

contributions/cities/MY.json: Record 3 ("Ampang"): "id" must not be included (auto-managed)

contributions/cities/MY.json: Record 2 ("Alor Setar"): "flag" must not be included (auto-managed)

contributions/cities/MY.json: Record 2 ("Alor Setar"): "updated_at" must not be included (auto-managed)

contributions/cities/MY.json: Record 2 ("Alor Setar"): "created_at" must not be included (auto-managed)

contributions/cities/MY.json: Record 2 ("Alor Setar"): "id" must not be included (auto-managed)

contributions/cities/MY.json: Record 1 ("Alor Gajah"): "flag" must not be included (auto-managed)

contributions/cities/MY.json: Record 1 ("Alor Gajah"): "updated_at" must not be included (auto-managed)

contributions/cities/MY.json: Record 1 ("Alor Gajah"): "created_at" must not be included (auto-managed)

contributions/cities/MY.json: Record 1 ("Alor Gajah"): "id" must not be included (auto-managed)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/github-script@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

contributions/cities/MY.json: Record 10 ("Banting") appears to be a duplicate of existing "Banting" (id: 76418, distance: 0.0km)

contributions/cities/MY.json: Record 9 ("Bandar Labuan") appears to be a duplicate of existing "Bandar Labuan" (id: 76417, distance: 0.0km)

contributions/cities/MY.json: Record 8 ("Bakri") appears to be a duplicate of existing "Bakri" (id: 76416, distance: 0.0km)

contributions/cities/MY.json: Record 7 ("Bahau") appears to be a duplicate of existing "Bahau" (id: 76415, distance: 0.0km)

contributions/cities/MY.json: Record 6 ("Bagan Serai") appears to be a duplicate of existing "Bagan Serai" (id: 76414, distance: 0.0km)

contributions/cities/MY.json: Record 5 ("Bagan Pulau Ketam") appears to be a duplicate of existing "Bagan Pulau Ketam" (id: 76413, distance: 0.0km)

contributions/cities/MY.json: Record 4 ("Ayer Hangat") appears to be a duplicate of existing "Ayer Hangat" (id: 76412, distance: 0.0km)

contributions/cities/MY.json: Record 3 ("Ampang") appears to be a duplicate of existing "Ampang" (id: 76411, distance: 0.0km)

contributions/cities/MY.json: Record 2 ("Alor Setar") appears to be a duplicate of existing "Alor Setar" (id: 76410, distance: 0.0km)

contributions/cities/MY.json: Record 1 ("Alor Gajah") appears to be a duplicate of existing "Alor Gajah" (id: 76409, distance: 0.0km)

contributions/cities/MY.json: Record 2 ("Alor Setar"): unknown field "native"

contributions/cities/MY.json: Record 2 ("Alor Setar"): unknown field "parent_id"

contributions/cities/MY.json: Record 2 ("Alor Setar"): unknown field "level"

contributions/cities/MY.json: Record 2 ("Alor Setar"): unknown field "type"

contributions/cities/MY.json: Record 1 ("Alor Gajah"): unknown field "translations"

contributions/cities/MY.json: Record 1 ("Alor Gajah"): unknown field "population"

contributions/cities/MY.json: Record 1 ("Alor Gajah"): unknown field "native"

contributions/cities/MY.json: Record 1 ("Alor Gajah"): unknown field "parent_id"

contributions/cities/MY.json: Record 1 ("Alor Gajah"): unknown field "level"