Skip to content

Auto-release on version bump + clearer login error (v2.2.1) - #4

Merged
Kofysh merged 3 commits into
masterfrom
claude/gifted-einstein-h0enx4
Jun 14, 2026
Merged

Auto-release on version bump + clearer login error (v2.2.1)#4
Kofysh merged 3 commits into
masterfrom
claude/gifted-einstein-h0enx4

Conversation

@Kofysh

@Kofysh Kofysh commented Jun 14, 2026

Copy link
Copy Markdown
Owner

Summary

Lands the work that didn't make it into #3, plus a login UX fix, and bumps to v2.2.1.

1. Auto-release on version bump (for real this time)

release.yml also runs on pushes to master: it reads <InformationalVersion> from the csproj and, if no v<version> tag exists yet, builds + zips + publishes the GitHub Release automatically. Pushing master without a version change is a no-op. Manual tag pushes and workflow_dispatch still work. (This was authored in #3 but the merge only captured the build fix, so master never got it.)

2. Clearer login error

ApiClient no longer collapses every failure into "Invalid server response." A rejected login now reports the real reason:

  • HTTP 401"Login rejected — check username, password and realm, and enter the TOTP code if 2FA is enabled."
  • other codes → "Login rejected by the server (HTTP )."

3. Version → 2.2.1

Effect of merging

Merging this from the GitHub UI (a normal push to master) will trigger the auto-release and publish v2.2.1 automatically.

⚠️ Note: merging via the API/bot does not trigger workflows (GitHub anti-recursion), so if it's merged that way the release must be kicked manually (Actions → Release → Run workflow). A UI merge fires it automatically.

https://claude.ai/code/session_01FhKJ3kR6pgaR4N3sWSfbFX


Generated by Claude Code

claude added 3 commits June 14, 2026 07:01
Extend the Release workflow to also run on pushes to master. It reads
<InformationalVersion> from the csproj and, if no matching v<version> tag
exists yet, builds and publishes the GitHub Release automatically. Pushing
master without a version change is a no-op, so releases are never spammed.
Manual tag pushes and workflow_dispatch keep working as before.

https://claude.ai/code/session_01FhKJ3kR6pgaR4N3sWSfbFX
…sponse"

PostTicketAsync collapsed every non-2xx response (and a null body) into the
same vague "Invalid server response." message — so a rejected login (HTTP 401)
looked like a server/protocol problem. Capture the status code and report it:
401 -> "check username, password and realm, and enter the TOTP code if 2FA is
enabled", other codes -> "Login rejected by the server (HTTP <code>)".

https://claude.ai/code/session_01FhKJ3kR6pgaR4N3sWSfbFX
Carries the login error-message fix and (once on master) enables the
auto-release workflow to publish v2.2.1 automatically.

https://claude.ai/code/session_01FhKJ3kR6pgaR4N3sWSfbFX
@Kofysh
Kofysh merged commit e0f0382 into master Jun 14, 2026
1 check passed
@Kofysh
Kofysh deleted the claude/gifted-einstein-h0enx4 branch June 14, 2026 11:23
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.

2 participants