chore: set minimum age gap for dependencies update

[latin-panda]

I have verified this PR works in these browsers (latest versions):

• Chrome
• Firefox
• Safari (macOS)
• Safari (iOS)
• Chrome for Android
• Not applicable

What else has been done to verify that this works as intended?

Why is this the best possible solution? Were any other approaches considered?

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

Do we need any specific form for testing your changes? If so, please attach one.

What's changed

Discussed here

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1b78a45

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[matthew-white]

In Central, we're also doing ignore-scripts=true (not sure what the yarn equivalent is).

[garethbowen]

Approved because it's a step in the right direction. We should standardise on the ODK policy when it's decided.

I think ignore scripts is also very important because that stops the worst hacks. We can opt back in to specific scripts that we need to run by setting the dependenciesMeta in the package.json.

[latin-panda]

Removing this because the project uses Yarn 4, packageManager, and Volta, which should be sufficient.