chore(release): v1.1.5 - #555
Merged
Merged
Conversation
Marks the CoinPay reconnect fix (#554): a worker whose link predated the wallet:read scope was told to connect an account they had already connected, and the invoice API now tells them to reconnect instead. Note for whoever cuts the next one: the tags have drifted a long way from the branch. v1.1.3 is 882 commits behind master, and package.json had already been moved to 1.1.4 by 1c4e430 without a tag ever being cut for it. So v1.1.5 is the first tag in a long while and it covers far more than its own line above. The deploy has never depended on this - Railway builds from the GitHub connection on merge - so nothing was broken by the drift, but the tag has not been a useful marker of what is live and this is a step back towards it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WxWrsbLuaSaZqQ7FFTrdVW
ThreatCrush Security Scan45 finding(s) HIGH/CRITICAL: 1 | MEDIUM: 8 | LOW: 36
Snippets are redacted; ThreatCrush never prints matched credential material. |
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.
Bumps
package.jsonto 1.1.5, marking the CoinPay reconnect fix (#554).A worker whose CoinPay link predated the
wallet:readscope was told to connect an account they had already connected — reported from the agenticjobs apply flow, where an agent tried to invoice $0.25 and got the same sentence twice. The invoice API now distinguishesnonefromneeds_reconnectand says reconnect, with steps that lead with reconnecting.Worth knowing: the tags have drifted
v1.1.3is 882 commits behindmasterpackage.jsonhad already been moved to1.1.4by1c4e430, and no tag was ever cut for itSo
v1.1.5will be the first tag in a long while, and it covers far more than the line above. Nothing was broken by this — Railway builds from the GitHub connection on merge, so the deploy has never depended on the tags — but the tag has not been a useful marker of what is live, and this is a step back towards one. Worth deciding separately whether you want tagging to be routine here or dropped honestly, rather than left half-done.Checks
Pre-commit hooks pass (lint + full Next build). #554 itself went in with all six checks green: build 2m41s, test 2m13s, credential scan, ThreatCrush and both Socket checks, on top of 2104 local tests across 219 files.
Merging this auto-deploys, since the Railway service is connected to this repo.
🤖 Generated with Claude Code