Add 'exclude-newer' configuration to uv tool in pyproject.toml files

[Dashing-Nelson]

Added exlcuding newer than 7 days for python libs

[Copilot]

Pull request overview

Adds an Astral uv resolver constraint (exclude-newer) across the workspace and its member projects to avoid selecting very recently published Python packages during dependency resolution.

Changes:

• Added [tool.uv] exclude-newer = "1 week" to the workspace pyproject.toml.
• Added [tool.uv] exclude-newer = "1 week" to argo-test and argo-kedro project pyproject.toml files.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
pyproject.toml	Introduces uv config at the workspace root.
argo-test/pyproject.toml	Introduces uv config for the argo-test project.
argo-kedro/pyproject.toml	Introduces uv config for the argo-kedro project.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

In TOML, declaring a parent table after a child table is invalid in strict parsers. Since [tool.uv.workspace] already creates the tool.uv table, adding a later [tool.uv] header can cause the file to fail to parse (e.g., with Python tomllib) and break tooling that reads pyproject.toml. Move [tool.uv] (and exclude-newer) above [tool.uv.workspace], or place exclude-newer in a way that doesn’t reopen the parent table.

Suggested change

	[tool.uv.workspace]
	members = ["argo-kedro", "argo-test"]
	[tool.uv]
	exclude-newer = "1 week"
	[tool.uv]
	exclude-newer = "1 week"
	[tool.uv.workspace]
	members = ["argo-kedro", "argo-test"]

[Copilot]

This file already defines [tool.uv.sources] earlier, which creates the tool.uv table. Adding [tool.uv] later can be invalid TOML (parent table declared after child) and may fail parsing in strict TOML parsers. Reorder the sections so [tool.uv] appears before [tool.uv.sources] (or avoid reopening tool.uv).