Skip to content

ci: add monthly auto-update workflow for jp zipcode data#13

Open
stjean2016 wants to merge 1 commit into
masterfrom
ci/jp-zipcode-auto-update
Open

ci: add monthly auto-update workflow for jp zipcode data#13
stjean2016 wants to merge 1 commit into
masterfrom
ci/jp-zipcode-auto-update

Conversation

@stjean2016

Copy link
Copy Markdown
Contributor

Adds a GitHub Actions workflow that keeps the Japan Post postal-code data fresh automatically, so jp/*.json no longer silently goes stale.

What it does

  • Triggers: workflow_dispatch (manual) + monthly cron (5th of each month, ~after Japan Post's month-end release).
  • Steps: checkout → set up Go → run japanpost/gen.sh (downloads KEN_ALL_ROME, builds the processor for the runner, regenerates jp/*.json + jp.tar.gz) → if the data changed, open a PR.
  • Merging that data PR triggers the existing S3 Sync workflow, which publishes the new files to S3.

⚠️ Depends on #12

This relies on the download-URL / pipeline fixes in #12 — the gen.sh currently on master still points at the dead URL and can't build the processor on Linux. Merge #12 first, otherwise this workflow's download/build step will fail.

Repo setting required

For the workflow to open PRs automatically, enable Settings → Actions → General → Workflow permissions → "Allow GitHub Actions to create and approve pull requests."

🤖 Generated with Claude Code

workflow_dispatch + monthly cron that runs japanpost/gen.sh to regenerate
jp/*.json and jp.tar.gz from Japan Post's KEN_ALL_ROME, then opens a PR when
the data changes. Merging that PR triggers the existing S3 Sync workflow.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant