Skip to content
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

Release v0.57.3 #2008

Merged
merged 5 commits into from
Feb 19, 2025
Merged

Conversation

lubronzhan
Copy link
Collaborator

@lubronzhan lubronzhan commented Feb 18, 2025

What this PR does / why we need it:

Which issue(s) this PR fixes

  • Fixes #

Special notes for your reviewer:

Release note:

Release v0.57.3

@SR11-avgo
Copy link

@lubronzhan I think your previous changes to remove exclude were not incorporated in the MR? I see you merged that change..can we rebuild?

Signed-off-by: Lubron Zhan <[email protected]>
@lubronzhan lubronzhan force-pushed the topic/lubron/release-0.57.3 branch from 384e192 to 96d1865 Compare February 18, 2025 22:04
@lubronzhan lubronzhan force-pushed the topic/lubron/release-0.57.3 branch from 6014ed0 to 7c25084 Compare February 18, 2025 22:48
@@ -156,7 +151,7 @@ dockerLibraryRegistry: mirror.gcr.io/library
Then on running conformance:

```bash
sonobuoy run --sonobuoy-image projects.registry.vmware.com/sonobuoy/sonobuoy:<VERSION> --e2e-repo-config conformance-image-config.yaml
sonobuoy run --sonobuoy-image sonobuoy/sonobuoy:<VERSION> --e2e-repo-config conformance-image-config.yaml
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Address as mentioned #1987 (review)

@@ -162,7 +157,7 @@ dockerLibraryRegistry: mirror.gcr.io/library
Then on running conformance:

```bash
sonobuoy run --sonobuoy-image projects.registry.vmware.com/sonobuoy/sonobuoy:<VERSION> --e2e-repo-config conformance-image-config.yaml
sonobuoy run --sonobuoy-image sonobuoy/sonobuoy:<VERSION> --e2e-repo-config conformance-image-config.yaml
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Address as mentioned #1987 (review)

@@ -19,7 +19,7 @@ Explicit doc changes (if any) should be made to the appropriate files in directo
Next, generate a set of versioned docs for v0.x.y. For instance, the new docs be generated by running the command:

```
./scripts/update_docs.sh v0.20.0
./scripts/update_docs.sh -v v0.57.3 -b
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The doc was wrong

@lubronzhan
Copy link
Collaborator Author

Move the refactoring of update_docs here #2009

@lubronzhan lubronzhan merged commit a988242 into vmware-tanzu:main Feb 19, 2025
20 checks passed
@lubronzhan lubronzhan deleted the topic/lubron/release-0.57.3 branch February 19, 2025 01:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants