Research / compatibility data last verified
RELEASE HISTORY / ALL PUBLIC RECORDS
2.3 is newer than 2.2, but it is a prerelease. misaka26 1.6 is Latest and Unstable at the same time. This timeline keeps dates, labels, platforms and warnings together.
THE DIRECT ANSWER
For public MisakaX 2.x, GitHub still labels 2.2 as Latest; the later 2.3 is a macOS-only Pre-release. In the separate misaka26 repository, 1.6 is Latest but the owner title says Unstable. MisakaX 3.0 beta is an undated, paid, incomplete storefront test—not the next public GitHub tag.
READ THE LABELS
GitHub’s interface supplies release metadata; the owner-written title and notes supply risk and scope. Keep both layers visible.
The release currently selected as Latest. It need not have the newest publication date when a newer record is a prerelease.
GitHub’s channel marker for a release presented as non-production. MisakaX 2.3 carries it today.
Text written into every current misaka26 release title, including 1.6. It remains meaningful beside Latest.
The current owner warning on MisakaX 1.2 and misaka26 1.0–1.3. A file or hash does not cancel it.
22 SOURCE-LINKED RECORDS
All records remain in the page source. Filters help you inspect one product, warning or platform without hiding the release-page evidence.
misaka26 v1.6 - Unstable
The newest public misaka26 record. It adds a TrollPad warning and Japanese localization while retaining the Unstable label.
misaka26 v1.5 - Unstable
Fixed the “right value must be 1 or 3” error.
misaka26 v1.4 - Unstable
Fixed an Intel Mac crash.
misaka26 v1.3 - Unstable (DON’T USE)
Added TrollPad on Windows and Intel Mac plus PWM, SRD and M-chip game flags. The owner title now says not to use it.
misaka26 v1.2 - Unstable (DON’T USE)
An early misaka26 build whose current owner title explicitly says not to use it.
misaka26 v1.1 - Unstable (DON’T USE)
An early Apple-silicon Mac build whose current owner title explicitly says not to use it.
misaka26 v1.0 - Unstable (DON’T USE / HIGH RISK)
The first misaka26 record. Its current owner title says not to use it and calls it high risk.
misakaX 2.3
The newer public MisakaX record. Its notes claim iOS/iPadOS 18.1 beta 5 through 18.2 beta 2 and add Find My Friends for KH/A variants.
misakaX 2.2
The release GitHub currently labels Latest. It covers the broad stable 16.0–18.0 claim and Apple Intelligence on 18.1+, with a beta-3/beta-4 wording conflict in its own notes.
misakaX 2.1.1
Added Sleep Apnea and corrected the Camera Control tweak.
misakaX 2.1
Continued the iOS 18.0 RC-era branch with Camera Control, AOD vibrancy and Dynamic Island size options.
misakaX 2.0
Introduced the iOS 18.0 RC-era Camera Control, AOD vibrancy and Dynamic Island size notes.
misakaX 1.9
Added Intel Mac support, improved macOS speed and introduced a device/MobileGestalt match check.
misakaX 1.7
Added Developer Mode and Metal HUD options.
misakaX 1.6
Added a TrollStore installer, iPad apps and iOS 16 support, plus an option to turn flags off. The Mac app no longer required Python.
misakaX 1.5
Fixed the Old Photos UI behavior, improved the interface and corrected a Windows plist parsing problem.
misakaX 1.4
Added Apple Intelligence, landscape Face ID and an Old Photos UI option, with a Clock UI fix.
misakaX: macOS 1.3 & windows 1.0
An emergency macOS fix for duplicate _copy.plist output. The release deliberately used different Mac and Windows version numbers.
misakaX 1.2
Added macOS 11+, SOS Collision, Tap to Wake and iPad-like multitasking, but the current release body explicitly says not to use 1.2.
misakaX 1.1
Fixed the pip dependency path and added an alert.
misakaX 1.0
The first public MisakaX release record.
MisakaX 3.0 Beta
A separate creator storefront listing, described by the creator as an incomplete test version. It is not a GitHub 2.x or misaka26 release.
No record matches all four filters. Reset one filter or show all products.
ASSET ANOMALIES
These are not corrections or accusations. They are exact mismatches a user needs to see before choosing an asset.
The release page exists but currently attaches no application file. Do not fill the gap with a mirror.
Find record ↑The release combines macOS 1.3 with Windows 1.0. Platform and filename matter more than the tag alone.
Find record ↑The Windows asset filename still says v1.3 while the macOS asset says v1.4. Use the owner page and digest.
Find record ↑The live paid listing exposes two gated ZIPs but no reliable publication timestamp. It stays outside dated order.
Find record ↑THE FOUR ERAS
The dates explain sequence, not whether a release fits your build or whether development will continue.
Rapid public releases added features, platform fixes and device/input matching.
2.2 became Latest; later 2.3 opened a narrower macOS prerelease channel.
Seven records in four days, all owner-labelled Unstable; early versions now say DON’T USE.
A separate paid test listing whose visible record cannot be safely inserted into the GitHub chronology.
RELEASE QUESTIONS
Use the timeline to establish publication history. Use the build checker to decide what applies to your device.
There are three different answers because there are three channels. GitHub currently labels MisakaX 2.2 as Latest. MisakaX 2.3 was published later but is marked Pre-release. The separate misaka26 repository labels 1.6 as Latest while its release title still says Unstable. Choose the product and channel before comparing version numbers.
Yes by publication date: 2.3 was published November 9, 2024, after 2.2 on September 17, 2024. That does not make it the stable successor: GitHub marks 2.3 Pre-release and still shows 2.2 as Latest.
GitHub distinguishes a release’s date from its channel label. A prerelease can be newer without becoming Latest. The repository owner can also choose which eligible release carries Latest. Read both the date and badge.
No stable claim is made on its release record. GitHub marks 2.3 Pre-release, and the record currently provides only a macOS archive. Use it only when its narrow beta-build claim matches your exact device build and you accept prerelease risk.
misaka26 1.6, published November 19, 2025, is the newest public release record and currently carries GitHub’s Latest label. Its owner-written title also says Unstable, so Latest must not be read as Stable.
The owner release uses the Git tag 26.1.6 while its visible release title calls the application misaka26 v1.6. We use the title’s user-facing version in the timeline and preserve the exact owner tag in the source link.
The labels answer different questions. Latest identifies the repository’s current release selection; Unstable is the owner’s risk/channel description. Both are true and both should stay visible when choosing a file.
The public evidence establishes two separate owner repositories and release histories, with misaka26 published later. It does not include an owner lifecycle statement saying that one product formally replaced or ended the other, so we do not turn chronology into a replacement claim.
Not from the date alone. Older records are history, not automatic recommendations. First match the exact iOS or iPadOS build and platform in the compatibility checker, then return to the release record that owns the claim.
The current owner titles for misaka26 1.0 through 1.3 explicitly warn against use; 1.0 also says High Risk. Those warnings override the existence of a downloadable archive or checksum.
The public 2.0 release record exists, but it currently has no uploaded application asset. Do not substitute a mirror or a file labelled 2.0 from another account. Later 2.1 and 2.1.1 records contain their own official assets.
That owner release intentionally combines macOS 1.3 with Windows 1.0 assets. The tag number is not enough to choose the file; read the release name, platform and exact asset filename.
That is how the owner asset is currently named: the 1.4 record has a v1.4 macOS file and a Windows file whose name still says v1.3. We record the mismatch instead of silently correcting it. Confirm the release page and published digest before deciding.
There is no public GitHub release record for version 1.8 in the current MisakaX release list. The sequence moves from 1.7 to 1.9. A missing version number does not authorize a mirror or prove that no private build ever existed.
No. The current 3.0 beta record is a separate creator storefront listing on Patreon, not a release under the public MisakaX or misaka26 GitHub repositories.
The live creator listing does not expose a reliable publication date that we can use as a release timestamp. We therefore label it Undated instead of placing it into the dated GitHub sequence.
The live listing checked August 24, 2026 currently shows a $12 price and describes the product as an incomplete test version. Older wording on the page about a planned free release does not override the current purchase state.
We found no 2026 public GitHub release record in either owner repository as of August 24, 2026. The newest listed GitHub record is misaka26 1.6 from November 2025; the separate 3.0 beta listing has no reliable visible publication date.
Release dates alone cannot answer that. A quiet release feed is not proof of abandonment, and a live repository or storefront is not a maintenance promise. No current public roadmap or support-lifecycle statement was found, so maintenance status remains unknown.
No. This page records what was published, when, under which channel and with which assets. Compatibility is a separate decision based on the exact iOS or iPadOS build, device family, computer platform and release claim.
The current misaka26 release asset records expose owner-published SHA-256 digests. The current GitHub asset records for MisakaX 2.2 and 2.3 do not expose a digest. A checksum proves that a file matches a stated value; it does not cancel an Unstable or DON’T USE warning.
It proves provenance only when you reached the correct owner record. It does not guarantee safety, compatibility or a successful restore. Keep platform security enabled, verify a published digest when available and make a backup before any Apply action.
PRIMARY RELEASE RECORDS
Dates, labels and assets were rechecked August 24, 2026. We link to release pages rather than binary URLs so the surrounding warnings remain visible.