You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- refresh `sha256sums` for `https://github.com/Microck/kagi-cli/archive/refs/tags/vX.Y.Z.tar.gz`
97
+
- regenerate `.SRCINFO`
98
+
- push the AUR repo and confirm the package page shows `X.Y.Z`
99
+
7. Installers and scripts
94
100
-`scripts/install.sh` and `scripts/install.ps1` resolve the latest GitHub release dynamically, so they need no per-release version bump
95
101
- the npm wrapper downloads assets using `npm/package.json` version, so npm must stay in lockstep with the GitHub tag
96
102
@@ -114,14 +120,14 @@ The authoritative manifest lives in the companion bucket repo `Microck/scoop-kag
114
120
115
121
### AUR
116
122
117
-
There is no AUR automation in this repo and no AUR package metadata tracked here. If an external AUR package exists, update it manually after the GitHub release:
123
+
There is no AUR automation in this repo and no AUR package metadata tracked here. The maintained package is `kagi-cli` at `ssh://aur@aur.archlinux.org/kagi-cli.git`. Update it manually after the GitHub release:
118
124
119
-
1.bump `pkgver`
120
-
2.refresh checksums and any source URLs
121
-
3.publish the PKGBUILD update
122
-
4.verify a fresh `paru` or `yay` install resolves the new version
123
-
124
-
If no AUR package is maintained, skip this section.
125
+
1.clone or update `ssh://aur@aur.archlinux.org/kagi-cli.git`
126
+
2.bump `pkgver` in `PKGBUILD`
127
+
3.refresh `sha256sums` for `https://github.com/Microck/kagi-cli/archive/refs/tags/vX.Y.Z.tar.gz`
128
+
4.regenerate `.SRCINFO`
129
+
5. commit and push the AUR repo
130
+
6. verify the package page or a fresh `paru` or `yay` install resolves the new version
0 commit comments