Repository navigation
release: prepare TauGrid v0.4.7 with workspace lifecycle fixes - #490
Merged
Merged
Conversation
Contributor
Author
|
16-second evidence: the exact chart/CLI version diff followed by images rendered from the updated chart. Registry hostnames are redacted; this demonstrates release preparation, not published artifact availability. release-pins.mp4 |
Contributor
Author
|
Candidate CI completed successfully, including the full Linux CLI suite, Windows CLI/installer checks, Helm checks, and reproducible release assets: https://github.com/Azure/taugrid/actions/runs/40472471452 . The local macOS process-termination caveat above remains documented. Version tags are now protected against updates and deletion with no bypass actors. Publication remains gated on verified coordinated image/chart availability. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Current
mainincludes #433, but coordinated install defaults still select 0.4.6 and the last published GitHub release is v0.4.5. Prepare v0.4.7 with aligned chart/dependency versions, image pins, CLI and infrastructure defaults, install examples, and assertions. Add curated notes covering #433 and changes since v0.4.5; preserve the existing v0.4.6 tag and all independently versioned components.This is release preparation, not evidence that v0.4.7 artifacts are published. After integration, the annotated tag must point to the verified preparation commit on
main; publish and verify all coordinated images/charts before dispatching the release workflow from that exact tag.Related issue
Includes merged #433. No issue is closed by the version bump.
Validation
Local validation used macOS, Go 1.27.3, Helm 4.2.0, and helm-unittest 1.1.1.
The failing package is identical to
main; currentmainLinux CLI CI passed. The local process-termination failure remains unresolved and is not hidden or fixed by this version-only preparation. Candidate CI, including reproducible release assets and platform checks, must pass before integration. No live-cluster validation or publication has been performed.Compatibility and operational impact
Default installs select 0.4.7 after publication. Controller image and read-only source-workload RBAC must be upgraded together to include #433. Independent SDK, monitoring-chart, telemetry-chart, and Ray-image versions remain unchanged. Do not overwrite any existing release tag, image, chart, or release asset. Existing installations are not changed by merging this preparation.
Checklist
No new dependencies were introduced. Dependency archives were regenerated for local validation and are ignored by the repository. Privacy review found no new operational identities in the diff, branch, commit subject, or evidence.