Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release: Rework versioning command #22997

Merged
merged 13 commits into from
Jun 9, 2023
Merged

Release: Rework versioning command #22997

merged 13 commits into from
Jun 9, 2023

Conversation

JReinhold
Copy link
Contributor

This PR changes the versioning release script from using a combination of @yarnpkg/plugin-version and lerna, to manually updating versions and dependencies in all package.json's.

The plugin was causing OOM errors in Windows unit tests, and lerna wasn't actually necessary.
This solution is a bit simpler conceptually, although the code is a bit more complex.

What I did

How to test

Checklist

  • Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
  • Make sure to add/update documentation regarding your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Maintainers

  • If this PR should be tested against many or all sandboxes,
    make sure to add the ci:merged or ci:daily GH label to it.
  • Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

@JReinhold JReinhold requested a review from a team as a code owner June 9, 2023 08:08
@JReinhold JReinhold changed the title Release: rework versioning command Release: Rework versioning command Jun 9, 2023
@JReinhold JReinhold added the build Internal-facing build tooling & test updates label Jun 9, 2023
Copy link
Contributor

@kasperpeulen kasperpeulen left a comment

Choose a reason for hiding this comment

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

Really nice stuff!

Comment on lines +26 to +28
jest.spyOn(console, 'log').mockImplementation(() => {});
jest.spyOn(console, 'warn').mockImplementation(() => {});
jest.spyOn(console, 'error').mockImplementation(() => {});
Copy link
Contributor

Choose a reason for hiding this comment

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

.mockImplementation() will do the same, as it uses a void function as default

@JReinhold JReinhold merged commit ade5322 into next Jun 9, 2023
@JReinhold JReinhold deleted the fix-release-publish branch June 9, 2023 10:51
kasperpeulen pushed a commit that referenced this pull request Jun 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Internal-facing build tooling & test updates
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants