Skip to content

Conversation

@michalChrobot
Copy link
Collaborator

@michalChrobot michalChrobot commented Oct 23, 2025

Purpose of this PR

This PR modified the release automation schedule with the following improvements:

  1. Automated trigger release will happen on Sunday rather then Saturday since we noticed that for America time it could be executed on Friday afternoon so running this on Sunday should resolve this issue.
  2. The CI job will fail silently if it will fail the validation part. It will show as success in Yamato but there will be a message stating that release preparation was not execute due to .... This is because we were getting a bit of spam due to weekly failures of this job which actually was an expected bahevior.
  3. I modified the job so we can trigger it manually. In that case the date check will be bypassed (we can trigger this manually whenever needed. Note that this should be the advised way of creating the release
  4. I had to modify bot permissions so it can push commits to develop-2.0.0 branch. I modified rule for develop and develop-2.0.0 branches with "Allow specified actors to bypass required pull requests" to allow scv-netcode-sdk bot to do this (release related commits)
  5. I regenerated recipes for Wrench jobs since we branched with editors (I may consider automatically regenerating recipes in the future via automation)
  6. I added recipe regeneration step as part of the release branch setup. This way we can resolve the issue that content of wrench scripts is dynamically created depending on editors availability so it may differ even without wrench update (newely branched editor)

From some nitpicks

  • I temporarily updated BossRoom branch until my PR there lands so I can build with latest changes that we want
  • I updated the TargetFramework for standards check
  • I updated a typo in cmb test definition in runAll set

Jira ticket

N/A

Documentation

N/A

Testing & QA (How your changes can be verified during release Playtest)

I will verify changes on test branch + manually trigger this for 2.7.0 release

Backports

Backported to develop in #3745

@michalChrobot michalChrobot self-assigned this Oct 23, 2025
@michalChrobot michalChrobot marked this pull request as ready for review October 26, 2025 16:38
@michalChrobot michalChrobot merged commit ada5be0 into develop-2.0.0 Oct 27, 2025
20 of 25 checks passed
@michalChrobot michalChrobot deleted the modify-release-automation-schedule branch October 27, 2025 11:44
michalChrobot added a commit that referenced this pull request Oct 27, 2025
* Ser release frequency to 10 AM on Sunday's

* Make the release fail silently when release conditions are not met

* Added possibility of a manual trigger that is disregarding the release date

* Removed standards failure about "Using directive is unnecessary"

* Revert "Removed standards failure about "Using directive is unnecessary""

This reverts commit 722b5b9.

* Updated wrench

* temp update of BossRoom branch + TargetFramework update

* Updated typo in cmb tests runAll definition

* Added wrench regeneration step to the release automation

* removed apparently unnecessary directive

* surpressed standards check complaint
michalChrobot added a commit that referenced this pull request Oct 27, 2025
* ci: Corrections to release automation (#3737)

* Ser release frequency to 10 AM on Sunday's

* Make the release fail silently when release conditions are not met

* Added possibility of a manual trigger that is disregarding the release date

* Removed standards failure about "Using directive is unnecessary"

* Revert "Removed standards failure about "Using directive is unnecessary""

This reverts commit 722b5b9.

* Updated wrench

* temp update of BossRoom branch + TargetFramework update

* Updated typo in cmb tests runAll definition

* Added wrench regeneration step to the release automation

* removed apparently unnecessary directive

* surpressed standards check complaint

* validation correction

* typo

* release trigger name correction

* added missed import

* typo

* corrected script name

* missing import
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants