Synchronize common files from prometheus/prometheus

[prombot]

Propagating changes from prometheus/prometheus default branch.

Source can be found here.

To check out this branch locally and push changes back:

git remote add prombot https://github.com/prombot/prometheus_alertmanager.git
git fetch prombot repo_sync
git checkout -b repo_sync prombot/repo_sync

Summary by CodeRabbit

• Chores
  • Updated internal CI/CD workflows to maintain compatibility with latest tooling versions.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: fa1b6639-1f7a-4539-89b0-9c79bbf13ad1

📥 Commits

Reviewing files that changed from the base of the PR and between 36afed4 and 8dce437.

📒 Files selected for processing (2)

• .github/workflows/govulncheck.yml
• .github/workflows/stale.yml

---

📝 Walkthrough

Walkthrough

This PR updates pinned commit SHAs for two GitHub Actions used in the repository's workflows. The govulncheck workflow is updated to use a newer version of golang/govulncheck-action, and the stale issue workflow is updated from v10.2.0 to v10.3.0 of actions/stale. No workflow logic or job structure is changed.

Changes

GitHub Actions Workflow Dependencies

Layer / File(s)	Summary
Govulncheck action update .github/workflows/govulncheck.yml	The golang/govulncheck-action step reference is updated to a new commit SHA while keeping the same action version label.
Stale issue action update .github/workflows/stale.yml	The actions/stale action is updated to v10.3.0 by changing the pinned commit SHA.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• prometheus/alertmanager#5187: Previously introduced the govulncheck workflow that is now having its action dependency updated.

Suggested reviewers

• TheMeier
• SoloJacobs

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description is minimal and lacks key sections from the template such as issue references, feature/bugfix categorization, user-facing changes, and release notes documentation.	Add release-notes block (even if 'NONE') and clarify whether this is a breaking change or requires documentation updates per the template.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change—synchronizing common files from the upstream prometheus/prometheus repository, which aligns with the actual changes to GitHub Actions workflow files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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 and usage tips.}