Skip to content

Release 1.1.0 - #10

Closed
bestouff wants to merge 2 commits into
libimobiledevice:masterfrom
bestouff:release-1.1.0
Closed

bestouff wants to merge 2 commits into
libimobiledevice:masterfrom
bestouff:release-1.1.0

Conversation

@bestouff

@bestouff bestouff commented Sep 29, 2026 •

Copy link
Copy Markdown

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_VERSION changed. A signing client
that 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 for
current 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:

tss_request_add_bora_tags()
tss_request_add_durant_tags()

New functions with nothing removed is a minor release, not a patch release.

Soversion

0:3:0 becomes 1:0:1, which is the +1 : 0 : +1 case in the comment above
the 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 && make passes on macOS 27.0 on arm64.

Remaining step

The version comes from git describe through git-version-gen, so this PR
cannot set it. The tag 1.1.0 still has to be created by a maintainer.

@bestouff

bestouff commented Nov 5, 2026

Copy link
Copy Markdown
Author

Thanks

@bestouff
bestouff deleted the release-1.1.0 branch November 5, 2026 07:32
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