| Age | Commit message (Collapse) | Author |
|---|
|
Uses a personal action for simpler invocations of cargo/cross commands.
|
|
Try to update to the newest cross version after 0.2.2 had some bugs causing a rollback to 0.2.1 (see #755).
|
|
|
|
|
|
Trying out Github's new issue form for bug reports.
If it doesn't look good or go well I'll revert.
|
|
Fix missing target parameter for primary test targets (e.g. aarch64), and adjust integration tests to work with cross.
|
|
Locks CI to cross 0.2.1.
|
|
Locks cross in deployment builds to 0.2.1, as 0.2.2 seems to break some things for now.
|
|
|
|
|
|
action-rs' action seems to not be really maintained anymore and
throws some redundant warnings that kinda clog up outputs. As
such, I feel like moving to a more active action is probably worth it.
|
|
Bumps `checkout` calls to v3.
|
|
Unifies nightly and deployment workflows using a shared action yml file to avoid as much duplication. Also updates the download-artifact action to v3.
|
|
|
|
Deletes the generated debian folder in nightly/deploy workflows, as I don't want to cache it.
|
|
Adds .deb generation for aarch64 and armv7 gnu targets in the nightly and deploy workflows.
|
|
|
|
Make a note of release sizes in the nightly/deploy scripts. This is mostly just in case I need to refer to it in the future (mainly for nightly, as the actual generated files are overwritten daily).
|
|
|
|
Adds musl targets to the nightly and deployment workflows.
|
|
|
|
|
|
Moves the rustfmt step into the supported job, to avoid having to wait too long for machine spinup time if they are separate jobs.
|
|
This encompasses features that we want on deployment.
|
|
|
|
|
|
|
|
Disables incremental compilation and debug symbols in CI and other related workflows, since they're not used there at all. Also forces --locked as needed.
|
|
|
|
Super small change, install cargo-llvm-cov with --locked.
|
|
|
|
|
|
This changes various as_ref() calls as needed in order for bottom to successfully build in Rust beta 1.61, as they were causing type inference issues. These calls were either removed or changed to an alternative that does build (e.g. as_slice()).
Functionally, there should be no change.
For context, see:
- https://github.com/ClementTsang/bottom/issues/708
- https://github.com/rust-lang/rust/issues/96074
|
|
Adds --locked to the build process for nightly and deploy workflows.
|
|
|
|
Adds the asset for the manpage to cargo deb config. Also moves the generated manpage file to a .1.gz file. Also, moves back to a build script since that was causing some issues for the automatic Cargo.toml fields detection for manpage and completion generation.
To prevent compilation from happening every time, and only in CI, we use an env var to avoid generation steps.
|
|
Adds manpage generation to the build process, as well as following the xtask concept of adding additional build scripts that only need to run on deploy/nightly as opposed to `build.rs`. Note this doesn't follow the recommended method of using workplaces because I don't really want to shift the entire repo structure just for this.
More on xtask: https://github.com/matklad/cargo-xtask
|
|
Manually install the audit crate as part of the audit CI since it seems to be using too old of a version of Rust.
|
|
Removes the manual strip used in favour of the now native functionality in Cargo.
|
|
Update to use a manual install of cargo tarpaulin, fixes the wrong filename being checked in the skip action.
|
|
Add the specific packaging locations that I maintain bottom on, and fix some typos.
|
|
Seems like the 32-bit binary triggers false positives on VirusTotal.
Going to disable this for now.
|
|
Just adds an extra line to the template/docs to check if an existing issue already exists.
|
|
Removes the winget step from the deployment pipeline; it seems like a bot now manages winget deployments for bottom, which is nice.
|
|
|
|
Adds an indicator in the form of `$version (stable)` to make it easier to see which is the most recent stable version.
This is done via CI and mike:
1. Set the previous title to just `$version`. We can get this value by `mike list stable` and grepping for valid version tags (otherwise this might have issues with `$version (stable)`).
2. Deploy `$new_version` and alias to stable.
3. Update the `$new_version` to have a new title of `$new_version (stable)`.
|
|
Update support links in documentation; add section on WSL in Linux known issues.
|
|
Add an additional validation step to the .deb file generation in nightly and deployment workflows.
|
|
Fixes completion file generation being broken while the .deb file is made, due to using an incorrect path.
|
|
Pins some actions using a specific commit hash.
|
