Repository navigation
Conversation
This was referenced Sep 29, 2026
Author
|
Thanks |
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.
Prepares a 1.1.0 release, following the convention of the previous ones: one
commit for the soversion, one commit for NEWS. Relates to #9.
Why now
The last release, 1.0.5, is from 2025-06-04. Since then the library gained
the tags for the newest devices, and
AUTH_VERSIONchanged. A signing clientthat reports an old version to the server is fragile, because the server side
can change without a matching change here.
libimobiledevice/idevicerestore#805 proposes a 2.0.0 release of
idevicerestore, which needs the tags in this library to request tickets forcurrent devices.
Version number
1.1.0, not the 1.0.6 mentioned in #9. That number predates a comparison of
the public headers. The interface gains two functions:
New functions with nothing removed is a minor release, not a patch release.
Soversion
0:3:0becomes1:0:1, which is the+1 : 0 : +1case in the comment abovethe value: "adds new functions to the interface".
CURRENT minus AGE stays 0, so the library major does not move and programs
linked against 1.0.5 keep working. A local build confirms it, since the file
is still named
libtatsu.0.dylib.Verification
./autogen.sh && makepasses on macOS 27.0 on arm64.Remaining step
The version comes from
git describethroughgit-version-gen, so this PRcannot set it. The tag
1.1.0still has to be created by a maintainer.