Unhandled error: HttpError: Resource not accessible by integration

contributions/cities/PY.json: Record 4 ("Altos"): "created_at" must not be included (auto-managed)

contributions/cities/PY.json: Record 4 ("Altos"): "id" must not be included (auto-managed)

contributions/cities/PY.json: Record 2 ("Acahay"): "flag" must not be included (auto-managed)

contributions/cities/PY.json: Record 2 ("Acahay"): "updated_at" must not be included (auto-managed)

contributions/cities/PY.json: Record 2 ("Acahay"): "created_at" must not be included (auto-managed)

contributions/cities/PY.json: Record 2 ("Acahay"): "id" must not be included (auto-managed)

contributions/cities/PY.json: Record 1 ("Abaí"): "flag" must not be included (auto-managed)

contributions/cities/PY.json: Record 1 ("Abaí"): "updated_at" must not be included (auto-managed)

contributions/cities/PY.json: Record 1 ("Abaí"): "created_at" must not be included (auto-managed)

contributions/cities/PY.json: Record 1 ("Abaí"): "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/

[FAIL] https://en.wikipedia.org/wiki/Alto_Paraguay_Department (HTTP 403)

contributions/cities/PY.json: Record 10 ("Bahía Negra") appears to be a duplicate of existing "Bahía Negra" (id: undefined, distance: 0.0km)

contributions/cities/PY.json: Record 9 ("Atyrá") appears to be a duplicate of existing "Atyrá" (id: 89723, distance: 0.0km)

contributions/cities/PY.json: Record 8 ("Arroyos y Esteros") appears to be a duplicate of existing "Arroyos y Esteros" (id: 89722, distance: 0.0km)

contributions/cities/PY.json: Record 7 ("Arquitecto Tomás Romero Pereira") appears to be a duplicate of existing "Arquitecto Tomás Romero Pereira" (id: 89721, distance: 0.0km)

contributions/cities/PY.json: Record 6 ("Areguá") appears to be a duplicate of existing "Areguá" (id: 89720, distance: 0.0km)

contributions/cities/PY.json: Record 5 ("Antequera") appears to be a duplicate of existing "Antequera" (id: 89719, distance: 0.0km)

contributions/cities/PY.json: Record 4 ("Altos") appears to be a duplicate of existing "Altos" (id: 89718, distance: 0.0km)

contributions/cities/PY.json: Record 3 ("Agua Dulce de Santa María") appears to be a duplicate of existing "Agua Dulce de Santa María" (id: undefined, distance: 0.0km)

contributions/cities/PY.json: Record 2 ("Acahay") appears to be a duplicate of existing "Acahay" (id: 89717, distance: 0.0km)

contributions/cities/PY.json: Record 1 ("Abaí") appears to be a duplicate of existing "Abaí" (id: 89716, distance: 0.0km)

contributions/cities/PY.json: Record 2 ("Acahay"): unknown field "native"

contributions/cities/PY.json: Record 2 ("Acahay"): unknown field "parent_id"

contributions/cities/PY.json: Record 2 ("Acahay"): unknown field "level"

contributions/cities/PY.json: Record 2 ("Acahay"): unknown field "type"

contributions/cities/PY.json: Record 1 ("Abaí"): unknown field "translations"

contributions/cities/PY.json: Record 1 ("Abaí"): unknown field "population"

contributions/cities/PY.json: Record 1 ("Abaí"): unknown field "native"

contributions/cities/PY.json: Record 1 ("Abaí"): unknown field "parent_id"

contributions/cities/PY.json: Record 1 ("Abaí"): unknown field "level"

contributions/cities/PY.json: Record 1 ("Abaí"): unknown field "type"