Adding changes for Fleet v4.87.1

[georgekarrv]

Summary by CodeRabbit

• Chores
  • Bumped Fleet to version v4.87.1 across Helm, Terraform, and the npm package.
  • Updated deployment image tags so environments using the chart or infrastructure defaults will pick up the new release.

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.

_{Tip: disable this comment in your organization's Code Review settings.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: b2c74d9a-99c8-4a62-a436-18e2b9699aec

📥 Commits

Reviewing files that changed from the base of the PR and between 0893409 and 11dca0c.

📒 Files selected for processing (1)

• charts/fleet/Chart.yaml

✅ Files skipped from review due to trivial changes (1)

• charts/fleet/Chart.yaml

---

Walkthrough

Version references are updated from v4.87.0 to v4.87.1 across four files: the Helm chart appVersion in Chart.yaml, the container imageTag in values.yaml, the fleet_image and image variable defaults in the AWS and GCP Terraform configurations, and the version field in tools/fleetctl-npm/package.json.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	No pull request description was provided, so the required template fields are missing.	Add the template sections, including Related issue, Checklist for submitter, Testing, Database migrations, and New Fleet configuration settings as applicable.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title matches the change set by naming the Fleet v4.87.1 update.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch update-changelog-prepare-4.87.1-main

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Pull request overview

Updates Fleet release artifacts and deployment defaults to reflect the v4.87.1 patch release across tooling, infrastructure, Helm chart values, and the top-level changelog.

Changes:

• Bumped version references from v4.87.0 → v4.87.1 in fleetctl NPM package metadata, dogfood Terraform defaults (AWS/GCP), and Helm chart defaults.
• Updated Helm chart appVersion and default imageTag to v4.87.1.
• Added the Fleet 4.87.1 changelog section and adjusted a Hangar gitrepo test fixture to reference v4.87.1.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
tools/hangar/internal/gitrepo/git_test.go	Updates RC branch-name fixtures for branch parsing tests.
tools/fleetctl-npm/package.json	Bumps fleetctl NPM package version to v4.87.1.
infrastructure/dogfood/terraform/gcp/variables.tf	Updates default Fleet Docker image tag to v4.87.1 (GCP dogfood).
infrastructure/dogfood/terraform/aws/variables.tf	Updates default Fleet Docker image tag to v4.87.1 (AWS dogfood).
charts/fleet/values.yaml	Updates default Helm imageTag to v4.87.1.
charts/fleet/Chart.yaml	Updates Helm appVersion to v4.87.1.
CHANGELOG.md	Adds release notes for Fleet 4.87.1.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 67.30%. Comparing base (7013549) to head (0893409).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #48291      +/-   ##
==========================================
- Coverage   67.31%   67.30%   -0.01%     
==========================================
  Files        3661     3661              
  Lines      231522   231530       +8     
  Branches    12264    12264              
==========================================
- Hits       155848   155841       -7     
- Misses      61726    61736      +10     
- Partials    13948    13953       +5     

Flag	Coverage Δ
backend	68.88% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[lukeheath]

Helm chart version bump?

[georgekarrv]

Ready for you again @lukeheath

[qodo-free-for-open-source-projects]

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: aggregate-result

Failed stage: Check for failures [❌]

Failed test name: vuln-mysql8.0.44

Failure summary: The action failed because at least one test job reported a failure status: - The workflow script scanned downloaded status files and found ./vuln-mysql8.0.44-status/status contained fail (lines 171-175). - As a result, it reported ❌ One or more test jobs failed: vuln-mysql8.0.44 and exited with code 1 (lines 191-192).

Relevant error logs: 1: ##[group]Runner Image Provisioner 2: Hosted Compute Agent ... 126: Artifact download completed successfully. 127: Extracting artifact entry: /home/runner/work/fleet/fleet/integration-enterprise-mysql8.0.44-status/status 128: Extracting artifact entry: /home/runner/work/fleet/fleet/service-mysql8.0.44-status/status 129: Artifact download completed successfully. 130: Artifact download completed successfully. 131: Extracting artifact entry: /home/runner/work/fleet/fleet/integration-core-mysql8.0.44-status/status 132: Artifact download completed successfully. 133: Extracting artifact entry: /home/runner/work/fleet/fleet/fast-status/status 134: Extracting artifact entry: /home/runner/work/fleet/fleet/scripts-status/status 135: Artifact download completed successfully. 136: Artifact download completed successfully. 137: Extracting artifact entry: /home/runner/work/fleet/fleet/main-mysql8.0.44-status/status 138: Artifact download completed successfully. 139: Total of 10 artifact(s) downloaded 140: Download artifact has finished successfully 141: ##[group]Run failed_tests="" 142: �[36;1mfailed_tests=""�[0m 143: �[36;1mstatus_count=0�[0m 144: �[36;1m# Find all status files (they are in directories like 'fleetctl-mysql8.0.44-status/status')�[0m 145: �[36;1mfor status_file in $(find ./ -type f -name 'status'); do�[0m 146: �[36;1m status_count=$((status_count + 1))�[0m 147: �[36;1m # Extract test name from parent directory (e.g., 'fleetctl-mysql8.0.44-status')�[0m 148: �[36;1m test_dir=$(basename $(dirname "$status_file"))�[0m 149: �[36;1m # Remove '-status' suffix to get the test name�[0m 150: �[36;1m test_name="${test_dir%-status}"�[0m 151: �[36;1m status_content=$(cat "$status_file")�[0m 152: �[36;1m echo "Processing: $status_file (Test: $test_name) with status content: $status_content"�[0m 153: �[36;1m if grep -q "fail" "$status_file"; then�[0m 154: �[36;1m echo " ❌ Test failed: $test_name"�[0m 155: �[36;1m failed_tests="${failed_tests}${test_name}, "�[0m 156: �[36;1m else�[0m 157: �[36;1m echo " ✅ Test passed: $test_name"�[0m 158: �[36;1m fi�[0m 159: �[36;1mdone�[0m 160: �[36;1mif [[ $status_count -eq 0 ]]; then�[0m 161: �[36;1m echo "❌ ERROR: No status files found! This indicates a workflow issue."�[0m 162: �[36;1m exit 1�[0m 163: �[36;1mfi�[0m 164: �[36;1mif [[ -n "$failed_tests" ]]; then�[0m 165: �[36;1m echo "❌ One or more test jobs failed: ${failed_tests%, }"�[0m 166: �[36;1m exit 1�[0m 167: �[36;1mfi�[0m 168: �[36;1mecho "✅ All test jobs succeeded."�[0m 169: shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0} 170: ##[endgroup] 171: Processing: ./fleetctl-mysql8.0.44-status/status (Test: fleetctl-mysql8.0.44) with status content: success 172: ✅ Test passed: fleetctl-mysql8.0.44 173: Processing: ./vuln-mysql8.0.44-status/status (Test: vuln-mysql8.0.44) with status content: fail 174: ❌ Test failed: vuln-mysql8.0.44 175: Processing: ./service-mysql8.0.44-status/status (Test: service-mysql8.0.44) with status content: success 176: ✅ Test passed: service-mysql8.0.44 177: Processing: ./integration-core-mysql8.0.44-status/status (Test: integration-core-mysql8.0.44) with status content: success 178: ✅ Test passed: integration-core-mysql8.0.44 179: Processing: ./mysql-mysql8.0.44-status/status (Test: mysql-mysql8.0.44) with status content: success 180: ✅ Test passed: mysql-mysql8.0.44 181: Processing: ./integration-enterprise-mysql8.0.44-status/status (Test: integration-enterprise-mysql8.0.44) with status content: success 182: ✅ Test passed: integration-enterprise-mysql8.0.44 183: Processing: ./integration-mdm-mysql8.0.44-status/status (Test: integration-mdm-mysql8.0.44) with status content: success 184: ✅ Test passed: integration-mdm-mysql8.0.44 185: Processing: ./scripts-status/status (Test: scripts) with status content: success 186: ✅ Test passed: scripts 187: Processing: ./fast-status/status (Test: fast) with status content: success 188: ✅ Test passed: fast 189: Processing: ./main-mysql8.0.44-status/status (Test: main-mysql8.0.44) with status content: success 190: ✅ Test passed: main-mysql8.0.44 191: ❌ One or more test jobs failed: vuln-mysql8.0.44 192: ##[error]Process completed with exit code 1. 193: Post job cleanup.

[rfairburn]

🎉 🥇