Release v0.2.15

[qclayssen]

No description provided.

[scwatts]

You've also bumped the version of bolt here, I think that is probably accidental

[qclayssen]

I did it because of how the container names work. With ghcr.io/umccr/bolt:0.2.14-gpgr, if I don't bump to ghcr.io/umccr/bolt:0.2.15-gpgr, the image gets the same name for different GPGR versions. This could be confusing and, in specific cases, cause collisions if I resume a sash workflow.

One alternative approach could be to add the tool version in the tag like ghcr.io/umccr/bolt:0.2.14-gpgr-v2.2.0 or use a hash-based suffix.

[scwatts]

I may misunderstand, is this PR aiming to also create the bolt 0.2.15 release? Or is it more that you're trying to bump gpgr and wanting to use the CICD to build images, which needs the workaround described to avoid name clashes?

[qclayssen]

This PR is primarily aiming to bump GPGR to version 0.2.2. The bolt version bump to 0.2.15 is workaround for the container clashes

[scwatts]

Thanks for the details, I think I understand that you're wanting to bump gpgr to 2.2.0 (I believe 0.2.2 is a typo) and test this in sash

I have a couple suggestions here:

• build the images locally as we've done here to test in sash and make any changes required if you haven't already
• review and consider any other changes that could be included in the proposed 0.2.15 release
• have a PR with the desired changes and then another for specifically for the release as we've done here

[qclayssen]

I've already tested this with the latest gpgr in bolt. It's what sash on ICA for OA v2.2.0 is currently using. No other changes are needed to support OA v2.2.0, so I was thinking of making this a small bump version so that ICA doesn't have to work on a branch.

But since it's functional, I could alternatively add this change to the bolt release/0.3.0 linked to sash v0.7.0 release. which would require more testing.

[scwatts]

Thanks for the extra context, this is making sense now. I see two options:

• create the 0.2.15 release (split this PR into one for the gpgr version bump and another for the release PR)
• include the gpgr version bump in the changes for the 0.3.0 release as you've identified

Up to you how you'd prefer to handle!

[scwatts]

Taking this activity as you proceeding with 0.2.15 release option :) I'll approve the other PR shortly

[scwatts]

Change to 2.2.0

[scwatts]

This commit shouldn't be included in this PR; the set of commits in this PR should be merged with main or rebased on main

I can rebase if you like after you make the adjustment to the CHANGELOG.md file above

[scwatts]

LGTM, and thanks for making those adjustments!