oopsbagel
1c51e5ed6f
ci: release platform independent installer zips
...
Release one zip file for each operating system / architecture
combination supported by the installer.
2025-07-03 01:03:29 -07:00
oopsbagel
5d2a5a2577
Merge pull request #434 from oopsbagel/profile-release-strip-debuginfo
...
cargo/config: strip debuginfo from --release bins for a significantly smaller installer size
2025-06-28 11:00:28 +00:00
oopsbagel
a4f4e12a57
ci: build everything when .cargo changes
2025-06-28 01:06:56 -07:00
Simon Fondrie-Teitler
5f45ae31d8
Fail build on cargo check and clippy warnings
2025-06-27 23:23:27 +02:00
Markus Unterwaditzer
a17e255148
un-skip jobs for testing
2025-06-23 09:38:00 -07:00
Markus Unterwaditzer
0f98b05475
Try out rust-cache action
2025-06-23 09:38:00 -07:00
oopsbagel
5a7fc2a063
Merge pull request #387 from oopsbagel/wingtech-ct2mhs01
...
feat: support Wingtech CT2MHS01 hotspot
2025-06-20 08:00:56 +00:00
oopsbagel
185da9cb36
fix(ci): explain why workflow_call: is needed
2025-06-13 19:42:38 -07:00
oopsbagel
c366eb9e4d
fix(ci): restore deleted workflow_call trigger
...
This is required to call this workflow from another workflow, such as
the release.yml workflow.
2025-06-13 19:38:49 -07:00
Markus Unterwaditzer
02c98a8e8e
Do not publish docs from any branch
...
Documentation was being pushed from an unrelated PR that I opened,
because that PR was created from a branch pushed to efforg instead of my
own fork.
2025-06-14 02:10:56 +02:00
oopsbagel
cb6f79f67a
ci: build wingtech
2025-06-12 01:11:01 -07:00
oopsbagel
5749c305c6
ci: don't try to use env:
...
I apparently don't know how this works.
2025-06-06 12:30:36 -07:00
oopsbagel
f53688086d
ci: minor syntax and workflow order fixes
2025-06-06 12:21:24 -07:00
oopsbagel
bd2e0b4394
ci: release from actions, only test changed files
...
This commit introduces release automation triggered by button clicks in
Github Actions, guarded by a check on whether all the Cargo.toml files
contain the same version string.
On PRs, changes to documentation no longer trigger code tests.
Similarly, changes to code that don't update documentation do not
trigger documentation tests. Changes that fail at the `cargo check`
stage abort early to prevent lengthy CI builds of the installer and
firmware.
Commits on the `main` branch always run the full test suite regardless
of what changed.
Releases also run the full check, test, build and publish suite.
2025-06-06 12:21:24 -07:00
