As WRES team, I would like to identify a candidate for github Release v6.29, test it, and if it passes, deploy it; candidate RC1: 4273062ed22407a6d766ad73e7dfe637af7228ab wres-20250206-4273062.zip

[epag]

• 1 - Tag a commit as staging to kick off pre-release workflow (Pre-release github action; this tests db migration)
• 2 - Nominate a commit that has passed the pre-release workflow (Pre-release github action)
• 3 - Initiate staging release (initiate-release-deployment Jenkins workflow; emails will report test results for external service, system tests, and 900 series)
• 4 - Test candidate with identified alpha (internal) User Acceptance Tests (-ti)
• 5 - Test candidate as a standalone.
• 6 - Push yml files changed
• 7 - Tag the commits that produced the release that passed everything and was already deployed to -prod
• 8 - Update database documentation in wiki
• 9 - Update user documentation
• 10 - Close GitHub tickets actually completed in this release and move tickets not completed to backlog

[epag]

We should probably do library updates, its been awhile since our last update.

Also I saw that we can create ticket templates now so ill go ahead and create a deploy template for easier ticket creation going forward

[epag]

Dependency updates made it in, gonna wait for that to pass automated testing and then will kick off the deployment.

Going to take a walk while I wait for those results, will be back in around an hour

[epag]

Looks like pre-commit failed, investigating

[epag]

Ahh, I think its because latest was tagged as the docker release and I think we look for the zip files from the previous release. Going to change that and re-run the flow to see if that fixes things

[epag]

Pre-release testing passed