[YUNIKORN-1028] move master branches to pseudo versions in go.mod

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0
• Component/s: core - common, shim - kubernetes
• Labels: pull-request-available
• Target Version: 1.0.0
• Assignee: Craig Condit
• Reporter: Wilfred Spiegelenburg
• Created: 13/Jan/22 23:30
• Updated: 04/May/22 23:52
• Resolved: 04/Feb/22 17:44

Description

The current go.mod for both the core and the k8shim point to a release tag of our own repositories. This is not correct.

The master branches should not point to a release tag as they can move while we go through our development process. Go provides the option to use a pseudo version for this and we should stick to that for master as per this comment https://go.dev/ref/mod#pseudo-versions:

Pseudo-versions may refer to revisions for which no semantic version tags are available. They may be used to test commits before creating version tags, for example, on a development branch.

Issue Links

• is caused by: YUNIKORN-1016 Update scheduler-interface dependency to v0.12.2-1 (core)
• is caused by: YUNIKORN-1017 Update dependencies to v0.12.2-1 (k8shim)
• is related to: YUNIKORN-371 Document how to manage and update go mod dependencies
• links to: GitHub Pull Request #363
• links to: GitHub Pull Request #371