Merge latest Tusky develop into Dusky and handle collection notifications #1
Loading…
Reference in a new issue
No description provided.
Delete branch "merge/tusky-develop-2026-10-02"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Merge 90 upstream commits through tusky/Tusky develop at
70d318a41(2026-09-30). Use upstream behavior for shared features and retain Dusky's branding, defaults, Markdown/HTML posting and quote composition, which are still absent upstream.Resolve the instance metadata and translation conflicts and advance the database to version 93 using Room auto-migrations.
Make Mastodon collection notifications tolerant of valid collection payloads: accept rejected/revoked item states and nullable remote descriptions. Keep referenced collections during database cleanup. Set the app version to 33.0-beta1-dusky2 (146), which can update the diagnostic build (145).
Validation: app:assembleBlueRelease completed successfully, Android release lint reported no new errors, and the release APK was signed with the supplied Dusky key and certificate and verified with apksigner. No additional tests were added. Actual delivery of a collection notification on a device remains to be verified.
Merge latest Tusky develop into Duskyto Merge latest Tusky develop into Dusky and handle collection notificationsView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.