Repository navigation
Release proxy 0.4.2 and Syncables 0.27.0 - #726
Merged
Merged
Conversation
Claude-Session: codex://threads/01a1b0eb-3184-735e-8126-92bb9409f07b Codex-Session: codex://threads/01a1b0eb-3184-735e-8126-92bb9409f07b
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.
Publish the merged SyncD/IAP management and notification work from #725 as installable packages. Bump the proxy manifest and lockfile to 0.4.2, and Syncables to 0.27.0; assemble the pending Syncables changelog fragments using its release script.
Validation: release diff reviewed; git diff --check, Syncables formatting and changelog validation passed. CI will validate the exact release commit before merge. Proxy publication follows the tag workflow after main passes; Syncables publishes automatically on merge.
The localthought.io wrapper will then use the published proxy. atomic-saas #159 will receive the same dependency update and remain unmerged.