chore(deps): update dependency @types/node to v18.17.12

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	18.16.19 -> 18.17.12

---

Configuration

📅 Schedule: Branch creation - "before 3am on Friday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[codecov]

Codecov Report

Merging #1617 (337275b) into main (0fbacba) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1617   +/-   ##
=======================================
  Coverage   91.77%   91.77%           
=======================================
  Files         139      139           
  Lines        7112     7112           
  Branches     1427     1427           
=======================================
  Hits         6527     6527           
  Misses        585      585           

[blumamir]

LGTM, but while we are at it, we should probably also align opentelemetry-resource-detector-container which depend on caret range.

[pichlermarc]

@blumamir Hmm, I wonder if we even want to bump @types/node if we don't need to. Possibly we should ignore it in the renovate config. 🤔 I think in core we don't usually bump it.

[blumamir]

@blumamir Hmm, I wonder if we even want to bump @types/node if we don't need to. Possibly we should ignore it in the renovate config. 🤔

That's a good point. I guess it doesn't really matter either way.
Bumping the version regularly will float issues faster, but it is also more ongoing work for us.

I think in core we don't usually bump it.

If it was already agreed that's the way to go, then let's sync in contrib as well :)

regardless of what we decide, we should align opentelemetry-resource-detector-container to match the rest of the repo.

[blumamir]

@blumamir Hmm, I wonder if we even want to bump @types/node if we don't need to. Possibly we should ignore it in the renovate config. 🤔 I think in core we don't usually bump it.

@pichlermarc I don't see any config in core repo to ignore @types/node new versions, nor do I see relevant renovate PRs. What am I missing?

If we do decide to pin it, what version should we use for pinning? Since we support node 14, shouldn't the type reference the oldest supported major version so it guards us from using new node features which are not supported in node 14?

[blumamir]

replaced by #1653

[forking-renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (18.17.12). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.