* 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
