chore(deps): Bump @actions/glob from 0.4.0 to 0.6.1

[dependabot]

Bumps @actions/glob from 0.4.0 to 0.6.1.

Changelog

Sourced from @​actions/glob's changelog.

0.6.1

• Fix a bad import for minimatch

0.6.0

• Breaking change: Package is now ESM-only
  • CommonJS consumers must use dynamic import() instead of require()

0.5.1

• Bump @actions/core to 2.0.3

0.5.0

• Added excludeHiddenFiles option, which is disabled by default to preserve existing behavior #1791: Add glob option to ignore hidden files

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​actions/glob since your current version.

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)

[Lms24]

@dependabot rebase

[sentry]

Bug: Upgrading @actions/glob introduces a dependency on @actions/core@^3.0.0, which conflicts with the explicitly pinned direct dependency on @actions/core@1.10.1 in package.json.
_{Severity: HIGH}

Suggested Fix

To resolve the conflict, update the @actions/core dependency in both package.json files to a version compatible with what @actions/glob@0.6.1 expects, for example: "@actions/core": "^3.0.0".

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: dev-packages/node-overhead-gh-action/package.json#L35

Potential issue: The pull request upgrades the `@actions/glob` dependency to version
`0.6.1`. This new version of `@actions/glob` has a transitive dependency on
`@actions/core@^3.0.0`. However, the `package.json` files for `node-overhead-gh-action`
and `size-limit-gh-action` still explicitly pin the direct dependency to
`@actions/core@1.10.1`. This creates a version conflict between the direct dependency
(`1.10.1`) and the transitive dependency (`^3.0.0`). This incomplete dependency
migration is likely to cause runtime failures if the package manager resolves to version
`3.0.0`, as the code was written for the `1.x` API and major version bumps often include
breaking changes.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[Lms24]

why would you flag this? We use @actions/core for our actions in the repo. This has nothing to do with @actions/glob