Auto-release on version bump + clearer login error (v2.2.1) - #4
Merged
Conversation
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.ymlalso runs on pushes tomaster: it reads<InformationalVersion>from the csproj and, if nov<version>tag exists yet, builds + zips + publishes the GitHub Release automatically. Pushingmasterwithout a version change is a no-op. Manual tag pushes andworkflow_dispatchstill work. (This was authored in #3 but the merge only captured the build fix, somasternever got it.)2. Clearer login error
ApiClientno longer collapses every failure into "Invalid server response." A rejected login now reports the real reason:)."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.https://claude.ai/code/session_01FhKJ3kR6pgaR4N3sWSfbFX
Generated by Claude Code