* install webkit after we confirmed we will publish
this should speed up the publish sequence as we now only run one at a time
* new lines don't work, use empty echo
We were running into race conditions where one package depended on another being published. Limit to only allow one publish at a time, and sort based on dependencies to (hopefully) eliminate the race condition.
* test(tauri.js) add template test
* fix(lint) ignore prefer-optional-chain because babel-jest wont accept it
* feat(webpack) raw-loader test for windows
* fix(workflow) install tauri-bundler
* fix(EOF)
* chore(test) try with done cb
* fix(test) cwd scope
* fix(test) transform regex for windows
* fix(test) windows regex on jest transform
Co-authored-by: nothingismagick <denjell@sfosc.org>
* feat(tauri.js) add API endpoint proxy
* feat(tauri.js) always resolve/reject proxy promise
* chore(proxy) wait for onTauriInit to start direct proxy to window.tauri
* feat(tests) add project for initial e2e test
* chore(tauri) remove whitespaces on runner.rs
* chore(test): remove updater.rs
* feat(tests) move e2e test to tauri.js/test/jest
thanks to @laegel for the awesome work moving the test code to jest
* feat(tests) prepare build for modes tests
* fix(tests) properly run build tests
* feat(tests) add dev e2e test
* fix(tests) cleanup
* chore(tests) move e2e test from express to http.createServer
* chore(tauri.js) husky back to 4.0.10
* chore(tests) custom transformer to export with default
* chore(tests) use jest mapping instead of relative paths
* chore(tests) move dev e2e test to http.createServer
* chore(tests) move dev/build e2e test to tes.each instead of for loop
* chore(tauri.js) add comment to non-webpack-require.ts
* chore(tests) change test.each to it.each
* chore(tests) adjust it.each message signature
* fix(tests) adjust to properly run on initial build
* fix(tests) properly cleanup
* fix(tests) wait server.close to reject test
* fix(tests) wait server.close to resolve test
* fix(actions) install webkit2gtk-4.0 on test-tauri-js-cli
* fix(ci) install tauri-cli on test-tauri-js-cli
* fix(tauri.js) lint errors
Co-authored-by: Lucas Nogueira <lucas@quasar.dev>
Co-authored-by: nothingismagick <denjell@sfosc.org>
`tauri-bundler` is not in the main cargo workspace so the target directory is not in the top level. Update the publishPath to compensate.
Also removing a couple extraneous things that aren't needed either. We had an extra '/' and we don't need to bother showing the directory within the `cargo package` command.
* feature(workflows): Add ESLint check to workflow
* Use setup-node v1.x.x instead of v1.0.0
Co-Authored-By: Jacob Bolda <me@jacobbolda.com>
Co-authored-by: Jacob Bolda <me@jacobbolda.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).
* 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(workflows): first-timer message
Just a little "hey there". For PRs remind them to sign commits.
* add explanation about why signed commits
* enhance pr-message
using the advice from @nklayman
This will create a draft release with all of the changes since the last tag. We can use it for the "marketing" changes / changelog, where each package can then still get its own changelog file. The bulk of the configuration sits in the tauri-pps/.github repo.
* rename smoke tests
* split into prod and source runs
* rename test job names for clarity
* snake case gatsby site
* remove airtable api key
* add new examples
* add new examples to renovate
* add scripts to package.json
* finish off vanillajs example
* shift example and slim config
removed gatsby-source-airtable and gatsby-theme-recipes to make things more simple, less fragile and speed up the build
* update action to point at new location
* update links
* add test articles
* add theme
* slim config, move to homepage folder
* update renovate path, enable automerge on examples
* turn off rebases, but keep on for examples
* add cache ext
* shorten artifact name
* cache rust cargo home
see https://doc.rust-lang.org/cargo/guide/cargo-home.html#caching-the-cargo-home-in-ci
* star artifact, relative rust cache
* forgot to relative prod rust cache
* seriously need one step per cache dir?
* forgot to fix artifact name
* likely need different key for each cache
* globs don't yet work, hardcode for now
* add releaseFolder option
MacOS has deeper folder structure than the others
* missed closing quote
* fix ubuntu artifact path
* use cargo home for cache dir
* set cargo home env
* try relative path?
* scrap env, use matrix
* wish it wasn't so verbose
* tilde
* cache rust based on hashed cargo.lock
* add themed gatsby site as example and test target
* add specific example ignores to gitignore
* update api key reference
* theme needs the alpha version currently
* update and pin deps
* remove lock file, we want a fresh build to test every time
* add recipe theme for cheap way to add to ton of site pages
* add tauri as dev dep
* build gatsby as a smoke test
* cd on each step
* pass api key
* chore(package.json): update
* schedule renovate to tone down noisiness (#122)
Also, there is a running theory that Tuesday is a good day for upgrades.
* combine jobs and add step with conditional (#121)
* combine jobs and add step with conditional
* too many equals
* Update dependency fast-glob to v3.1.1 (#113)
* chore(yarn.lock): update
* chore(versions): bump tauri.js & tauri
* feat(gatsby): include tauri resources
* feat(build): tauri build works
* tauri prod and source scripts
* add build from source and artifact upload to action
* don't need to init, examples are already
* point to direct executable with matrix
* ignore WixTools from build
* config app name
* build and install source deps before build project on source
* odd things when tauri is defined in a script, remove
* set gatsby config to what is believed will be ~es5
* babel plugin is actually neeeded
* run subscripts with yarn
* lower timeout limit to 30 minutes, easy to swamp CI with this
* shorten job names
* install tauri-cli (rust)
* make API key optional (sort of hacky)
* install rust for prod for cargo command following
* artifact name cannot have / within it
* windows is running a tad slow
* chore(checkin): cargo.lock
* feat(upgrades): update and try to fix node tests
* fix(@iarna): replace with @tauri-apps
* chore(deps): upgrade sharp
* feat(env): add env var that works on mac
* feat(deps): upgrade, cleanup and update code
* fix(workflow): env vars
* chore(deps): upgrades
* fix(.gitignore)
It has been hanging on MacOS builds. Although we would want to fix this hang long term. This is a temporary way to deal with it and prevent future occurrences of swamping the CI. It would be surprising if jest tests ran longer than 15 minutes.
* chore(monorepo): cleanup
* fix(tauri-cli): build errors
* fix(tauri:build.rs): dont' panic if env missing
* fix(finalize): setup for crates
* npm publish on release
actual publish currently disabled
* cargo publish on release
actual publish currently disabled
* update PR tests for new folder structure
* doesn't like the period on job name?
* fail on cargo warnings
otherwise we would assume green arrow is all good
* green on warnings for now
* test lib on PR
* add build command
* ls to see where we are at
* ls after
* cd in one step
* less matrixes
* Rename test-lib-on-pr.yml to test-on-pr.yml
* pull out strategy
* Update test-on-pr.yml
* more spaces
* jobs don't like spaces
* test bindings
* build templates
* build tools
