Skip to content

Sync main → develop after v1.4.2 release#170

Merged
saadqbal merged 1 commit into
developfrom
sync/main-to-develop-post-v1.4.2
Jun 1, 2026
Merged

Sync main → develop after v1.4.2 release#170
saadqbal merged 1 commit into
developfrom
sync/main-to-develop-post-v1.4.2

Conversation

@saadqbal
Copy link
Copy Markdown
Contributor

@saadqbal saadqbal commented Jun 1, 2026

Summary

Routine post-release sync. Brings main back to develop after v1.4.2 (#169).

What's in the diff

That's it. Develop already had #167's content; this just brings the squash-merge of the sync PR to develop so git log origin/main..origin/develop is empty going forward.

After merge

Develop and main both at the v1.4.2 baseline. Ready for the next development cycle.

🤖 Generated with Claude Code


Note

Low Risk
No code or configuration changes—only a merge commit to align branch pointers.

Overview
No file changes in this PR—the diff is empty.

This is a routine post-release branch sync: merging main into develop after v1.4.2 so both branches share the same release baseline and develop is ready for the next cycle. The merge commit records the squash-merge of the prior release sync PR; develop already contained the feature work from that release.

Reviewed by Cursor Bugbot for commit ba82ef6. Bugbot is set up for automated code reviews on this repo. Configure here.

…oxy (#169)

fix(#166, #168): installer survives corporate proxy + sanitizes credential input
@saadqbal saadqbal self-assigned this Jun 1, 2026
@LukasWodka
Copy link
Copy Markdown
Contributor

👋 Heads-up — Code review queue is at 14 / 8

Above the WIP limit. The team convention is to review existing PRs before opening new work.

Open PRs currently in Code review (oldest first):

Pull from review before opening new work. (This is a nudge from the kanban WIP check, not a block.)

@saadqbal saadqbal merged commit 0f0c0e2 into develop Jun 1, 2026
21 checks passed
@saadqbal saadqbal deleted the sync/main-to-develop-post-v1.4.2 branch June 1, 2026 10:17
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.

3 participants