Skip to content

Bump actions/stale from 10.0.0 to 10.2.0#46761

Closed
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/github_actions/actions/stale-10.2.0
Closed

Bump actions/stale from 10.0.0 to 10.2.0#46761
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/github_actions/actions/stale-10.2.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot bot commented on behalf of github Feb 21, 2026

Bumps actions/stale from 10.0.0 to 10.2.0.

Release notes

Sourced from actions/stale's releases.

v10.2.0

What's Changed

Bug Fix

Dependency Updates

New Contributors

Full Changelog: actions/stale@v10...v10.2.0

v10.1.1

What's Changed

Bug Fix

Improvement

Dependency Upgrades

New Contributors

Full Changelog: actions/stale@v10...v10.1.1

v10.1.0

What's Changed

New Contributors

Full Changelog: actions/stale@v10...v10.1.0

Commits
  • b5d41d4 build(deps-dev): bump lodash from 4.17.21 to 4.17.23 (#1313)
  • dcd2b94 Fix punycode and url.parse Deprecation Warnings (#1312)
  • d6f8a33 build(deps-dev): bump js-yaml from 4.1.0 to 4.1.1 (#1304)
  • a21a081 Fix checking state cache (fix #1136), also switch to octokit methods (#1152)
  • 9971854 build(deps): bump actions/checkout from 4 to 6 (#1306)
  • 5611b9d build(deps): bump actions/publish-action from 0.3.0 to 0.4.0 (#1291)
  • fad0de8 Improves error handling when rate limiting is disabled on GHES. (#1300)
  • 39bea7d Add Missing Input Reading for only-issue-types (#1298)
  • e46bbab build(deps-dev): bump @​types/node from 20.10.3 to 24.2.0 and document breakin...
  • 65d1d48 build(deps-dev): bump eslint-config-prettier from 8.10.0 to 10.1.8 (#1276)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added changelog/no-changelog No changelog entry needed dependencies PRs that bump a dependency dependencies-github-actions PRs that bump a gha dependency dev/tooling qa/no-code-change No code change in Agent code requiring validation team/agent-devx labels Feb 21, 2026
@dependabot dependabot bot requested a review from a team as a code owner February 21, 2026 20:32
@dependabot dependabot bot added changelog/no-changelog No changelog entry needed dependencies PRs that bump a dependency qa/no-code-change No code change in Agent code requiring validation dependencies-github-actions PRs that bump a gha dependency team/agent-devx labels Feb 21, 2026
@dd-octo-sts dd-octo-sts bot added the internal Identify a non-fork PR label Feb 21, 2026
@github-actions github-actions bot added the short review PR is simple enough to be reviewed quickly label Feb 21, 2026
@dependabot dependabot bot force-pushed the dependabot/github_actions/actions/stale-10.2.0 branch from f534148 to 145d9d8 Compare February 27, 2026 18:44
@agent-platform-auto-pr
Copy link
Copy Markdown
Contributor

agent-platform-auto-pr bot commented Feb 27, 2026

Files inventory check summary

File checks results against ancestor 86310699:

Results for datadog-agent_7.78.0~devel.git.260.50fdb65.pipeline.100012664-1_amd64.deb:

No change detected

@chouetz
Copy link
Copy Markdown
Member

chouetz commented Mar 3, 2026

@dependabot rebase

Bumps [actions/stale](https://github.com/actions/stale) from 10.0.0 to 10.2.0.
- [Release notes](https://github.com/actions/stale/releases)
- [Changelog](https://github.com/actions/stale/blob/main/CHANGELOG.md)
- [Commits](actions/stale@3a9db7e...b5d41d4)

---
updated-dependencies:
- dependency-name: actions/stale
  dependency-version: 10.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/github_actions/actions/stale-10.2.0 branch from 145d9d8 to 50fdb65 Compare March 3, 2026 14:02
@dd-octo-sts
Copy link
Copy Markdown
Contributor

dd-octo-sts bot commented Mar 3, 2026

/merge

@gh-worker-devflow-routing-ef8351
Copy link
Copy Markdown

gh-worker-devflow-routing-ef8351 bot commented Mar 3, 2026

View all feedbacks in Devflow UI.

2026-03-03 14:16:27 UTC ℹ️ Start processing command /merge


2026-03-03 14:16:35 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.


2026-03-03 19:05:15 UTC ⚠️ MergeQueue: This merge request was unqueued

devflow unqueued this merge request: It did not become mergeable within the expected time

@chouetz chouetz closed this Mar 16, 2026
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot bot commented on behalf of github Mar 16, 2026

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

This was referenced Mar 16, 2026
duncanista pushed a commit to DataDog/datadog-lambda-extension that referenced this pull request Mar 16, 2026
## Pin GitHub Actions to SHA hashes

This automated PR pins third-party GitHub Actions references from
mutable tag versions (e.g., `@v4`) to their corresponding SHA hashes
(e.g., `@abc123...`). The original tag is preserved as a comment for
readability. Your workflows will work exactly the same way. Internal
actions (under the `DataDog` organization) are not pinned.

Read
https://docs.github.com/en/actions/reference/security/secure-use#using-third-party-actions
for more details and info on how to configure this for entire repos.

### Why pin GitHub Actions?

Git tags are mutable: they can be moved to point to different commits at
any time. A compromised or malicious action maintainer could update a
tag to inject arbitrary code into your CI workflows (see the [tj-actions
incident](https://www.wiz.io/blog/github-action-tj-actions-changed-files-supply-chain-attack-cve-2025-30066)).
Pinning to SHA hashes ensures you always run the exact code you
reviewed, protecting your repository from supply chain attacks such as
the tj-actions incident.

### What if something breaks?

If a pinned action doesn't work for your use case, you can push a commit
directly to this branch to fix it. As a last resort, reach out to
**#sdlc-security** on Slack.

### Set up Dependabot or Renovate for automatic updates

Once actions are pinned to SHA hashes, you should configure Dependabot
or Renovate to receive weekly update PRs when new versions are
available.

In the case of Dependabot, create or update `.github/dependabot.yml`:
```yaml
version: 2
updates:
  - package-ecosystem: "github-actions"
    directory: "/"
    schedule:
      interval: "weekly"
    groups:
      github-actions:
        patterns:
          - "*"
    open-pull-requests-limit: 10
```

Dependabot will automatically propose PRs that update both the SHA hash
and the version comment like [in this
example](DataDog/datadog-agent#46761).

---
*This PR was automatically generated by the GitHub Actions Pinning tool,
owned by #sdlc-security.*
gh-worker-dd-mergequeue-cf854d bot pushed a commit to DataDog/dd-trace-go that referenced this pull request Mar 16, 2026
## Pin GitHub Actions to SHA hashes

This automated PR pins third-party GitHub Actions references from mutable tag versions (e.g., `@v4`) to their corresponding SHA hashes (e.g., `@abc123...`). The original tag is preserved as a comment for readability. Your workflows will work exactly the same way. Internal actions (under the `DataDog` organization) are not pinned.

Read https://docs.github.com/en/actions/reference/security/secure-use#using-third-party-actions for more details and info on how to configure this for entire repos.

### Why pin GitHub Actions?

Git tags are mutable: they can be moved to point to different commits at any time. A compromised or malicious action maintainer could update a tag to inject arbitrary code into your CI workflows (see the [tj-actions incident](https://www.wiz.io/blog/github-action-tj-actions-changed-files-supply-chain-attack-cve-2025-30066)). Pinning to SHA hashes ensures you always run the exact code you reviewed, protecting your repository from supply chain attacks such as the tj-actions incident.

### What if something breaks?

If a pinned action doesn't work for your use case, you can push a commit directly to this branch to fix it. As a last resort, reach out to **#sdlc-security** on Slack.

### Set up Dependabot or Renovate for automatic updates

Once actions are pinned to SHA hashes, you should configure Dependabot or Renovate to receive weekly update PRs when new versions are available.

In the case of Dependabot, create or update `.github/dependabot.yml`:
```yaml
version: 2
updates:
  - package-ecosystem: "github-actions"
    directory: "/"
    schedule:
      interval: "weekly"
    groups:
      github-actions:
        patterns:
          - "*"
    open-pull-requests-limit: 10
```

Dependabot will automatically propose PRs that update both the SHA hash and the version comment like [in this example](DataDog/datadog-agent#46761).

---
*This PR was automatically generated by the GitHub Actions Pinning tool, owned by #sdlc-security.*


Co-authored-by: kemal.akkoyun <kemal.akkoyun@datadoghq.com>
gh-worker-dd-mergequeue-cf854d bot pushed a commit to DataDog/httpd-datadog that referenced this pull request Mar 19, 2026
## Pin GitHub Actions to SHA hashes

This automated PR pins third-party GitHub Actions references from mutable tag versions (e.g., `@v4`) to their corresponding SHA hashes (e.g., `@abc123...`). The original tag is preserved as a comment for readability. Your workflows will work exactly the same way. Internal actions (under the `DataDog` organization) are not pinned.

Read https://docs.github.com/en/actions/reference/security/secure-use#using-third-party-actions for more details and info on how to configure this for entire repos.

### Why pin GitHub Actions?

Git tags are mutable: they can be moved to point to different commits at any time. A compromised or malicious action maintainer could update a tag to inject arbitrary code into your CI workflows (see the [tj-actions incident](https://www.wiz.io/blog/github-action-tj-actions-changed-files-supply-chain-attack-cve-2025-30066)). Pinning to SHA hashes ensures you always run the exact code you reviewed, protecting your repository from supply chain attacks such as the tj-actions incident.

### What if something breaks?

If a pinned action doesn't work for your use case, you can push a commit directly to this branch to fix it. As a last resort, reach out to **#sdlc-security** on Slack.

### Set up Dependabot or Renovate for automatic updates

Once actions are pinned to SHA hashes, you should configure Dependabot or Renovate to receive weekly update PRs when new versions are available.

In the case of Dependabot, create or update `.github/dependabot.yml`:
```yaml
version: 2
updates:
  - package-ecosystem: "github-actions"
    directory: "/"
    schedule:
      interval: "weekly"
    groups:
      github-actions:
        patterns:
          - "*"
    open-pull-requests-limit: 10
```

Dependabot will automatically propose PRs that update both the SHA hash and the version comment like [in this example](DataDog/datadog-agent#46761).

---
*This PR was automatically generated by the GitHub Actions Pinning tool, owned by #sdlc-security.*


Co-authored-by: julien.doutre <julien.doutre@datadoghq.com>
gh-worker-dd-mergequeue-cf854d bot pushed a commit to DataDog/dd-trace-rs that referenced this pull request Mar 20, 2026
## Pin GitHub Actions to SHA hashes

This automated PR pins third-party GitHub Actions references from mutable tag versions (e.g., `@v4`) to their corresponding SHA hashes (e.g., `@abc123...`). The original tag is preserved as a comment for readability. Your workflows will work exactly the same way. Internal actions (under the `DataDog` organization) are not pinned.

Read https://docs.github.com/en/actions/reference/security/secure-use#using-third-party-actions for more details and info on how to configure this for entire repos.

### Why pin GitHub Actions?

Git tags are mutable: they can be moved to point to different commits at any time. A compromised or malicious action maintainer could update a tag to inject arbitrary code into your CI workflows (see the [tj-actions incident](https://www.wiz.io/blog/github-action-tj-actions-changed-files-supply-chain-attack-cve-2025-30066)). Pinning to SHA hashes ensures you always run the exact code you reviewed, protecting your repository from supply chain attacks such as the tj-actions incident.

### What if something breaks?

If a pinned action doesn't work for your use case, you can push a commit directly to this branch to fix it. As a last resort, reach out to **#sdlc-security** on Slack.

### Set up Dependabot or Renovate for automatic updates

Once actions are pinned to SHA hashes, you should configure Dependabot or Renovate to receive weekly update PRs when new versions are available.

In the case of Dependabot, create or update `.github/dependabot.yml`:
```yaml
version: 2
updates:
  - package-ecosystem: "github-actions"
    directory: "/"
    schedule:
      interval: "weekly"
    groups:
      github-actions:
        patterns:
          - "*"
    open-pull-requests-limit: 10
```

Dependabot will automatically propose PRs that update both the SHA hash and the version comment like [in this example](DataDog/datadog-agent#46761).

---
*This PR was automatically generated by the GitHub Actions Pinning tool, owned by #sdlc-security.*


Co-authored-by: bjorn.antonsson <bjorn.antonsson@datadoghq.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/no-changelog No changelog entry needed dependencies PRs that bump a dependency dependencies-github-actions PRs that bump a gha dependency dev/tooling internal Identify a non-fork PR qa/no-code-change No code change in Agent code requiring validation short review PR is simple enough to be reviewed quickly team/agent-devx

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant