chore: version bump 0.8.15 #1244
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fixes p2p stats display checking `null` store state
Description --- - upgrade `tauri` to V2 see their [migration guide for more info](https://tauri.app/start/migrate/from-tauri-1/): * moved auto update and systray logic to FE using tauri v2 plugins * updated imports and uses where needed - updated gh workflows: * separate workflow for beta builds * adjusted CI runs to suit V2 - split out our tauri_commands to their own file (`commands.rs`) to declutter `main.rs` Motivation and Context --- - we want notifications and cool V2 things! How Has This Been Tested? --- - locally What process can a PR reviewer use to test or verify this change? --- - run app - check it works the same as before (if not better 🤞🏼) Breaking Changes --- - yet to be seen --------- Co-authored-by: Misieq01 <[email protected]> Co-authored-by: Brian Pearce <[email protected]>
Description --- re-enable the license check Closes: #501
Description release notes
#1208 Description --- P2pool stats should be visible only after restarting the app, when toggled on [Screencast from 12-06-2024 12:00:40 PM.webm](https://github.com/user-attachments/assets/3114cb1c-aa58-47cc-88c3-0ac182acfcf5)
Description --- - **chore: bumped outdated deps** - **p2p UI:** - added 'Me' row - cleaned up redundant stats - made the height diff indicators clearer - fixed up scroll container How Has This Been Tested? --- - locally https://github.com/user-attachments/assets/761c5e38-49ea-4e44-8dde-be3cc1f93c4e <img width="1840" alt="Screenshot 2024-12-06 at 14 24 36" src="https://github.com/user-attachments/assets/ff8fd323-d8ac-42da-96e9-a06572d4915c"> <img width="1296" alt="Screenshot 2024-12-06 at 14 25 14" src="https://github.com/user-attachments/assets/8798feea-be88-489f-b916-edaebfc24ba8">
Currently, this sentry log is duplicated as a new sentry event for each instance. This is an attempt to group them together into a single log, but include the data
#1194 Description --- * use `outer_position` and `inner_size` to match the window settings identically
Bumps [tauri-apps/tauri-action](https://github.com/tauri-apps/tauri-action) from 0.5.15 to 0.5.16. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tauri-apps/tauri-action/releases">tauri-apps/tauri-action's releases</a>.</em></p> <blockquote> <h2>action v0.5.16</h2> <h2>[0.5.16]</h2> <ul> <li><a href="https://www.github.com/tauri-apps/tauri-action/commit/acdef251b8450d568e025c512753e61ef582fa8f"><code>acdef25</code></a> (<a href="https://redirect.github.com/tauri-apps/tauri-action/pull/949">#949</a> by <a href="https://www.github.com/tauri-apps/tauri-action/../../FabianLars"><code>@FabianLars</code></a>) The action will now set <code>TAURI_BUNDLER_DMG_IGNORE_CI: true</code> by default on tauri cli versions 2.2.0 and above. See <a href="https://redirect.github.com/tauri-apps/tauri-action/issues/740">tauri-apps/tauri-action#740</a> for context. This can be disabled by explicitly setting <code>TAURI_BUNDLER_DMG_IGNORE_CI: false</code> yourself.</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/tauri-apps/tauri-action/blob/dev/CHANGELOG.md">tauri-apps/tauri-action's changelog</a>.</em></p> <blockquote> <h2>[0.5.16]</h2> <ul> <li><a href="https://www.github.com/tauri-apps/tauri-action/commit/acdef251b8450d568e025c512753e61ef582fa8f"><code>acdef25</code></a> (<a href="https://redirect.github.com/tauri-apps/tauri-action/pull/949">#949</a> by <a href="https://www.github.com/tauri-apps/tauri-action/../../FabianLars"><code>@FabianLars</code></a>) The action will now set <code>TAURI_BUNDLER_DMG_IGNORE_CI: true</code> by default on tauri cli versions 2.2.0 and above. See <a href="https://redirect.github.com/tauri-apps/tauri-action/issues/740">tauri-apps/tauri-action#740</a> for context. This can be disabled by explicitly setting <code>TAURI_BUNDLER_DMG_IGNORE_CI: false</code> yourself.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tauri-apps/tauri-action/commit/ecd2eff64572601ddde25cc4962c2704435736e9"><code>ecd2eff</code></a> apply version updates (<a href="https://redirect.github.com/tauri-apps/tauri-action/issues/967">#967</a>)</li> <li><a href="https://github.com/tauri-apps/tauri-action/commit/344613d48c5053196cc7e8c26e0cc0789a190fcc"><code>344613d</code></a> chore(deps): update dependency eslint to v9.16.0 (<a href="https://redirect.github.com/tauri-apps/tauri-action/issues/968">#968</a>)</li> <li><a href="https://github.com/tauri-apps/tauri-action/commit/14666abb5117aaa6751a53df5c962329f1fbbdb9"><code>14666ab</code></a> chore: Re-build dist for <a href="https://redirect.github.com/tauri-apps/tauri-action/issues/949">#949</a></li> <li><a href="https://github.com/tauri-apps/tauri-action/commit/3ded1908b27019796a688256f3715ddf8df3f32c"><code>3ded190</code></a> chore(deps): update dependency <code>@types/node</code> to v22.10.1 (<a href="https://redirect.github.com/tauri-apps/tauri-action/issues/965">#965</a>)</li> <li><a href="https://github.com/tauri-apps/tauri-action/commit/cf7c431929d5115eb934788c3e4169e074e06c41"><code>cf7c431</code></a> chore(deps): update eslint monorepo to v9.16.0 (<a href="https://redirect.github.com/tauri-apps/tauri-action/issues/966">#966</a>)</li> <li><a href="https://github.com/tauri-apps/tauri-action/commit/acdef251b8450d568e025c512753e61ef582fa8f"><code>acdef25</code></a> fix: Set TAURI_BUNDLER_DMG_IGNORE_CI to true for <code>tauri build</code>, fixes <a href="https://redirect.github.com/tauri-apps/tauri-action/issues/740">#740</a> (#...</li> <li><a href="https://github.com/tauri-apps/tauri-action/commit/749ca9cf8d13525bb39eb7457578769e21582fc3"><code>749ca9c</code></a> chore(deps): update dependency prettier to v3.4.1 (<a href="https://redirect.github.com/tauri-apps/tauri-action/issues/962">#962</a>)</li> <li><a href="https://github.com/tauri-apps/tauri-action/commit/12b826e492234abf18e61009a324b67baf52bf57"><code>12b826e</code></a> chore(deps): update dependency typescript to v5.7.2 (<a href="https://redirect.github.com/tauri-apps/tauri-action/issues/960">#960</a>)</li> <li><a href="https://github.com/tauri-apps/tauri-action/commit/2d016802775028b7c978a23e9e08cfdd85dd99ae"><code>2d01680</code></a> chore(deps): update dependency prettier to v3.4.0 (<a href="https://redirect.github.com/tauri-apps/tauri-action/issues/961">#961</a>)</li> <li><a href="https://github.com/tauri-apps/tauri-action/commit/0120761fadc38a77e9c0b67d418d5ce053ca1389"><code>0120761</code></a> chore(deps): update dependency <code>@types/node</code> to v22.10.0 (<a href="https://redirect.github.com/tauri-apps/tauri-action/issues/959">#959</a>)</li> <li>Additional commits viewable in <a href="https://github.com/tauri-apps/tauri-action/compare/v0.5.15...v0.5.16">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Description --- This is a one time cleaning of the log directory to tidy up. Sometimes users send the wrong log files, as the file structure has changed leaving remnants of old logs. This PR removes *all* logs, and then starts fresh. Motivation and Context --- Easier for users to send us relevant stuff.
Description --- `AutoUpdate error: Could not fetch a valid release JSON from the remote` is a recurring issue reported on Sentry. Unfortunately, I have limited information regarding the response itself. My assumption is that GitHub releases may occasionally restrict access for certain users. I decided to set an additional endpoint for `latest.json` from our CDN, which will be utilized only when the GitHub endpoint is inaccessible(a non-2XX status code is returned).
Description --- - added tooltip for steps to try if you've landed up on an orphan chain - adjusted dialog styling for the loader when importing a new wallet form seed words Motivation and Context --- resolves: - #1193 - #1189 How Has This Been Tested? --- - locally: https://github.com/user-attachments/assets/fbeee140-fda3-4467-8282-cf824d1e3514 https://github.com/user-attachments/assets/bc944f27-3ce2-4b36-a6e2-e016c36ed8df --- <img width="1256" alt="Screenshot 2024-12-09 at 14 21 08" src="https://github.com/user-attachments/assets/18df9fa8-3ace-4395-a3e0-5fa059bb24d1"> <img width="1212" alt="Screenshot 2024-12-09 at 14 32 45" src="https://github.com/user-attachments/assets/fd614ddc-e868-468a-b95c-441a6db1e3ac"> <img width="1256" alt="Screenshot 2024-12-09 at 14 32 49" src="https://github.com/user-attachments/assets/187e7a8b-efea-4efd-8418-1075975f269b">
Description --- This pull request introduces support pre-release versions, placed in settings. It also contains creating `UpdatesManager` on the backend side, which is kinda refactor of the previous updater implementation for Tauri V1. * Added `pre_release` field to `AppConfig`, placed in "General Settings" * Moved updater logic to the backend, created `UpdatesManager` to handle all related logic and provide straightforward commands. It gives us more control over the updates flow and far more space for debugging. * Updater Dialog UI is not changed, it's just "dumb" and react to the events from rust. User shouldn't see any significant change How it works --- * When the pre-release version is enabled, the application retrieves the latest versions from `alpha-latest.json`. Disabling this flag immediately updates the application to the non-pre-release version. * When the pre-release version is disabled, the application fetches the latest versions from `latest.json`. From the user's perspective, there should be no significant changes. Enabling this flag instantly updates the application to the pre-release version. Motivation and Context --- #518 - Since we upgraded Tauri to v2, we can now handle pre-release versions. We use [Tauri Dynamic Update Server](https://v2.tauri.app/plugin/updater/#dynamic-update-server) to achieve this. This required us to move updater logic to the backend. What process can a PR reviewer use to test or verify this change? --- Testable on development environment. Play with this by changing * `tauri-conf.json` version to set the "current" app version * `latest.json` version to set the latest non-pre-release version * `alpha.json` version to set the latest pre-release version Toggle "pre_release" flag in the settings to switch between these app versions, turn on/off the `auto_update flag` and see how it affects the app. You can also update the app via "Release Notes" section --------- Co-authored-by: brianp <[email protected]>
Description --- Onwards and upwards!
Description --- Onwards and upwards! --------- Co-authored-by: stringhandler <[email protected]> Co-authored-by: Misieq01 <[email protected]>
Description --- - fixes missing release artifacts after Tauri V2 merge: needed to change `createUpdaterArtifacts` to [`v1Compatible`](https://tauri.app/plugin/updater/#building) for the zips How Has This Been Tested? --- - beta build branch: macOs:  linux:  windows:  What process can a PR reviewer use to test or verify this change? --- - check artifacts in [the release workflow](https://github.com/tari-project/universe/actions/runs/12294412932)
Description --- This fixes an issue where the twitter login information was lost between v1 and v2 upgrades because of the URL schema change. Fixes: #1230 Motivation and Context --- Users on v0.8.11 reported twitter no longer logged in on windows, and re-logging in was not solving the issue. How Has This Been Tested? --- It hasn't been tested yet. --------- Co-authored-by: Shannon Tenner <[email protected]>
Description --- - cleaned up animation timeouts (couldn't repro the original issue but there was an issue of the animaions not actually going away which was reporoducable every time) - cleaned up the `useAirdropUserPointsListener` listener and how the zustand store was updated there: - biggest one being the check against the count from the payload vs the store - made sure to only update the store after - added triggers for the animations for very BASIC testing in the admin ui (not that helpful since it's not directly related to the points) Motivation and Context --- - resolves an issue picked up when checking #1238, but should also hopefully resolve that issue. couldn't reproduce but it's all related to the listener and the timeouts being weird 😬 How Has This Been Tested? --- - locally, pointing to airdrop dev BE and adding the referrals (and target for the extra animation!) manually to trigger the points listener: https://github.com/user-attachments/assets/db2b2049-d9f1-4398-a6f5-e1296430a56a What process can a PR reviewer use to test or verify this change? --- little bit tough if you don't have access to the BE (dev!) admin for testing, but you can also just make sure your local dev build is pointing to airdrop dev, then on a separate dev build use your referral code, and wait for the points to test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Onwards and upwards