Skip to content

build: remove engines field from package.json #28853

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 1 commit into from
Apr 10, 2024

Conversation

crisbeto
Copy link
Member

As discussed, these changes remove the engines enforcement since it can be annoying given that our project isn't sensitive to Node version changes.

As discussed, these changes remove the `engines` enforcement since it can be annoying given that our project isn't sensitive to Node version changes.
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Apr 10, 2024
@angular-robot angular-robot bot added the area: build & ci Related the build and CI infrastructure of the project label Apr 10, 2024
Copy link
Contributor

@wagnermaciel wagnermaciel left a comment

Choose a reason for hiding this comment

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

🙌

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Apr 10, 2024
@crisbeto crisbeto merged commit 8340e62 into angular:main Apr 10, 2024
crisbeto added a commit that referenced this pull request Apr 10, 2024
As discussed, these changes remove the `engines` enforcement since it can be annoying given that our project isn't sensitive to Node version changes.

(cherry picked from commit 8340e62)
@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 May 11, 2024
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 area: build & ci Related the build and CI infrastructure of the project target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants