Stack Wallet

This commit simply corrects an error message text. When a part of the app called ShopInBitService is used before being set up, the thrown error now tells the user to call ensureInitialized() instead of the outdated init(). There is no security change.

This commit is a routine user-interface refactor. It replaces a one-shot list of gift-card vendors with an 'infinite scroll' list that loads more cards as the user scrolls, and updates the backend client to return paginated results. There is no security-relevant change visible in the diff.

This commit cleans up a merge conflict in the Stack Wallet app. It adds a new optional database column to store the raw order status text from a third-party shopping service (ShopInBit), updates the generated database code, and fixes a small logic bug where an order status could be set to null. There is no obvious security vulnerability here; it looks like a routine data-model and bug-fix cleanup after merging two branches.

This commit is a routine user-interface refactor for a third-party shopping feature called ShopinBit. It replaces some desktop-specific popup dialog code with a shared navigation system, tweaks button layouts, and fixes styling. There is no clear security bug being patched, and no sensitive data handling or cryptographic code is changed.

This commit changes a single user-interface label in a travel booking form. The dropdown that previously showed the placeholder text 'Month or season' now shows just 'Month'. There is no security relevance: it is purely a wording correction.

This commit replaces two separate date text fields in a travel booking form with a single built-in date-range picker widget. It is a routine user-interface cleanup with no apparent security relevance.

This commit is a routine user-interface cleanup: it moves the date-range picker code out of the transaction-search screen and into a reusable widget file. There is no security-relevant change visible in the diff.

This commit is a routine user-interface feature update. It extends the app's custom date picker so it can optionally return a date range instead of a single date, and updates the existing call sites to keep using only the first selected date. There is no security-relevant change visible in the diff.

This commit is a routine user-interface styling fix. It swaps the standard Flutter date picker for a custom Stack Wallet date picker in a travel booking form and makes the custom picker accept optional start/end date limits. There is no security-relevant change visible in the code.

This commit only adjusts vertical spacing (padding) between checkboxes and buttons on mobile screens in three shopping/concierge forms. It is a cosmetic UI tweak with no security relevance.

This commit fixes a user-interface annoyance in Stack Wallet. Previously, closing certain pop-up dialogs would show an unnecessary 'are you sure you want to close?' warning even when no important progress was at risk. The change makes the warning appear only when appropriate, such as when the user is in the middle of a multi-step flow, and skips it on the very first step or when the navigation stack is empty. There is no direct evidence this is a security fix.

This commit only adds new build and packaging automation. It creates GitHub Actions jobs to produce AppImage, Flatpak, Android, Windows, macOS, and iOS builds for the Campfire and Stack Duo wallet variants, plus small launcher scripts and desktop metadata files. There is no change to wallet logic, cryptography, networking, or user data handling.

This commit is a user-interface cleanup. It moves the 'Are you sure you want to close?' confirmation logic into a shared dialog widget and lets different screens choose whether to show a warning, a generic message, or no warning at all. There is no indication this fixes a security vulnerability; it appears to be a normal feature/refactoring change.

This commit is a routine user-interface cleanup for the ShopinBit checkout flow. It swaps one dialog widget for another, adjusts spacing and padding, replaces a Material icon with an SVG icon, removes an unused internal warning dialog, and tweaks dropdown positioning. There is no indication of any security fix or behavior change that would affect user safety.

This commit adds a new automated build step that produces a Flatpak installer for Linux. It does not change the wallet's code, cryptographic handling, or permissions beyond what a normal Linux desktop app needs. There is no indication this is a security fix or introduces a vulnerability.

This commit changes the Flatpak packaging for Stack Wallet so the app can read and write files in a folder named .stackwallet inside the user's home directory. Flatpak apps normally run in a sandbox with limited access to the rest of the system. The change gives the app access to one specific, named folder, which is a common and usually reasonable way for a wallet app to store its data. By itself, this is not a vulnerability, but it slightly widens the sandbox. If the app were ever compromised, that folder could be read or modified by the attacker.

This commit adds a new automated build step that packages the existing Linux version of Stack Wallet as a Flatpak installer. It does not change the wallet's actual code, only the build/release pipeline and packaging metadata. There is no indication of a security fix or vulnerability.

This change updates the Flatpak packaging for Stack Wallet so the app can read and write files in the user's ~/.stackwallet folder. This is likely needed so the wallet can store its data outside the sandbox. By itself, granting access to a dedicated wallet directory is a routine, expected permission change and not a vulnerability. However, it slightly widens the app's sandbox escape surface because a bug or malicious component inside the app could now access, modify, or delete files in that folder, including wallet backups or configuration data.

This commit simply removes a small UI feature that showed the number of open support tickets on a 'My requests' button in the ShopInBit service area. The button still works and opens the requests page; it just no longer displays the count. There is no security relevance visible in the change.

This commit is a user-interface refactor for two third-party order/payment features (CakePay and ShopInBit). It moves order loading and polling out of the UI screens into dedicated background services, adds pull-to-refresh and refresh buttons, and removes full-screen loading spinners that previously blocked the app. There is no direct evidence in the commit that it fixes a security vulnerability; it appears aimed at improving responsiveness and fixing UI lock-ups.

This commit adds a confirmation dialog that asks users 'Are you sure you want to close?' when they click the X button partway through a ShopInBit or CakePay purchase flow. Previously, the X button could close the whole checkout window unexpectedly, which might cause a user to lose their place or abandon a payment. There is no sign of a security vulnerability being fixed; it is a usability improvement to prevent accidental closure.

This commit is a small user-experience improvement for the ShopinBit feature in Stack Wallet. It skips a screen that repeatedly asks the user for their display name when that name has already been saved. There is no security issue visible in the change.

This commit simply hides or shows two app features—ShopinBit and CakePay gift cards—based on configuration flags. It is a normal UI customization change, not a security fix or vulnerability.

This commit is a small UI fix for the ShopInBit ticket detail screen. It changes how timestamps received from the API are displayed to users, making the formatting consistent whether or not the API includes timezone information. It also adds the date (e.g., 'Jan 5') when a message is not from today. There is no security issue visible in this change.

This commit is a routine user-interface cleanup. It replaces several custom-built text input boxes in the ShopInBit shopping flow with a shared, reusable component called AdaptiveTextField, and removes an old, now-unused custom text field file. There is no indication this change fixes or introduces a security problem.