Skip to content

Conversation

@sftse
Copy link
Contributor

@sftse sftse commented Dec 17, 2025

Work on refactoring the globals in tauri-cli. I think this is beneficial as-is, but it is not quite finished.

This still is missing a full transition towards lazy initialized tauri_dir and frontend_dir while guaranteeing not to break anything, as discussed in this comment.
Completed.

Read commit-by-commit.

@sftse sftse requested a review from a team as a code owner December 17, 2025 15:31
@github-project-automation github-project-automation bot moved this to 📬Proposal in Roadmap Dec 17, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 17, 2025

Package Changes Through ee5d876

There are 4 changes which include tauri-utils with patch, tauri-build with patch, tauri-cli with patch, tauri with patch

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package current next
tauri-utils 2.8.1 2.8.2
tauri-bundler 2.7.5 2.7.6
tauri-runtime 2.9.2 2.9.3
tauri-runtime-wry 2.9.3 2.9.4
tauri-codegen 2.5.2 2.5.3
tauri-macros 2.5.2 2.5.3
tauri-plugin 2.5.2 2.5.3
tauri-build 2.5.3 2.5.4
tauri 2.9.5 2.9.6
@tauri-apps/cli 2.9.6 2.9.7
tauri-cli 2.9.6 2.9.7

Add another change file through the GitHub UI by following this link.


Read about change files or the docs at github.com/jbolda/covector

@sftse
Copy link
Contributor Author

sftse commented Dec 18, 2025

Any chance to run CI automatically on my PRs? Would make iteration much faster, I often miss things built only on other platforms.

@FabianLars
Copy link
Member

Any chance to run CI automatically on my PRs? Would make iteration much faster, I often miss things built only on other platforms.

That decision will probably take longer to discuss than your pr will be open x)

@sftse sftse force-pushed the less-statics branch 2 times, most recently from ee5a7b4 to a1b4415 Compare December 19, 2025 22:19
@sftse
Copy link
Contributor Author

sftse commented Dec 19, 2025

This is RFR

@sftse
Copy link
Contributor Author

sftse commented Dec 21, 2025

@FabianLars
I put effort into readable commits that compile individually. High-latency round trips reduce the quality of my contributions, here the last commits merge multiple unrelated things because it takes way too long to figure out what is related.

RFR

@sftse
Copy link
Contributor Author

sftse commented Dec 21, 2025

Fixed next errors

@FabianLars
Copy link
Member

I put effort into readable commits that compile individually. High-latency round trips reduce the quality of my contributions, here the last commits merge multiple unrelated things because it takes way too long to figure out what is related.

Yeah i totally get that. GitHub only offers us 2 options: Auto run workflows for everyone or only for those with write permissions. There's no way to give individuals workflow permissions without also giving write access to the repo. All in all very annoying.

You could however enable workflow runs in your own fork (free of charge since it's open source) and open a second PR from your branch against your own fork's dev branch.

@sftse
Copy link
Contributor Author

sftse commented Dec 22, 2025

You could however enable workflow runs in your own fork (free of charge since it's open source) and open a second PR from your branch against your own fork's dev branch.

Didn't think of that, I'm not familiar with the workflows.
I might take that for a spin, thanks.

@FabianLars
Copy link
Member

whoops sorry, didn't mean to click on button...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 📬Proposal

Development

Successfully merging this pull request may close these issues.

2 participants