Skip to content

ci: use current minimum Node.js v16 version to test snapshot builds #23143

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

Merged
merged 4 commits into from
May 18, 2022

Conversation

clydin
Copy link
Member

@clydin clydin commented May 16, 2022

Node.js 16.10 is currently the minimum version of v16 supported by the Angular CLI
and is now used when executing the Angular snapshot E2E test suite to ensure
that the latest snapshots of Angular continue to function at this Node.js version.
Node.js v16 is the version currently used to develop the Angular CLI.
The npm 7+ workaround of installing npm 6 is also removed to more closely track
the behavior of Node.js 16.10 as well as any other Node.js version used during
testing.

@clydin clydin force-pushed the ci/fix-snapshots-e2e branch 4 times, most recently from 0eb694d to efda44e Compare May 16, 2022 23:10
@clydin clydin added the target: minor This PR is targeted for the next minor release label May 16, 2022
@clydin clydin changed the title ci: use current minimum Node.js version to test snapshot builds ci: use current minimum Node.js v16 version to test snapshot builds May 17, 2022
@clydin clydin force-pushed the ci/fix-snapshots-e2e branch 3 times, most recently from 5b4226c to dfff175 Compare May 17, 2022 14:33
@clydin clydin marked this pull request as ready for review May 17, 2022 16:03
clydin added 4 commits May 17, 2022 12:06
Node.js 16.10 is currently the minimum version of v16 supported by the Angular CLI
and is now used when executing the Angular snapshot E2E test suite to ensure
that the latest snapshots of Angular continue to function at this Node.js version.
Node.js v16 is the version currently used to develop the Angular CLI.
The npm 7+ workaround of installing npm 6 is also removed to more closely track
the behavior of Node.js 16.10 as well as any other Node.js version used during
testing.
…nitial version

The `misc/npm-7` E2E test previously assumed the initial version of npm was 6.x and
would then always install 6.x after the test was complete. With newer Node.js versions
this assumption is no longer true. The test now records the initial version present
prior to starting the test and restores that recorded version at completion.
@clydin clydin force-pushed the ci/fix-snapshots-e2e branch from 97adcfe to d379886 Compare May 17, 2022 16:06
@clydin clydin added the action: review The PR is still awaiting reviews from at least one requested reviewer label May 17, 2022
const { stdout: stdoutPack } = await silentNpm(
'pack',
npmSpecifier,
'--registry=https://registry.npmjs.org',
Copy link
Collaborator

Choose a reason for hiding this comment

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

--registry shouldn't be needed here.

Suggested change
'--registry=https://registry.npmjs.org',

Copy link
Collaborator

@alan-agius4 alan-agius4 left a comment

Choose a reason for hiding this comment

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

LGTM, one NIT.

@clydin clydin added action: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release and removed target: minor This PR is targeted for the next minor release action: review The PR is still awaiting reviews from at least one requested reviewer labels May 18, 2022
@clydin clydin merged commit 177fa0d into angular:main May 18, 2022
@clydin clydin deleted the ci/fix-snapshots-e2e branch May 18, 2022 13:36
@jbedard
Copy link
Contributor

jbedard commented May 18, 2022

@clydin what solved the npm 7 issue?

I'm not sure if #23115 would have changed this at all?

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants