For #28837. Fixing this all of this because we got multiple reports from the community and customers and these were also detected by Amazon Inspector. - Fixes CVE-2025-22871 by upgrading Go from 1.24.1 to 1.24.2. - `docker scout` now fails the daily scheduled action if there are CRITICAL,HIGH CVEs (we missed setting `exit-code: true`). - Report CVE-2025-46569 as not affected by it because of our use of OPA's go package. - Report CVE-2024-8260 as not affected by it because Fleet doesn't run on Windows. - The `security/status.md` shows a lot of changes because we are now sorting CVEs so that newest come first. --- - [X] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files) for more information. - [ ] Manual QA for all new/changed functionality - For Orbit and Fleet Desktop changes: - [ ] Make sure fleetd is compatible with the latest released version of Fleet (see [Must rule](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/fleetd-development-and-release-strategy.md)). - [ ] Orbit runs on macOS, Linux and Windows. Check if the orbit feature/bugfix should only apply to one platform (`runtime.GOOS`). - [ ] Manual QA must be performed in the three main OSs, macOS, Windows and Linux. - [ ] Auto-update manual QA, from released version of component to new version (see [tools/tuf/test](../tools/tuf/test/README.md)). - [ ] For unreleased bug fixes in a release candidate, confirmed that the fix is not expected to adversely impact load test results or alerted the release DRI if additional load testing is needed. |
||
|---|---|---|
| .. | ||
| config | ||
| build-and-check-fleetctl-docker-and-deps.yml | ||
| build-binaries.yaml | ||
| build-fleetd-base-msi.yml | ||
| build-fleetd-base-pkg.yml | ||
| build-fleetd_tables.yaml | ||
| build-orbit.yaml | ||
| check-automated-doc.yml | ||
| check-tuf-timestamps.yml | ||
| check-updates-timestamps.yml | ||
| check-vulnerabilities-in-released-docker-images.yml | ||
| close-stale-eng-initiated-issues.yml | ||
| code-sign-windows.yml | ||
| codeql-analysis.yml | ||
| db-upgrade-test.yml | ||
| dependency-review.yml | ||
| deploy-fleet-website.yml | ||
| deploy-vulnerability-dashboard.yml | ||
| docs.yml | ||
| dogfood-automated-policy-updates.yml | ||
| dogfood-deploy.yml | ||
| dogfood-gitops.yml | ||
| fleet-and-orbit.yml | ||
| fleetctl-preview-latest.yml | ||
| fleetctl-preview.yml | ||
| fleetd-tuf.yml | ||
| generate-desktop-targets.yml | ||
| generate-nudge-targets.yml | ||
| generate-osqueryd-targets.yml | ||
| golangci-lint.yml | ||
| goreleaser-fleet.yaml | ||
| goreleaser-orbit.yaml | ||
| goreleaser-snapshot-fleet.yaml | ||
| ingest-maintained-apps.yml | ||
| integration.yml | ||
| pr-helm.yaml | ||
| randokiller-go.yml | ||
| README.md | ||
| release-fleetctl-docker-deps.yaml | ||
| release-fleetd-base.yml | ||
| release-fleetd-chrome-beta.yml | ||
| release-fleetd-chrome.yml | ||
| release-helm.yaml | ||
| render-deploy.yml | ||
| scorecards-analysis.yml | ||
| test-bulk-operations-dashboard-changes.yml | ||
| test-db-changes.yml | ||
| test-fleetd-chrome.yml | ||
| test-go.yaml | ||
| test-js.yml | ||
| test-native-tooling-packaging.yml | ||
| test-packaging-build-docker-deps.yml | ||
| test-packaging.yml | ||
| test-puppet.yml | ||
| test-vulnerability-dashboard-changes.yml | ||
| test-website.yml | ||
| test-yml-specs.yml | ||
| tfvalidate.yml | ||
| trivy-scan.yml | ||
| update-certs.yml | ||
| update-old-tuf-timestamp-signature.yaml | ||
| update-osquery-versions.yml | ||
| update-tuf-timestamp-signature.yaml | ||
| verify-fleetd-base.yml | ||
Github Actions
Fleet uses Github Actions for continuous integration (CI). This document describes best practices and at patterns for writing and maintaining Fleet's Github Actions workflows.
Bash
By default, Github Actions sets the shell to bash -e for linux and MacOS runners. To help write
safer bash scripts in run jobs and avoid common issues, override the default by adding the following
to the workflow file
defaults:
run:
# fail-fast using bash -eo pipefail. See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference
shell: bash
By specifying the default shell to bash, some extra flags are set. The option pipefail changes
the behaviour when using the pipe | operator such that if any command in a pipeline fails, that
commands return code will be used a the return code for the whole pipeline. Consider the following
example in test-go.yaml
- name: Run Go Tests
run: |
# omitted ...
make test-go 2>&1 | tee /tmp/gotest.log
If the pipefail option was not set, this job would always succeed because tee would always
return success. This is not the intended behavior. Instead, we want the job to fail if make test-go fails.
Concurrency
Github Action runners are limited. If a lot of workflows are queued, they will wait in pending until a runner becomes available. This has caused issue in the past where workflows take an excessively long time to start. To help with this issue, use the following in workflows
# This allows a subsequently queued workflow run to interrupt previous runs
concurrency:
group: ${{ github.workflow }}-${{ github.head_ref || github.run_id}}
cancel-in-progress: true
When a workflow is triggered via a pull request, it will cancel previous running workflows for that
pull request. This is especially useful when changes are pushed to a pull request frequently.
Manually triggered workflows, workflows that run on a schedule, and workflows triggered by pushes to
main are unaffected.