Skip to content

Conversation

EmandM
Copy link
Collaborator

@EmandM EmandM commented Sep 15, 2025

Purpose of this PR

Remove the broken check in package-pack and vetting-test

Jira ticket

n/a

Documentation

  • No documentation changes or additions were necessary.

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

Functional Testing

Manual testing :

  • Manual testing done

Automated tests:

  • Covered by existing automated tests
  • Covered by new automated tests

Does the change require QA team to:

  • Review automated tests?
  • Execute manual tests?
  • Provide feedback about the PR?

If any boxes above are checked the QA team will be automatically added as a PR reviewer.

Backports

Backported in #3678

@EmandM EmandM requested review from NoelStephensUnity and a team as code owners September 15, 2025 21:12
@EmandM EmandM mentioned this pull request Sep 15, 2025
6 tasks
Copy link
Collaborator

@NoelStephensUnity NoelStephensUnity left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🐎

EmandM added a commit that referenced this pull request Sep 15, 2025
## Purpose of this PR

Remove the broken check in package-pack and vetting-test

## Backports

Backported by #3677
@EmandM EmandM merged commit 2275c2f into develop-2.0.0 Sep 15, 2025
12 checks passed
@EmandM EmandM deleted the fix/remove-release-py-from-pvp-checks branch September 15, 2025 21:17
michalChrobot added a commit that referenced this pull request Sep 17, 2025
## Purpose of this PR
This PR follows on
#3677
because even though we don't need to execute release.py when packing the
package (due to existing pvp exception) nor vetting test job (uses
upm-ci which does not run PVP checks) we should future proof release.py
and similar scripts from making this mistake.

The main reason why the release.py was causing the package pack to fail
on windows is that when you open a file in text mode ('w') on Windows,
Python's default behavior is to convert each newline character (\n) into
the platform's standard line separator, which is \r\n (CRLF). This can
cause inconsistencies when the file is used in environments that expect
\n (LF), such as Git.

The solution was to ensure that we are specifying the newline like
`with open(path, 'w', encoding='UTF-8', newline='\n') as file:`

### Jira ticket
N/A

## Documentation
N/A

## Testing & QA (How your changes can be verified during release
Playtest)
PR trigger check was green and I verified that when release.py command
was included in pack job the results were green (see
**[THIS](https://unity-ci.cds.internal.unity3d.com/job/56280166)** job)

## Backports
Backport to `develop` branch in
#3681
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