Skip to content

ci: fixing issues around Standards check#4097

Open
michalChrobot wants to merge 13 commits into
develop-2.0.0from
standards-check-update
Open

ci: fixing issues around Standards check#4097
michalChrobot wants to merge 13 commits into
develop-2.0.0from
standards-check-update

Conversation

@michalChrobot

@michalChrobot michalChrobot commented Jul 23, 2026

Copy link
Copy Markdown
Member

Purpose of this PR

This PR fixes the issues we had with standards check job which are

  1. Editor was not pinned which means whenever new version of 6000.3 got released you could get random manifest changes. I had to align this to testproject ProjectVersion so I used 6000.0.72f1 editor (this will be different for develop-3.x.x)
  2. Dotnet version may vary depending on which image was used for the job. This should be quite stable as we pin the image directly but I improved logging and pointed to this issue (so local results may not always be the same as CI due to different dotnet version)
  3. I unified the approach for package-lock.json handling with the one we have on develop-3.x.x branch (added to .gitignore and removed from test projects)
  4. I unified editors for all our test projects here (to use 6000.0.72f1 which is latest patch of the minimal supported one)

Jira ticket

N/A

Documentation

Improved job logging

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

Green standards check should be enough

Up-port

Will do

Backports

N/A

@michalChrobot michalChrobot self-assigned this Jul 23, 2026
@michalChrobot
michalChrobot marked this pull request as ready for review July 23, 2026 20:53
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.

1 participant