Skip to content

Sync main -> release-0.2 #18

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Feb 11, 2025
Merged

Sync main -> release-0.2 #18

merged 4 commits into from
Feb 11, 2025

Conversation

BlaineEXE
Copy link
Contributor

Update release-0.2 branch with latest cloudbuild changes that will allow us to publish a release.

BlaineEXE and others added 4 commits February 6, 2025 15:35
Using `gcloud container images add-tag` to add tags to images built and
pushed to GCR was resulting in the added tags having a date of Dec. 31,
1969 (the epoch). In order to avoid tags having epoch dates, adjust the
cloudbuild script to use `--tag` arguments for each tag.

Signed-off-by: Blaine Gardner <[email protected]>
cloudbuild: fix epoch dating on staged image tags
When doing cloudbuilds for tagged releases, limit images to only a
single tag that represents the semver tag.

The registry.k8s.io tooling uses scripts to coordinate which images and
tags are promoted from staging to release. The script don't handle image
digests with multiple tags, and COSI can assume less release breakage by
not relying on more advanced handling.

When the cloudbuild script detects a release is happening, it will now
apply only the semver tag to the image.

Signed-off-by: Blaine Gardner <[email protected]>
…publish

cloudbuild: limit image release tags to semver only
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Feb 11, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BlaineEXE

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 11, 2025
@xing-yang
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 11, 2025
@k8s-ci-robot k8s-ci-robot merged commit f1f3921 into release-0.2 Feb 11, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants