Skip to content

Patch Release 1.52.1 #4284

@igooch

Description

@igooch

Patch Release 1.52.1

Modified release steps for creating a release patch version.

The cherry picked commit is specific to the fix for the Bitnami image #4270.

Steps

  • Run make shell and run gcloud config configurations activate agones-images.
  • git checkout release-1.52.0 && git pull --rebase upstream release-1.52.0
  • Run git cherry-pick 409a6fc3e96d82bda9a16fb10b6288d82c5fd356
  • Run make pre-build-release to ensure all example images exist on agones-images/examples repository and to deploy the 1.52.1-1 service on GCP/App Engine/Services.
  • Manual update references to 1.52.0 to 1.52.1 (the script sdk-update-version does not currently have a function for patching.)
    • "build/Makefile",
    • "install/helm/agones/Chart.yaml",
    • "install/yaml/install.yaml",
    • "install/helm/agones/values.yaml",
    • "sdks/nodejs/package.json",
    • "sdks/nodejs/package-lock.json",
    • "sdks/unity/package.json",
    • "sdks/csharp/sdk/AgonesSDK.nuspec",
    • "sdks/csharp/sdk/csharp-sdk.csproj",
    • "sdks/rust/Cargo.toml"
  • Create a draft release with the release template.
    • run make release-example-image-markdown to populate example images and append the output in Images available with this release section
    • Draft a new release with release draft. Update the Tag version and Release title with the release version and click on Generate release notes to generate the release notes with Full Changelog info for 1.52.1. Make sure to add the description. Include the Images available with this release section from the previous step that will be present after the Full Changelog and save the draft.
    • copy the 1.52.1 release details from the Full Changelog and paste it on top of the CHANGELOG.md file
  • Site updated
    • Create a new file named 1.52.1.md in /site/content/en/blog/releases. Copy the draft release content in this file (this will be what you send via email)[refer the previous release file].
    • run make site-server frequently to make sure everything looks fine for the release in your localhost
    • Run make del-data-proofer-ignore FILENAME=1.52.1-1.md to remove the data-proofer-ignore attribute from the previous release blog. Review all occurrences of the link_test and data-proofer-ignore attributes globally. Exclude html and release files.
    • config.toml updates:
      • Run make site-config-update-version to update the release version and sync data between dev and prod.
      • Update documentation with updated example images tags.
  • Create PR with these changes, and merge them with an approval.
  • Note: For the patch release, you will be working on the release-1.52.0 branch. There's no need to run the git remote update && git checkout main && git reset --hard upstream/main command.
  • Publish SDK packages
    • Run make sdk-shell-node to get interactive shell to publish node package. Requires Google internal process to publish.
    • Run make sdk-publish-csharp to deploy to NuGet. Requires login credentials. Will need NuGet API Key from Agones account.
  • Run make post-build-release to build the artifacts in GCS (These files will be attached in the release notes) and to push the latest images in the release repository and push chart on agones-chart.
  • Run make tag-deprecated-images to tag images from the previous version with a deprecated-public-image-<version> label, indicating they are no longer actively maintained.
  • Run make shell and run gcloud config configurations activate <your development project> to switch Agones development tooling off of the agones-images project.
  • Smoke Test: run make install-release to view helm releases, uninstall agones-system namespace, fetch the latest version of Agones, verify the new version, installing agones-system namespace, and list all the pods of agones-system. (Use git log to ensure that you are testing the same set of changes as the patch release.)
  • Attach all assets found in the cloud storage with 1.52.1 to the draft GitHub Release.
  • Copy any review changes from the release blog post into the draft GitHub release.
  • Publish the draft GitHub Release.
  • Note: For a patch release, you can skip the create release branch step as you are already on the release branch.
  • Run make sdk-publish-rust. This command executes cargo login for authentication, performs a dry-run publish, and if that succeeds, does the actual publish. Will need crate's API TOKEN from your crate's account.
  • In test/sdk/go/Makefile, change release_version to 1.52.1.
    • Run make shell and execute gcloud config configurations activate agones-images.
    • Within the shell, cd to the test/sdk/go/ directory and run make cloud-build.
  • Verify and update Kubernetes version support and Agones version mappings in test/upgrade/versionMap.yaml.
    • Update ReleaseVersion to the current release 1.52.1.
  • Create a PR with these changes and merge it with approval.
  • Email mailing lists with the release details (copy-paste the release blog post). Refer to the Internal Mailing list posting guide for details.
  • Paste the announcement blog post to the #users Slack group.
  • Post to the agonesdev Twitter account.
  • Close this issue. Congratulations! - the patch release is now complete! 🎉 👏 😄 👍

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions