chore(deps): pin dependencies

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
@types/nprogress (source)	devDependencies	pin	^0.2.3 -> 0.2.3
@types/react-test-renderer (source)	devDependencies	pin	^18.0.7 -> 18.0.7
electron	devDependencies	pin	^22.3.27 -> 22.3.27
node		pin	20 -> 20.10.0

Add the preset :preserveSemverRanges to your config if you don't want to pin your dependencies.

---

Configuration

📅 Schedule: Branch creation - "monthly" (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

[bmulholland]

@afonsojramos How would you like to pin dependencies?

Personally my approach is a lot more open, where I set broad version ranges in package.json (usually just "latest") and upgrade the lockfile only. But that's counter to most of the JS ecosystem, I think because most people are used to package.json for packages, not end projects.

[afonsojramos]

I see your point, but at the same time I don't think it affects much. We are the ones doing the releases, and we have the lock-files versioned, so it is probably best to stay with pinning.