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
chore(release): prepare v1.1.0 and weekly Sat 9am PT cadence
Bump backend to 1.1.0, add release notes/changelog for progressive
dashboards and multi-schema/Performance UX, and document the weekly
Saturday 09:00 America/Los_Angeles release automation.
Co-authored-by: Venkat SF <venkatesh.sakamuri@stayflexi.com>
- Multi-schema awareness across Editor, Brain, and Advisor UI (#55).
25
+
- Slow Queries and Workload Analysis merged into a single Performance area (#52).
26
+
27
+
### Fixed
28
+
29
+
- CI: remove CodeQL visibility guard that blocked merges (#56).
30
+
- Cloud agent ops notes for Hermes MCP restart and multi-schema fixtures (#53).
31
+
32
+
### Notes
33
+
34
+
-`@deepsql/mcp` remains `0.27.0` for this cut (no MCP API changes required).
35
+
- Hand-apply SQL changelog `V111`–`V114` when not using `ddl-auto=update`.
36
+
9
37
## [1.0.0] — 2026-08-13
10
38
11
39
First public OSS release.
@@ -31,4 +59,5 @@ First public OSS release.
31
59
- Residual high-severity items tracked in `docs/oss-ux/OSS_SECURITY_REVIEW.md` (IDOR sweep, SET preamble allowlist, SSRF hardening, share-password defaults) are deferred past this cut.
32
60
- Primary distribution path remains `docker compose up --build` (no pre-built container registry in this release).
Product **releases** are weekly (Saturday 09:00 PT) — see [`WEEKLY_RELEASE_AUTOMATION.md`](./WEEKLY_RELEASE_AUTOMATION.md) and [`RELEASE.md`](./RELEASE.md). This daily automation is optional **PR triage only**; it does not cut tags.
2
4
3
5
Cursor Automations cannot be created via MCP/API from a Cloud Agent — create this once in the UI.
Product release notes live under [`docs/releases/`](../releases/). Build locally with `./scripts/release/build-artifacts.sh v1.0.0` (output: `release-artifacts/v1.0.0/`).
15
+
Product release notes live under [`docs/releases/`](../releases/). Build locally with `./scripts/release/build-artifacts.sh v1.1.0` (output: `release-artifacts/v1.1.0/`).
15
16
16
17
Other Cloud Agents: read these paths from the repo (this branch or after merge to `main`).
Tag the **product** version (`v1.0.0`). Keep backend `pom.xml` in lockstep with the tag for the JAR filename. MCP may continue its own semver when publishing `@deepsql/mcp` to npm.
27
+
Tag the **product** version (`v1.1.0`). Keep backend `pom.xml` in lockstep with the tag for the JAR filename. MCP may continue its own semver when publishing `@deepsql/mcp` to npm.
28
+
29
+
Default bump for a weekly cut: **MINOR** when user-visible features landed since the last tag; **PATCH** for fixes/docs only; **MAJOR** only for breaking install/API changes.
15
30
16
31
## Pre-flight (release manager)
17
32
@@ -27,20 +42,20 @@ Tag the **product** version (`v1.0.0`). Keep backend `pom.xml` in lockstep with
America/Los_Angeles observes PST/PDT; “9 AM PST” in planning means **09:00 Pacific** (this cron).
12
+
13
+
Related (optional): daily PR triage remains in [`DAILY_RELEASE_AUTOMATION.md`](./DAILY_RELEASE_AUTOMATION.md). The Saturday run owns **cutting the release**.
14
+
15
+
## Create
16
+
17
+
1. Open https://cursor.com/automations/new (or Agents Window → Create automation).
4.**Repository:** DeepSQLAI/deepsql (required — scheduled automations default to no repo).
21
+
5.**Tools:** enable repo git tools, **Comment on Pull Request**, and whatever is needed to open PRs / push tags in your plan. Prefer the Cloud Agent path that can push to the repo.
22
+
6. Paste the prompt below.
23
+
7. Activate; run once manually the first Saturday (or trigger manually) to verify.
24
+
25
+
## Identity note
26
+
27
+
Built-in GitHub comments from automations post as the **`cursor`** GitHub app identity. Write release notes and PR text as a human release manager — never say “bot / automation / Cursor” in GitHub comment bodies.
28
+
29
+
## Prompt (paste as-is)
30
+
31
+
```text
32
+
You are the release manager for DeepSQL OSS (DeepSQLAI/deepsql). This is the WEEKLY release run (Saturday 09:00 America/Los_Angeles).
33
+
34
+
## Goal
35
+
Cut the next product GitHub Release from `main` if there is anything to ship since the latest `v*.*.*` tag. Follow docs/oss-ux/RELEASE.md.
36
+
37
+
## Scope
38
+
- Work only in this repository.
39
+
- Durable process docs: docs/oss-ux/RELEASE.md, docs/oss-ux/WEEKLY_RELEASE_AUTOMATION.md, docs/oss-ux/OSS_SECURITY_REVIEW.md.
40
+
41
+
## Steps
42
+
1. `git fetch --tags origin` and identify the latest product tag (vMAJOR.MINOR.PATCH) and `origin/main` tip.
43
+
2. If `main` has no commits since that tag: stop. Comment nothing on GitHub; summarize “no release this week” in the run summary.
44
+
3. If `main` CI is red on the tip commit: stop. Leave a short release-manager note on the most relevant open PR or as a run summary listing the failing checks. Do not tag.
45
+
4. Decide the next version:
46
+
- PATCH if only fixes/docs/chores
47
+
- MINOR if user-visible features landed (default when unsure and features exist)
48
+
- MAJOR only for breaking install/API changes called out explicitly
49
+
5. Create a short-lived branch `cursor/weekly-release-vX.Y.Z-…` from `origin/main`:
50
+
- Bump `backend/pom.xml` project `<version>` to X.Y.Z (must match the tag for the JAR name).
51
+
- Append CHANGELOG.md Keep-a-Changelog section for [X.Y.Z].
- Update the Versioning table in docs/oss-ux/RELEASE.md “Current” column.
54
+
6. Pre-flight on a running stack when available (docs/oss-ux/RELEASE.md): login, e2e-agent-check.py → AGENT_OK + DASH_OK, quick security smoke. If the stack cannot be brought up, say so and still prepare the docs/version PR but do not push the tag until smoke is green.
55
+
7. Open a PR into `main`, get CI green, merge (or ask @venkateshsakamuri-lab to merge if you lack rights).
56
+
8. On the merged `main` commit: annotated tag `vX.Y.Z` and `git push origin vX.Y.Z`. Tag push runs `.github/workflows/release.yml` which builds artifacts and creates the GitHub Release.
57
+
9. Confirm the Release page exists and assets uploaded. If Actions fails, fall back to `./scripts/release/build-artifacts.sh vX.Y.Z` + `gh release create` per RELEASE.md.
58
+
10. Optionally triage leftover open PRs (same standards as the daily triage prompt) after the release is published.
59
+
60
+
## Versioning reminders
61
+
- Product tag and backend pom stay in lockstep.
62
+
- MCP npm (`mcp/package.json`) has its own semver — only bump/publish when MCP/CLI changed.
63
+
- Do not put release artifacts under Vite `dist/`.
64
+
65
+
## Comment style
66
+
- Write as a normal release manager. Never mention bot / AI / Cursor / automation in GitHub text.
67
+
- One clear summary when useful (version, commit range, Release URL).
68
+
69
+
## Output (run summary)
70
+
- Previous tag → new tag (or “skipped: no changes / CI red”)
**Weekly product cut** — dashboards, multi-schema UX, and Performance consolidation on top of `v1.0.0`.
4
+
5
+
## Highlights
6
+
7
+
-**Progressive dashboards** — builds stream a shell, then widgets; clone, folders/favorites, version history, refresh/TV kiosk, and AI-evaluated alerts.
8
+
-**Server-owned dashboard chat** — generation turns persist even if the SSE client disconnects; concurrent turns are rejected safely.
9
+
-**Multi-schema UI** — Editor, Brain, and Advisor surfaces treat non-`public` Postgres schemas as first-class.
10
+
-**Performance hub** — Slow Queries and Workload Analysis live in one Performance area.
11
+
-**CI unblock** — CodeQL visibility guard that blocked merges is removed.
# set SECURITY_JWT_SECRET, ENCRYPTION_KEY (or ENCRYPTION_KEYS), and DEEPSQL_CHAT_* in .env
21
+
docker compose up --build -d
22
+
```
23
+
24
+
From `v1.0.0`: pull/checkout `v1.1.0`, rebuild Compose (or swap JAR + frontend tarball from this Release), and apply hand SQL for dashboard tables if you are not relying on `ddl-auto=update`:
25
+
26
+
-`V111` / `V112` — `generation_status`, optimistic `version` on `saved_dashboards`
0 commit comments