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

[pull] main from gruntjs:main #1

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

[pull] main from gruntjs:main #1

wants to merge 2 commits into from

Conversation

pull[bot]
Copy link

@pull pull bot commented Jul 25, 2024

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

Krinkle and others added 2 commits July 20, 2024 20:48
* grunt-cli updated to nopt 4.x in gruntjs/grunt-cli#117
* grunt-cli updated to nopt 5.0 in gruntjs/grunt-cli#156
* changelog: https://github.com/npm/nopt/blob/v5.0.0/CHANGELOG.md

The simple usage of `nopt(known, alias, argv, 2)` has remained
unchanged through both changes, same as in this repo.

Installation of latest grunt- produces a warning:

> npm WARN deprecated [email protected]: This package is no longer supported.

This package was used by nopt to call `os.homedir()` which has been built-in
since Node.js 2. The dependency was removed in nopt 5.0.0 with
npm/nopt@5c0e45b.

Newer versions of nopt are available, but those raise the required
Node.js engine level. In order to make this safe to land, and easy to release,
resolve the warning first by moving to nopt 5.0.0, matching grunt-cli.

I'm loosening grunt-cli to allow for grunt-cli 1.5.0, which was just
released with a similar fix. This way it will update by default, but
not cause duplicate installations for downstream projects that depend
on grunt-cli 1.4 directly.
Update from nopt 3.x to nopt 5.0.0
Copy link

changeset-bot bot commented Jul 25, 2024

⚠️ No Changeset found

Latest commit: e2edc00

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

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