Repository navigation
chore(release): prepare 0.3.9 - #8
Merged
Merged
Conversation
Force no-cache image builds and a new Cloud Run revision per tag so ListTasks omit-artifacts from 0.3.8 cannot stay behind a stale digest.
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
1 participant
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
cloudbuild.yaml:docker build --no-cache, tagCOMMIT_SHA+SHORT_SHA, Cloud Run--revision-suffix+SUPEROPTIX_GIT_SHAso tag deploys cannot stick on a stale image digest (makes the 0.3.8 ListTasks omit-artifacts fix land on a2a.superoptix.ai)After merge
Tag
v0.3.9→ Release to PyPI + Cloud Build → newsuperoptix-a2arevision. Then probe ListTasks.