aboutsummaryrefslogtreecommitdiffstats
path: root/.github/workflows (unfollow)
Commit message (Collapse)Author
2024-06-12chore(build): compile protobufs with protox (#2122)Remo Senekowitsch
* chore(build): compile protobufs with protox protox is a pure-rust implementation of the protobuf compiler. Therefore, it can be managed by cargo. This removes the implicit dependency on protoc being available in the environment for the build. * fix(build): replace copypasta in build script The paths passed to `compile` aren't actually used by the build. `skip_protoc_run` prevents that. That's why a clean build succeeds even with this mistake. However, the paths are passed to a `cargo:rerun-if-changed` directive. So this mistake would've caused a failed incremental build if the protobuf definitions were changed.
2024-06-10chore: add installer e2e tests (#2110)Ellie Huxtable
* chore: add installer e2e tests * only run if edited or main
2024-06-05chore: switch to cargo dist for releases (#2085)Ellie Huxtable
* chore: switch to cargo dist for releases From https://axo.dev cargo-dist handles building releases far better than we can, and do so for several large projects now. We will need to change our install script to use the cargo-dist installer. Historically, we have used the system package manager wherever possible. Once switched to the new installer, this will no longer be the case. If the user wishes to use their package manager, and Atuin is maintained there, then they can choose to do so. This way, we can ensure that users are running a known build, can easily uninstall (just delete the atuin dir), easily update, etc. Builds will use our lockfile, and can have their checksum verified. Later, I'd like to introduce build signing. As Axo are focused on release engineering, they will likely have resolved many more issues than we have - libc versions, etc. I'm not particularly happy with our response of "just use your package manager", as many users seem to have difficulty there. It's unclear what our installer has done, as this behaviour varies massively across systems. It's also unclear how some package maintainers may have patched things I'm hoping that some better release tooling will lead to more confidence in the process, and therefore more frequent releases. Uninstall clarity: #111, #372, #640, #1485, #1546, #2049, #1529 * config * add protobuf * test build * use native arm mac * lol * add toolchain * use 1.78, 2vcpu * nix flake update * 1.77
2024-06-03chore(ci): don't run "Update Nix Deps" CI on forks (#2070)Xavier Vello
2024-05-08feat: add background daemon (#2006)Ellie Huxtable
* init daemon crate * wip * minimal functioning daemon, needs cleanup for sure * better errors * add signal cleanup * logging * things * add sync worker * move daemon crate * 30s -> 5mins * make clippy happy * fix stuff maybe? * fmt * trim packages * rate limit fix * more protoc huh * this makes no sense, why linux why * can it install literally just curl * windows in ci is slow, and all the newer things will not work there. disable the daemon feature and it will build * add daemon feature * maybe this * ok wut where is protoc * try setting protoc * hm * try copying protoc * remove optional * add cross config * idk nix * does nix want this? * some random pkg I found does this * uh oh * hack, be gone! * update contributing
2024-04-24fix(ci): release workflow (#1978)Ellie Huxtable
2024-04-15chore(release): prepare for release v18.2.0 (#1950)Ellie Huxtable
* chore(release): prepare for release v18.2.0 * disable codespell for the changelog
2024-04-11feat(gui): add base structure (#1935)Ellie Huxtable
* initial * ui things * cargo * update, add history refresh button * history page a bit better, add initial dotfiles page * re-org layout * bye squigglies * add dotfiles ui, show aliases * add default shell detection * put stats in a little drawer, alias import changes * use new table for aliases, add alias deleting * support adding aliases * close drawer when added, no alias autocomplete * clippy, format * attempt to ensure gdk is installed ok * sudo * no linux things on mac ffs * I forgot we build for windows too... end of day * remove tauri backend from workspace
2024-04-05chore(ci): Add codespell support (config, workflow) and make it fix some ↵Yaroslav Halchenko
typos (#1916) * Add github action to codespell main on push and PRs * Add rudimentary codespell config * ignore crate, inbetween etc * [DATALAD RUNCMD] run codespell throughout fixing typo automagically but ignoring the failure due to ambigous typos === Do not change lines below === { "chain": [], "cmd": "codespell -w || :", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^ * [DATALAD RUNCMD] Do interactive fixing of leftover ambigous typos === Do not change lines below === { "chain": [], "cmd": "codespell -w -i 3 -C 2", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^
2024-03-10chore(ci): setup nextest (#1848)Ellie Huxtable
2024-03-06chore(ci): add cross-compile job for illumos (#1830)Rain
I also tried getting FreeBSD to work, but didn't get too far sadly. I don't have the time to debug this so I just put in a comment for now. (With my changes, Atuin works great on FreeBSD as well.)
2024-02-29feat(nushell): add nushell completion generation (#1791)Remmy Cat Stock
2024-02-26feat(nix): add update action (#1779)Patrick Jackson
2024-02-05chore(ci): run rust build/test/check on 3 platforms (#1675)Ellie Huxtable
* chore(ci): run rust build/test/check on 3 platforms * need to properly test windows * do not need to strip here, and windows has a suffix anyway
2024-02-01chore(ci): re-enable test cache, add separate check step (#1663)Ellie Huxtable
2024-01-30chore(ci): use github m1 for release builds (#1658)Ellie Huxtable
2024-01-09fix: disable musl deb building (#1525)Ellie Huxtable
It never worked, and broke release building. I don't think we need musl debs, but if so ensure they don't break install scripts Resolve #1500
2023-10-26Fix cargo deb usage (#1337)Ellie Huxtable
v2.0.0 of cargo deb added the revision number. I'd rather not change the output name of our file, so force cargo-deb to stick to the "old" behaviour
2023-10-25Revert "Revert "Revert "Use github runners for unit tests (for now) (#1279)" ↵Ellie Huxtable
(#1294)" (#1295)" (#1325) This reverts commit 089cb6847c41b555b3a69ad1970f9449a77df491.
2023-10-19Checkout repo so the manifest publish step can read git (#1314)Ellie Huxtable
2023-10-19use the short sha to tag images (#1313)Ellie Huxtable
2023-10-19Use ubuntu for x86, oopsEllie Huxtable
2023-10-19Fix eventsEllie Huxtable
2023-10-19Switch to Actuated for docker builds (#1312)Ellie Huxtable
2023-10-08Revert "Revert "Use github runners for unit tests (for now) (#1279)" ↵Ellie Huxtable
(#1294)" (#1295) This reverts commit 10541134693ba710261832c309fae67036c6e892.
2023-10-08Revert "Use github runners for unit tests (for now) (#1279)" (#1294)Ellie Huxtable
This reverts commit 0abbcd6941fb27d9dd7ac3443c78c06607660d33.
2023-10-02Use github runners for unit tests (for now) (#1279)Ellie Huxtable
My self hosted runner is much faster, but my house was hit by lightning and the internet is down. I'm a few thousand miles away atm so won't be able to sort it for a while. Tests broken by _nature_.
2023-10-02Revert "Re-enable `linux/arm64` platform in CI docker build (#1276)" (#1278)Ellie Huxtable
This reverts commit ab8a48b2e01c33597b96bd05e66aa53413d1fe29.
2023-10-02Re-enable `linux/arm64` platform in CI docker build (#1276)rriski
This was previously enabled in #616 and then reverted in #730.
2023-08-14Run test build for client-only feature set (#1167)Tobias Genannt
2023-07-31Split integration and unit tests, use runner for unit (#1134)Ellie Huxtable
* Split integration and unit tests, use runner for unit * Probs does not need cache as network is slow
2023-07-30Add self hosted runner (#1133)Ellie Huxtable
2023-07-27some simple server tests (#1096)Conrad Ludgate
* some simple server tests * fmt * logging in server test * log server errors * fix postgres uri * postgres ports * localhost again? * Rebase fixes --------- Co-authored-by: Ellie Huxtable <ellie@elliehuxtable.com>
2023-06-13update release.yaml add RUSTFLAGS, add qemu-user, add QEMU_PREFIX before ↵mmx
gen-completions (#872)
2023-04-19Upload tar before building deb (#898)Ellie Huxtable
2023-04-18Allow specifying tag to build for workflow_dispatch (#896)Ellie Huxtable
2023-04-18Add package param to cargo deb (#895)Ellie Huxtable
2023-04-17Add workflow dispatch for release (#888)Ellie Huxtable
2023-04-16Fix release workflow (#885)Ellie Huxtable
2023-03-31feat: add github action to test the nix builds (#833)Patrick Jackson
2023-03-28Update CI action steps (#814)Marijan Smetko
2023-03-25Add musl build (#809)Marijan Smetko
Clean up Trigger with everything but release Remove trigger
2023-02-26Revert "Re-enable arm docker builds (#616)" (#730)Ellie Huxtable
Docker builds are failing on ARM, let's see if they work on AMD. Might be worth waiting until we have less C that needs building This reverts commit f3894ef9c0c9d2d9effa963b116d0075d4e7a9e5.
2023-02-26Enable RUST_BACKTRACE for docker builds (#729)Ellie Huxtable
They're failing on ARM atm, maybe this will help
2022-11-17Re-enable arm docker builds (#616)Patrick Jackson
2022-11-04Build ARM64 releases & update runners (#593)Lucy
Not entirely sure how to test this workflow. Why weren't ARM64 builds being made anyways? The workflow literally has cases to handle it! Fixes https://github.com/ellie/atuin/issues/369
2022-06-06Disable ARM docker builds (#438)Ellie Huxtable
These are failing and need investigating
2022-05-09Build ARM docker image in GitHub Actions using QEMU (#400)Daniel
This PR updates the GH Action docker workflow to crossbuild the docker image for ARM using QEMU. This theoratically works but takes about for a clean build 2.5 hours, which may or may not be tolerable for each commit on `main`. A action run where the dependencies are already cached needs about 15 minutes with this PR.
2022-04-23Use `--locked` flag for CI builds (#337)Orhun Parmaksız
2022-04-22feature-flags (#328)Conrad Ludgate
* use feature flags * fmt * fix features * update ci * fmt Co-authored-by: Ellie Huxtable <ellie@elliehuxtable.com>