chore!: version 4 💥💚📝, minor tweaks 📝

.github/workflows/build-publish.yml

@@ -49,7 +49,7 @@ jobs:
       with:
         push: true
         tags: |
-          ghcr.io/${{ github.repository }}:v3
+          ghcr.io/${{ github.repository }}:v4
           ghcr.io/${{ github.repository }}:${{ steps.docker-tags.outputs.permanent-tag }}
         labels: ${{ steps.docker-metadata.outputs.labels }}
         platforms: linux/amd64

README.md

@@ -1,6 +1,6 @@
 # PostGIS GTFS importer
 
-This tool **imports [GTFS Schedule](https://gtfs.org/schedule/) data into a [PostGIS](https://postgis.net) database using [`gtfs-via-postgres`](https://github.com/public-transport/gtfs-via-postgres)**. It allows running a production service (e.g. API) on top of programmatically re-imported data from a periodically changing GTFS feed without downtime.
+This tool **imports [GTFS Schedule](https://gtfs.org/schedule/) data into a [PostGIS](https://postgis.net) database using [`gtfs-via-postgres`](https://github.com/public-transport/gtfs-via-postgres)**. It allows running a production service (e.g. an API) on top of programmatically re-imported data from a periodically changing GTFS feed without downtime.
 
 Because it works as [atomically](https://en.wikipedia.org/wiki/Atomicity_(database_systems)) as possible with PostgreSQL, it makes the import pipeline *robust*, even if an import fails or if simultaneous imports get started.
 
@@ -31,7 +31,7 @@ docker run --rm -it \
 	-v $PWD/gtfs-tmp:/tmp/gtfs \
 	-e 'GTFS_DOWNLOAD_USER_AGENT=…' \
 	-e 'GTFS_DOWNLOAD_URL=…' \
-	ghcr.io/mobidata-bw/postgis-gtfs-importer:v3
+	ghcr.io/mobidata-bw/postgis-gtfs-importer:v4
 ```
 
 *Note:* We mount a `gtfs-tmp` directory to prevent it from re-downloading the GTFS dataset every time, even when it hasn't changed.

package.json

@@ -1,7 +1,7 @@
 {
 	"private": true,
 	"name": "postgis-gtfs-importer",
-	"version": "3",
+	"version": "4",
 	"type": "module",
 	"main": "index.js",
 	"bin": {