ci: update workflows on release/25.10-lts

[fluentdo-ci]

Update workflows automatically on release/25.10-lts

• Created by https://github.com/telemetryforge/agent/actions/runs/21254450253
• Auto-generated by create-pull-request: https://github.com/peter-evans/create-pull-request

---

Summary by cubic

Rebranded CI workflows to Telemetry Forge on release/25.10-lts so builds, tests, and releases publish to the right registries and paths. Also disabled RocksDB ZSTD compression in record dedup to avoid issues on this LTS branch.

• Refactors

  • Switch images to ghcr.io/telemetryforge/agent (UBI, Debian) and rename FLUENTDO_* to TELEMETRY_FORGE_*.
  • Update repo refs/coverage/docs links, labels, and artifact names/paths (tar, GCS).
  • Remove Homebrew update workflow.
  • Add package test debugging; fix K8s/BATS/package test paths; add zlib for unit tests.

• Bug Fixes

  • Temporarily set RocksDB compression to none in flb_record_dedup.c (tracks issue Enable compression support for RocksDB #192).

^{Written for commit 8d92e7d. Summary will update on new commits.}

[cubic-dev-ai]

2 issues found across 12 files (changes from recent commits).

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name=".github/workflows/call-build-containers.yaml">

<violation number="1">
P1: Restore the `build-args: |` key so the test image build receives build arguments and the workflow remains valid YAML.</violation>
</file>

<file name=".github/workflows/call-build-macos-packages.yaml">

<violation number="1">
P2: The linkage check points to `bin/fluentdo-agent`, but the project’s executable is `fluent-bit`. This will make the linkage check fail and skip validation. Use the actual binary name to ensure the check runs.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P2: The linkage check points to bin/fluentdo-agent, but the project’s executable is fluent-bit. This will make the linkage check fail and skip validation. Use the actual binary name to ensure the check runs.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At .github/workflows/call-build-macos-packages.yaml, line 96:

<comment>The linkage check points to `bin/fluentdo-agent`, but the project’s executable is `fluent-bit`. This will make the linkage check fail and skip validation. Use the actual binary name to ensure the check runs.</comment>

<file context>
@@ -93,13 +93,13 @@ jobs:
               continue-on-error: true
               run: |
-                  DYLD_PRINT_LIBRARIES=1 DYLD_PRINT_LIBRARIES_POST_LAUNCH=1 DYLD_PRINT_RPATHS=1 bin/telemetryforge-agent --dry-run
+                  DYLD_PRINT_LIBRARIES=1 DYLD_PRINT_LIBRARIES_POST_LAUNCH=1 DYLD_PRINT_RPATHS=1 bin/fluentdo-agent --dry-run
               working-directory: source/build
 
</file context>

[patrick-stephens]

@cubic-dev-ai this change is incorrect so we should flag that next time

[cubic-dev-ai]

1 issue found across 1 file (changes from recent commits).

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="source/src/flb_record_dedup.c">

<violation number="1" location="source/src/flb_record_dedup.c:310">
P1: Rule violated: **Ensure tests are added**

Production code under `source/` was modified without any corresponding test changes under `source/tests/` or `source/testing/`, which violates the requirement to add/update automated tests for source changes (rule: Ensure tests are added).</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}