Predrag Gruevski 0dd2c21089 Do not bust poetry install cache when manually installing pydantic v2. (#9407) ... Using `poetry add` to install `pydantic@2.1` was also causing poetry to change its lockfile. This prevented dependency caching from working: - When attempting to restore a cache, it would hash the lockfile in git and use it as part of the cache key. Say this is a cache miss. - Then, it would attempt to save the cache -- but the lockfile will have changed, so the cache key would be *different* than the key in the lookup. So the cache save would succeed, but to a key that cannot be looked up in the next run -- meaning we never get a cache hit. In addition to busting the cache, the lockfile update itself is also non-trivially long, over 30s:  This PR fixes the problems by using `pip` to perform the installation, avoiding the lockfile change.		2023-08-17 18:23:00 -04:00
..
actions/poetry_setup	Ensure the in-project venv gets cached in CI tests. (#9336)	2023-08-17 11:47:22 -04:00
ISSUE_TEMPLATE	Remove from PR template (#6018)	2023-06-11 19:34:26 -07:00
workflows	Do not bust poetry install cache when manually installing pydantic v2. (#9407)	2023-08-17 18:23:00 -04:00
CONTRIBUTING.md	update contributor guide (#8088)	2023-07-21 12:01:05 -07:00
PULL_REQUEST_TEMPLATE.md	update pr temp (#9062)	2023-08-10 11:10:06 -07:00