Skip to content

Tags

Tags

v0.3.2

Toggle v0.3.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore(release): 0.3.2 (#47)

The first release published to GitHub Packages rather than Maven Central (#46). Code-wise it adds
the inline iOS video fix (#43) on top of 0.3.1.

v0.3.1

Toggle v0.3.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore(release): 0.3.1 (#42)

The first release under Maven Central's 1,000-file monthly limit (#41): no .sha256/.sha512 checksums and no iosX64 target, about 852 files where 0.3.0 was 1,730. The code is 0.3.0's.

v0.3.0

Toggle v0.3.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore(release): 0.3.0 (#40)

* fix(ios): ask for the mobile page on iPads too

An iPad's WKWebView asks for the desktop site by default, so the same
workflow got a different page on an iPad than on an iPhone or Android.
Store searches written against the mobile pages never finished there,
and some desktop pages sat loading past the navigation timeout.

Both the pool's WebViews and VitreWebView now set the default content
mode to mobile, matching what Android's WebView always gets. A site that
serves iPads its wide layout regardless still does.

* chore(release): 0.3.0-rc.2

Carries the iPad fix from #38: iOS WebViews ask for the mobile page on an iPad too. Still an rc, since 0.3.0's desktop target has only been verified on macOS.

* chore(release): 0.3.0

0.3.0 proper, after 0.3.0-rc.2: the JetBrains Runtime JCEF desktop target from #36 and the iPad mobile-page fix from #38.

v0.3.0-rc.2

Toggle v0.3.0-rc.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore(release): 0.3.0-rc.2 (#39)

* fix(ios): ask for the mobile page on iPads too

An iPad's WKWebView asks for the desktop site by default, so the same
workflow got a different page on an iPad than on an iPhone or Android.
Store searches written against the mobile pages never finished there,
and some desktop pages sat loading past the navigation timeout.

Both the pool's WebViews and VitreWebView now set the default content
mode to mobile, matching what Android's WebView always gets. A site that
serves iPads its wide layout regardless still does.

* chore(release): 0.3.0-rc.2

Carries the iPad fix from #38: iOS WebViews ask for the mobile page on an iPad too. Still an rc, since 0.3.0's desktop target has only been verified on macOS.

v0.3.0-rc.1

Toggle v0.3.0-rc.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore(release): 0.3.0-rc.1 (#37)

Carries the KCEF → JetBrains Runtime JCEF migration from #36. A minor bump because the desktop API is source-breaking: KCEF's types leave the public surface and hosts start Chromium with CefRuntime.init on a JBR with JCEF. An rc first, as with 0.2.0, since the desktop target has only been verified on macOS.

v0.2.0

Toggle v0.2.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore(release): 0.2.0 (#34)

Promote `0.2.0-rc.2` to the final `0.2.0`. Also point the README's install
coordinates at `0.2.0`, which still advertised `0.1.2`.

v0.2.0-rc.2

Toggle v0.2.0-rc.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore(release): 0.2.0-rc.2 (#19)

Carries the network-interception fix from #18, which landed after
0.2.0-rc.1 was already published to Central.

v0.2.0-rc.1

Toggle v0.2.0-rc.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore(release): 0.2.0-rc.1 (#17)

Minor rather than patch: since 0.1.2 the public surface grew by the
WebView cookie jar (#6), taking a picture of the page (#10) and
branching a workflow with `If` / `runIf` (#13).

An rc rather than 0.2.0 so those additions can be resolved from Central
by a real consumer before the number the README recommends moves. The
release workflow flags any version carrying a prerelease component, so
the GitHub release will not display as Latest; Maven Central takes it
like any other version.

Also fixes the installation snippet, which named 0.1.0 — a version that
never reached Central, because that release failed before uploading
anything. Anyone copying the block got an unresolved dependency. It now
names 0.1.2, the latest version that is actually downloadable, rather
than this release candidate.

v0.1.2

Toggle v0.1.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix: publish without the configuration cache (#4)

0.1.1 got past signing and failed storing the configuration cache:
PublishToMavenRepository holds a repository spec Gradle has no serialiser for
(gradle/gradle#22779), and the publish plugin refuses a release under the
configuration cache regardless. `--no-configuration-cache` on the publish task
overrides org.gradle.configuration-cache=true for that one invocation and
leaves every other task in mise.toml on the cache.

Reproduced locally, and the same command dry-runs clean with the flag.

0.1.1 uploaded nothing before it failed, and cannot be retried under its own
number for the same reason 0.1.0 could not, so the retry goes out as 0.1.2.

Claude-Session: https://claude.ai/code/session_01AbVnaE46xJ5S26MuxAfHjz