| Age | Commit message (Collapse) | Author |
|---|
|
Rust toolchain updates every six weeks including clippy.
With new updates clippy can cover more cases that it previously missed so with weekly CI runs we can catch these cases and fix them in a timely manner.
|
|
to reduce the number of PRs it creates
|
|
Daily pull requests are a bit too frequent and just spam the list of PRs.
|
|
This reverts commit 348f30e23276b8a7722eb562a0a8995708e7c2dd.
There's a breaking change in v4 that currently prevents releases from building.
As such, revert the version bump for now until the breaking changes have been addressed.
|
|
v3 uses Node 16 which is slated for deprecation by GitHub Actions
|
|
v3 uses Node 16 which is slated for deprecation by GitHub Actions
|
|
v3 uses Node 16 which is slated for deprecation by GitHub Actions
|
|
Adds a GitHub Action that auto-adds a label to a PR in case there are merge conflicts.
|
|
The filename was changed in #620 but the CI config was never updated
accordingly.
As such it still tried to upload the old filename and would silent fail.
|
|
The repo root dir also has a `package.json` which contains the necessary
build tools. We wanna keep those up-to-date as well.
|
|
|
|
Adds config for running dependabot to make PRs whenever some dependency is outdated.
Should check both Rust and NodeJS dependencies.
|
|
Clippy checks for common errors and fails the CI if one is spotted
|
|
* build: Upload Windows installer separately
addtionally to zip with debug files
* build: Upload Linux AppImage separately
addtionally to zip with debug files
* fix: Actually upload to separate zip
|
|
build: Only upload platform relevant artifact
as opposed to attempt uploading artifacts not relevant to platform
Main reason of doing this is to remove the warning of "missing
artifacts" caused by e.g. Windows runner looking for Linux artifacts as
well next to Windows artifacts
|
|
instead of `npm install`
`npm clean-install` is recommended over `npm install` for CI pipelines.
|
|
Cause tag is ref not release
|
|
|
|
|
|
* build: Replace unmaintained action
Replaces actions-rs/toolchain with dtolnay/rust-toolchain and updates
some more code in the process.
* build: Do format check by invoking cargo directly
Instead of relying on unmaintained and outdated action
* build: Replace action for getting rust toolchain
Use dtolnay/rust-toolchain instead of unmaintained actions-rs/toolchain
* build: Replace action for getting rust toolchain
Use dtolnay/rust-toolchain instead of unmaintained actions-rs/toolchain
* build: Replace action for getting rust toolchain
Use dtolnay/rust-toolchain instead of unmaintained actions-rs/toolchain
* fix: Correct syntax error
|
|
Uploads the Windows debug symbols to sentry.io via CI
|
|
|
|
* build: Upload pdb as well
* build: Upload Windows pdb on release build
|
|
* build: Separate zips for artifacts
for Windows and Linux
* fix: Ensure separate folders
|
|
* feat: Initial trial to auto-generate TS bindings
That way instead of manually duplicating code, we can just run
`cargo test` to generate them.
* fix: Update forgotten imports
* refactor: Move FlightCoreVersion to autogen bind
TypeScript binding autogenerated from Rust code
* refactor: Move ReleaseInfo to autogen binding
TypeScript binding autogenerated from Rust code
* docs: Explain how to generate TS binds from Rust
* feat: Check for binding changes in CI
Checks for uncommitted binding changes in CI and fails if they differ
* style: Formatting fixes
|
|
* feat: Add Rust code format check to CI
* fix: Set path correctly
* chore: Fix formatting
* refactor: Run format check as separate step
* refactor: Rename stage
Co-authored-by: Rémy Raes <contact@remyraes.com>
---------
Co-authored-by: Rémy Raes <contact@remyraes.com>
|
|
* build: Attempt caching Rust build artifacts
* temp: Change to force recompile to test cache
* build: Set Rust workspace dir correctly
* temp: Change to force recompile to test cache
|
|
|
|
Version 2 uses Node 12 which is being deprecated by GitHub.
Version 3 should use Node 16 instead.
|
|
|
|
Remedies the issue that anyone pushing without access to private key
will see their CI fail.
|
|
|
|
|
|
It's the only one not supported by auto-update
Might reconsider once adding Flatpak support
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
