Jacob Bolda

I believe we have addressed these issues. Let's reopen if we haven't!

This is an issue upstream in https://github.com/tauri-apps/tauri-toml. We should probably confirm that the fixes there have been addressed in the original https://github.com/iarna/iarna-toml and switch back to that if appropriate. (`tauri-toml`...

Considering if we can address this via #236.

Closed by #303 and published in #300.

@wusyong, within the Tauri ecosystem, we are currently using the `create-pull-request` action to commit and open the PR. It has guidelines regarding enabling signed commits. We have looked at pulling...

Ah! Thanks for this. I was just chatting with someone what the error was if it hadn't been published yet. The workflow I have been recommending is publishing a `0.0.0`...

(If you have the non-dodgy version, would be nice for future reference.) We are checking if it has been published and if it hasn't then run the publish for it....

> What if you published to a target and the "dry-run" target was the default? > > That way, when you ran publish in your CI script you might say...

It is possible that this is resolved and we haven't fully confirmed it.

@samuel-rufi, we currently don't have a great way to automate / semi-automate the release of packages separately. There are a lot of situations laced with nuance that make it difficult...