Skip to content

chore: sync dev after v0.7.0 (release notes + #1115 fix)#1321

Open
vybe wants to merge 2 commits into
devfrom
release/0.7.0
Open

chore: sync dev after v0.7.0 (release notes + #1115 fix)#1321
vybe wants to merge 2 commits into
devfrom
release/0.7.0

Conversation

@vybe

@vybe vybe commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Post-release reconciliation for tag v0.7.0. Brings the two things dev is missing onto it, conflict-free (this branch was cut from dev's tip):

After merge, dev's tree matches main's. Avoids the squash-divergence conflict a direct main→dev merge hits (see closed #1320).

🤖 Generated with Claude Code

Eugene Vyborov and others added 2 commits June 23, 2026 17:01
…gres-safe)

The #300 SQLAlchemy migration dropped the get_db_connection import from
db/schedules.py but left get_agent_schedules_summary (#1115) calling it,
so the /schedules/analytics-summary endpoint raised NameError at runtime.
Surfaced for the first time by the v0.7.0 release-PR full-suite run (dev
pushes only lint).

Port the method to get_engine() Core queries like its siblings, and
replace the SQLite-only bare-column-with-MAX last-run query with a
portable ROW_NUMBER() window so it works on PostgreSQL too.

Also refresh the test_login_rate_limit_split config stub, which went
stale when auth.py grew a PUBLIC_ACCESS_REQUESTS_ENABLED dependency
(trinity-enterprise#10) — 8 collection errors under HEAD.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

⚠️ Nightly unit-suite check skipped — merge conflict against dev.

Resolve by running git merge dev locally and pushing the result. The next nightly run will re-test once the conflict is gone.

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