- 
          
 - 
                Notifications
    
You must be signed in to change notification settings  - Fork 16
 
Description
Part of stackabletech/issues#759.
Note
During a Stackable release we update all dependencies in the operator-rs
repository. After these bumps, each workspace member is released using an
appropriate SemVer version. Later, each product operator repository can then
use the updates crates.
Replace the items in the task lists below with the applicable Pull Requests
- chore: Bump Rust version and workflow actions #1112
 - chore: Bump transitive Rust dependencies #1113 (These bumps are already included in stackable-operator 0.100.1)
 -  Verify crate versions using 
.scripts/verify_crate_versions.sh. -  
Push the release tags using.scripts/tag_and_push_release.sh. 
Update Rust Version and Workflow Actions
Note
The PR is usually titled: chore: Bump Rust version and workflow actions
-  Adjust the version of the channel in the 
rust-toolchain.tomlfile. See https://releases.rs. -  Adjust the version 
RUST_TOOLCHAIN_VERSIONin the workflows:
-.github/workflows/build.yml
-.github/workflows/pre_commit.yaml
-.github/workflows/publish-docs.yaml -  Also adjust the nightly Rust toolchain version used for formatting (this should be kept in
sync across here, operator-templating and docker-images).
-.github/workflows/pre_commit.yaml
-.vscode/settings.json -  
Add a changelog entry. -  Update any actions (using the Git commit hash) in the workflows. Hint: Also make sure that the
cargo-udepsaction is up-to-date, otherwise the CI might report errors. 
Update Rust Dependencies
Note
This PR is usually titled: chore: Bump Rust dependencies
-  
Bump minor versions of dependencies in theCargo.tomlmanifest. -  Then run the 
cargo updatecommand. -  
Fix any code which needs updating due to the dependency bumps. - Locally update any product operator to identify any breaking changes downstream. The secret-operator already uses the updated transitive dependencies through stackable-operator 0.100.1, see feat(crd): Mark certManager as non-experimental secret-operator#649.
 -  
Add a changelog entry if required. 
Adjust and Verify Crate Versions
Warning
Currently, all workspace members use 0.X.Y versions. This means we can
introduce breaking changes in any version without needing to bump the major
level. But we still have the following rules:
- Breaking changes (internally and externally) will bump the minor level of
the version, so0.X.Ybecomes0.X+1.Y. - All other non-breaking changes will bump the patch level of the version, so
0.X.Ybecomes0.X.Y+1. 
Note
The PR is usually titled: chore: Release workspace members
-  
Bump the crate versions in their appropriateCargo.tomlmanifests. -  
Verify the previous step using.scripts/verify_crate_versions.sh. 
Metadata
Metadata
Assignees
Labels
Type
Projects
Status