* fix error file name 'tauri.conf.js' to 'tauri.conf.json'
* fix(tauri.js) if the DOM is already loaded, listen for <a> clicks (#436)
code is fine, the CI is borked
* fix(open) open <a> on browser only if target=_blank (#437)
merging because CI is borked
* fix(tauri): make github action envs absolute for extra path level in runner.rs (#438)
* fix(tauri): extra path level in runner.rs
This file is one folder deeper than the other files which reference this env. This env is a relative folder reference so we need to concat an extra folder traversal into it.
* Revert "fix(tauri): extra path level in runner.rs"
This reverts commit eb1034b4f3.
* make envs in GH Actions absolute for now
* runner is only available within steps
* feat(bundler) add exception_domain option by nothingismagick (#439)
* chore(deps) Update Tauri JS CLI (#421)
Co-authored-by: WhiteSource Renovate <renovatebot@gmail.com>
Co-authored-by: Lucas Fernandes Nogueira <lucas@tauri.studio>
Co-authored-by: Jacob Bolda <me@jacobbolda.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: WhiteSource Renovate <renovatebot@gmail.com>
Co-authored-by: nothingismagick <denjell@sfosc.org>
* feat(bunder) bootstrapps zshrc and bashrc too
* feat(bundle) add bootstrapper to deb
* fix(linux): find linux path in bootstrapper
Co-authored-by: nothingismagick <drthompsonsmagickindustries@gmail.com>
* fix(tauri): extra path level in runner.rs
This file is one folder deeper than the other files which reference this env. This env is a relative folder reference so we need to concat an extra folder traversal into it.
* Revert "fix(tauri): extra path level in runner.rs"
This reverts commit eb1034b4f3.
* make envs in GH Actions absolute for now
* runner is only available within steps
* Migrating examples to the example repo
* update smoke test github action to example repo
* unclear what the path should be
* lock file moved
* remove ls
* x64?
darn conflicts
* missed cache path
* cargo build step isn't needed
Co-authored-by: Jacob Bolda <me@jacobbolda.com>
We were missing the envs so tauri-core didn't publish. It is fine if every package has these envs. We shouldn't need to verify as we have already built many times prior, and the verification gets very odd with packages all being bumped and being interdependent (inception verification).
Co-authored-by: Jacob Bolda <me@jacobbolda.com>
We were missing the envs so tauri-core didn't publish. It is fine if every package has these envs. We shouldn't need to verify as we have already built many times prior, and the verification gets very odd with packages all being bumped and being interdependent (inception verification).
* yarn before pack
* login to cargo to publish
* skip install on same version
* workflow edits trigger too
* and this one too
Co-authored-by: Jacob Bolda <me@jacobbolda.com>
* Update and rename cargo-publish.yml to release-cargo.yml
* Update and rename npm-publish.yml to release-npm.yml
* Delete push-to-dev.yml
* Create pr-to-master.yml
* add newer packages to matrix
* check cargo published version
* skip cargo audit if versions match
* chore(release-cargo) tauri-cli renamed to tauri-bundler
Co-authored-by: Lucas Fernandes Nogueira <lucasfernandesnog@gmail.com>
* feat(tauri&tauri.js) allow inliner/loadAsset to be used with publicPath
* fix minor error
Co-authored-by: Tensor-Programming <abeltensor@tensor-programming.com>
