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
echo "::warning title=Package index sync failed::GitHub release assets were published, but Homebrew/Scoop sync did not complete. Check the release job logs."
518
+
echo "::warning title=Package index sync incomplete::GitHub release assets were published, but Homebrew/Scoop sync did not complete. Configure REPO_SYNC_TOKEN or update the package indexes manually."
echo "::warning title=AUR package sync failed::GitHub release assets were published, but the AUR package was not updated. Check the release job logs."
523
+
echo "::warning title=AUR package sync incomplete::GitHub release assets were published, but the AUR package was not updated. Configure AUR_SSH_PRIVATE_KEY or update the AUR package manually."
echo "::warning title=Mintlify deployment trigger failed::GitHub release assets were published, but the private Mintlify deployment endpoint did not accept the configured cookie. Rotate MINTLIFY_DEPLOY_COOKIE or trigger the deployment from the Mintlify dashboard."
528
+
echo "::warning title=Mintlify deployment incomplete::GitHub release assets were published, but docs deployment was not confirmed. Configure or rotate MINTLIFY_DEPLOY_COOKIE, or trigger the deployment from the Mintlify dashboard."
Copy file name to clipboardExpand all lines: CHANGELOG.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,23 @@ Before `1.0.0`, breaking changes may still ship in minor releases.
7
7
8
8
## [Unreleased]
9
9
10
+
## [0.12.0]
11
+
12
+
### Added
13
+
14
+
-`kagi assistant` now supports built-in and file-backed JSON contracts for prompt responses, validates the final Assistant output before printing it, and makes one repair attempt when the model returns invalid JSON.
15
+
- CLI failures can opt into structured JSON error envelopes with `--error-format json` or `KAGI_ERROR_FORMAT=json`.
16
+
-`kagi search --lens` now accepts exact enabled lens names as well as numeric lens positions.
17
+
-`kagi extract --filter` now reads HTTPS URLs from stdin and emits ordered JSONL records for pipeline-friendly batch extraction.
18
+
19
+
### Changed
20
+
21
+
- Release automation now emits explicit warnings when optional Homebrew, Scoop, AUR, or Mintlify sync credentials are missing or stale.
22
+
23
+
### Fixed
24
+
25
+
- Updated `quinn-proto` to clear the current RustSec `cargo audit` gate.
Copy file name to clipboardExpand all lines: docs/release-runbook.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,7 @@ Ship one version across the Rust CLI, GitHub release assets, npm wrapper, Homebr
17
17
-`REPO_SYNC_TOKEN` GitHub Actions secret for `Microck/homebrew-kagi` and `Microck/scoop-kagi`
18
18
-`AUR_SSH_PRIVATE_KEY` GitHub Actions secret for `ssh://aur@aur.archlinux.org/kagi-cli.git`
19
19
-`MINTLIFY_DEPLOY_COOKIE` GitHub Actions secret for the private Mintlify deployment trigger
20
+
Missing or stale optional sync credentials do not block GitHub release asset publication, but the release workflow emits explicit warnings and the affected channel must be recovered manually.
20
21
5. Confirm `CHANGELOG.md` has a complete user-facing entry ready to publish. The release workflow extracts notes from the `## [X.Y.Z]` section, so the heading must exist before the tag is pushed.
21
22
22
23
## Update release metadata
@@ -72,6 +73,7 @@ git push origin vX.Y.Z
72
73
- calls Mintlify's private deployment update endpoint when `MINTLIFY_DEPLOY_COOKIE` is configured
73
74
- syncs `Microck/homebrew-kagi` and `Microck/scoop-kagi`
74
75
- syncs the `kagi-cli` AUR package when `AUR_SSH_PRIVATE_KEY` is configured
76
+
- warns when optional package-index, AUR, or Mintlify sync work is skipped or fails after GitHub release publication
75
77
76
78
`.github/workflows/npm-publish.yml` runs after a successful `Release` workflow and publishes `npm/package.json` to npm when `NPM_PUBLISH_ENABLED=true`.
77
79
@@ -103,7 +105,7 @@ Verify all public release surfaces after the workflows finish:
103
105
7. Mintlify docs
104
106
- confirm `https://kagi.micr.dev` reflects the committed docs changes from `docs/`
105
107
- if the site still shows old content, inspect the `Trigger Mintlify docs deployment` release step
106
-
- if Mintlify rejected the private deployment trigger, rotate `MINTLIFY_DEPLOY_COOKIE` or trigger the deployment from the Mintlify dashboard
108
+
- if Mintlify rejected the private deployment trigger or the release emitted a Mintlify warning, rotate `MINTLIFY_DEPLOY_COOKIE` or trigger the deployment from the Mintlify dashboard
107
109
- verify the changed command, guide, or reference pages render correctly
108
110
8. Installers and scripts
109
111
-`scripts/install.sh` and `scripts/install.ps1` resolve the latest GitHub release dynamically, so they need no per-release version bump
@@ -176,6 +178,8 @@ Configure `MINTLIFY_DEPLOY_COOKIE` as a GitHub Actions secret containing the com
176
178
177
179
This uses a private dashboard endpoint, not a stable public API. If the cookie expires, Mintlify changes the endpoint, or Cloudflare rejects the request, the release workflow emits a warning and continues. Rotate the secret or trigger the deployment from the Mintlify dashboard.
178
180
181
+
The public docs site can still return HTTP 200 while serving an old deployment. Compare visible docs content or response metadata such as `last-modified` against the release changes before treating Mintlify as complete.
182
+
179
183
### Cargo
180
184
181
185
There is no crates.io publish step. `cargo install` currently pulls from GitHub, so no separate registry release is required.
0 commit comments