Crossplane V2.1.2 Release: Discussion And Steps

Introduction to Crossplane v2.1.2 Release

The Crossplane community is buzzing with excitement as we approach the release of v2.1.2 on December 1, 2025. This release marks a significant milestone in the evolution of Crossplane, bringing with it a host of improvements, bug fixes, and new features designed to enhance the user experience and expand the platform's capabilities. In this article, we'll delve into the discussion surrounding the release, the meticulous steps involved in cutting a new version, and how you can stay informed throughout the process. Understanding the intricacies of a release cycle helps users appreciate the robustness and reliability of Crossplane. This process ensures that each release meets the high standards expected by the community.

Understanding the Importance of a Structured Release Process

A structured release process is critical for maintaining the integrity and stability of any software project, especially one as complex and impactful as Crossplane. Each step in the process, from tagging the release to promoting it to stable channels, is designed to catch potential issues early and ensure a smooth transition for users. This rigorous approach minimizes disruptions and ensures that new features and bug fixes are delivered in a predictable and reliable manner. For Crossplane, this structured approach is particularly important due to its role in managing critical cloud infrastructure. A well-defined release process also fosters collaboration among contributors and provides transparency to the community. By following a clear set of steps, the release team can work efficiently and effectively, reducing the risk of errors and ensuring that all necessary tasks are completed on time. This process not only benefits the current release but also lays the foundation for future releases, creating a sustainable and scalable model for software development.

The Role of Community Discussion in Shaping the Release

The Crossplane release process isn't just about technical steps; it's also deeply rooted in community discussion and collaboration. Before any code is shipped, there are extensive discussions around what features and fixes should be included in the release. This ensures that the release aligns with the needs and priorities of the Crossplane community. The discussion category for this release provides a forum for users and contributors to share their thoughts, raise concerns, and offer suggestions. This feedback is invaluable in shaping the final product and ensuring that the release meets the diverse needs of the Crossplane user base. Open communication channels, such as Slack and GitHub, facilitate these discussions and allow for real-time collaboration. This collaborative approach not only improves the quality of the release but also fosters a sense of ownership and community among Crossplane users and contributors. By actively participating in these discussions, users can directly influence the direction of the project and contribute to its ongoing success.

Key Steps in Cutting the Crossplane v2.1.2 Release

Cutting a new release of Crossplane involves a series of carefully orchestrated steps, each designed to ensure the quality and stability of the final product. These steps, outlined in detail below, provide a comprehensive roadmap for the release team, ensuring that nothing is overlooked and that the release process adheres to the highest standards.

1. Tagging the Release

The first step in the release process is to tag the release. This involves running the Tag workflow on the release-2.1 branch with the appropriate release version, in this case, v2.1.2. The tag acts as a snapshot of the codebase at a specific point in time, providing a stable reference point for future builds and releases. A suggested message, such as "Release v2.1.2," is typically included to provide context and clarity. Tagging is a crucial step because it establishes a clear demarcation between the current state of the codebase and the upcoming release. This allows developers to continue working on new features and bug fixes without affecting the stability of the release. The Tag workflow automates much of the tagging process, reducing the risk of human error and ensuring consistency across releases. By tagging the release, the team creates a solid foundation for the subsequent steps in the release process.

2. Running the CI Workflow and Verifying the Build

Once the release is tagged, the next step is to run the CI workflow on the release branch. This automated process builds the release binaries and performs a series of tests to ensure that the code is functioning as expected. A key part of this step is verifying that the tagged build version exists on the releases.crossplane.io build channel. Specifically, the team checks that build/release-2.1/v2.1.2/... contains all the relevant binaries. This verification step is critical for ensuring that the release artifacts are properly built and available for distribution. The CI workflow acts as a safety net, catching any potential issues before they can impact users. By automating the build and testing process, the team can quickly identify and address any problems, reducing the risk of releasing a faulty version. This step is essential for maintaining the quality and reliability of Crossplane releases.

3. Promoting Patch Versions (Lowest to Highest)

When multiple patch versions are being released, it's crucial to promote them in the correct order – from lowest to highest. This ensures that the highest version is the last to be promoted, preventing the promote workflow from overwriting the latest patch release. For example, v1.12.2 should be promoted after v1.11.3. This ordering requirement is essential for maintaining the integrity of the release channels and ensuring that users receive the correct updates. However, there's an alternative approach: by checking the "pre-release" checkbox in the promote workflow for older releases, as described in [#5420], the ordering requirement can be avoided. This flexibility allows the team to streamline the release process while still maintaining the stability and reliability of the platform. Promoting patch versions in the correct order is a critical step in ensuring that users receive the intended updates and that the release channels remain consistent.

4. Promoting to the Stable Channel

After verifying the build, the next step is to promote the release to the stable channel. This involves running the Promote workflow with the channel set to stable on the release-2.1 branch. The team then verifies that the tagged build version exists on the releases.crossplane.io stable channel at stable/v2.1.2/.... Promoting to the stable channel signifies that the release has passed all necessary tests and is ready for general use. This step is a major milestone in the release process, as it makes the new version available to a wider audience. The Promote workflow automates the process of copying the release artifacts to the stable channel, ensuring a consistent and reliable deployment. By promoting to the stable channel, the team signals their confidence in the quality and stability of the release.

5. Publishing Release Notes

A crucial step in any software release is publishing detailed and informative release notes. For Crossplane v2.1.2, this involves creating a [new release] for the tagged version, using the same name as the version. The release notes should include a descriptive summary of the changes, bug fixes, and new features included in the release. A best practice is to generate the changes list by selecting v2.1.1 as the "Previous tag," which ensures that all changes since the previous patch release for the same minor version are included. Before publishing the release notes, it's essential to set them as a Draft and ask the rest of the team to double-check them. This peer review process helps to ensure accuracy and completeness, providing users with the information they need to effectively adopt the new release. Well-written release notes are invaluable for users, as they provide a clear understanding of the changes and improvements in the new version.

6. CloudFront Cache Invalidation

To ensure that users receive the latest version of the release artifacts, it's necessary to perform a CloudFront cache invalidation. This involves requesting @jbw976 to invalidate the cache on https://charts.crossplane.io/stable/ and https://releases.crossplane.io/stable/. Cache invalidation forces the content delivery network (CDN) to fetch the latest versions of the files, ensuring that users are not served outdated content. This step is particularly important for users who rely on automated updates or who have caching enabled in their environments. By invalidating the cache, the team ensures that all users have access to the most recent release artifacts, minimizing potential compatibility issues or unexpected behavior.

7. Notifying Users on Communication Channels

Communication is key to a successful release. It's essential to notify users of the new release on all relevant communication channels. This includes:

• Slack: #announcements channel on Crossplane's Slack workspace.
• Twitter: Reach out to a Crossplane maintainer or steering committee member (see [OWNERS.md]) to help disseminate the information.
• Bluesky: Same as Twitter.
• LinkedIn: Same as Twitter.

Consistent and timely communication ensures that users are aware of the new release and can plan their upgrades accordingly. Providing clear and concise information about the release, including its benefits and any potential impact, helps to facilitate a smooth transition for users. By leveraging multiple communication channels, the team can reach a wider audience and ensure that the message is effectively delivered.

8. Removing Extra Permissions

As a final step, it's important to remove any extra permissions that were granted to release team members specifically for this release. This is a security best practice that helps to minimize the risk of unauthorized access or accidental changes. By revoking these permissions, the team ensures that only authorized personnel have access to sensitive systems and resources. This step is often overlooked but is crucial for maintaining the security and integrity of the Crossplane project.

Staying Informed and Contributing to Future Releases

The Crossplane community is a vibrant and collaborative ecosystem, and there are many ways to stay informed and contribute to future releases. Here are a few suggestions:

Monitoring Communication Channels

Stay tuned to the #announcements channel on the Crossplane Slack workspace, follow Crossplane on Twitter and other social media platforms, and regularly check the Crossplane GitHub repository for updates and announcements. These channels provide valuable information about upcoming releases, community events, and other important news.

Participating in Discussions

Actively participate in discussions related to future releases. Share your thoughts, ask questions, and offer suggestions. Your feedback is crucial in shaping the direction of the project and ensuring that Crossplane continues to meet the needs of its users.

Contributing Code and Documentation

If you're a developer, consider contributing code or documentation to the project. Crossplane is an open-source project, and contributions from the community are highly valued. There are many ways to contribute, from fixing bugs to adding new features to improving the documentation.

Conclusion

The release of Crossplane v2.1.2 is a significant event for the community, and the meticulous process outlined above ensures that the release is stable, reliable, and meets the needs of its users. By understanding the steps involved in cutting a new release, users can appreciate the effort and expertise that goes into each version of Crossplane. Staying informed and actively participating in the community are key to ensuring the ongoing success of the project. We encourage you to explore the new features and improvements in v2.1.2 and to continue contributing to the Crossplane community.

For more information about Crossplane and its releases, visit the official Crossplane website.