Skip to content

chore: sync develop with main after squash releases#82

Merged
Jaro-c merged 1 commit into
developfrom
main
Jun 5, 2026
Merged

chore: sync develop with main after squash releases#82
Jaro-c merged 1 commit into
developfrom
main

Conversation

@Jaro-c

@Jaro-c Jaro-c commented Jun 5, 2026

Copy link
Copy Markdown
Member

One-time synchronization. Past squash merges left develop and main with diverging history (already-released commits kept reappearing in release PRs). Merging main back into develop reconciles both histories.

From now on the merge policy avoids this entirely: task branches rebase-merge into develop, and develop merges into main with a merge commit.

Promotes to `main`:
- Agent and compose translator extraction (#75) + follow-up issue #76
- Community health files aligned with org-wide defaults (#77, #79)
- Tooling-only gitignore (#78)
- `docs/security-architecture.md`, README Development section, fixed
installer URL
@Jaro-c Jaro-c merged commit 37be073 into develop Jun 5, 2026
8 checks passed
@Jaro-c Jaro-c added effort:XS Less than an hour type:chore Maintenance task, no production code change labels Jun 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

effort:XS Less than an hour type:chore Maintenance task, no production code change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant