🔄 synced file(s) with upbound/sa-up

[upbound-bot]

synced local file(s) with upbound/sa-up.

Changed files

• synced local Makefile with remote shared/configurations/Makefile

---

This PR was created automatically by the repo-file-sync-action workflow run #12034829720

[village-labs-bot]

upbound/configuration-app #65

Change Summary

• Version upgrades for multiple core dependencies including UP (v0.34.0 -> v0.35.0), Crossplane CLI (v1.17.1 -> v1.18.0), and Crossplane (v1.17.1-up.1 -> v1.18.0-up.1)
• Uptest version bump from v1.1.2 to v1.2.0
• All changes are focused on the Makefile configuration with no functional code changes

Potential Vulnerabilities

• File: Makefile:120-122
• Code: ```
  UP_VERSION = v0.35.0
  CROSSPLANE_CLI_VERSION = v1.18.0
  CROSSPLANE_VERSION = v1.18.0-up.1

- Explanation: When upgrading multiple core dependencies simultaneously, there's a potential for version compatibility issues between components. Should verify that these versions have been tested together in a staging environment.

## Code Smells
None identified in this change set.

## Debug Logs
None identified in this change set.

## Unintended Consequences
- File: `Makefile:120-123`
- Code: ```
UP_VERSION = v0.35.0
CROSSPLANE_CLI_VERSION = v1.18.0
CROSSPLANE_VERSION = v1.18.0-up.1
UPTEST_VERSION = v1.2.0

• Explanation: Major version updates across multiple dependencies could potentially break existing workflows or automation scripts that depend on specific version behaviors. Teams should be notified of these changes.

• File: Makefile:120-122

• Code: ```
  UP_VERSION = v0.35.0
  CROSSPLANE_CLI_VERSION = v1.18.0
  CROSSPLANE_VERSION = v1.18.0-up.1

- Explanation: The simultaneous update of Crossplane CLI and Crossplane core versions might impact existing configurations or custom resources that rely on previous version specifications.

## Risk Score: 6

[kaessert]

/test-examples