Skip to content

chore(main): release 18.0.0#2325

Merged
bcoe merged 1 commit intomainfrom
release-please--branches--main--components--yargs
May 27, 2025
Merged

chore(main): release 18.0.0#2325
bcoe merged 1 commit intomainfrom
release-please--branches--main--components--yargs

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot commented Apr 28, 2023 •
edited
Loading

🤖 I have created a release beep boop

18.0.0 (2025-05-26)

⚠ BREAKING CHANGES

  • command names are not derived from modules passed to command.
  • singleton usage of yargs yargs.foo, yargs().argv, has been removed.
  • minimum node.js versions now ^20.19.0 || ^22.12.0 || >=23.
  • yargs is now ESM first

Features

Bug Fixes

  • addDirectory do not support absolute command dir (#2465) (3a40a78)
  • allows ESM modules commands to be extensible using visit option (#2468) (200e1aa)
  • browser: fix shims so that yargs continues working in browser context (#2457) (4ae5f57)
  • build: address problems with typescript compilation (#2445) (8d72fb3)
  • coerce should play well with parser configuration (#2308) (8343c66)
  • deps: update dependency yargs-parser to v22 (#2470) (639130d)
  • exit after async handler done (#2313) (e326cde)
  • handle spaces in bash completion (#2452) (83b7788)
  • parser-configuration should work well with generated completion script (#2332) (888db19)
  • propagate Dictionary including undefined in value type (#2393) (2b2f7f5)
  • zsh: completion no longer requires double tab when using autoloaded (0dd8fe4)

Code Refactoring

  • command names are not derived from modules passed to command. (d90af45)
  • singleton usage of yargs yargs.foo, yargs().argv, has been removed. (d90af45)

Build System

  • minimum node.js versions now ^20.19.0 || ^22.12.0 || >=23. (d90af45)

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--yargs branch 2 times, most recently from b38e541 to 1395336 Compare April 28, 2023 17:56
@bcoe bcoe added the ci label Apr 28, 2023
@github-actions github-actions bot force-pushed the release-please--branches--main--components--yargs branch from 1b2fec6 to 03f802c Compare May 1, 2023 15:10
@github-actions github-actions bot changed the title chore(main): release 17.7.3 chore(main): release 18.0.0 Jan 4, 2024
@github-actions github-actions bot force-pushed the release-please--branches--main--components--yargs branch from 03f802c to 604acdc Compare January 4, 2024 15:59
@bcoe bcoe added ci and removed ci labels Jan 4, 2024
@github-actions github-actions bot force-pushed the release-please--branches--main--components--yargs branch 2 times, most recently from 46c24af to 3b45e4f Compare January 5, 2024 16:24
@github-actions github-actions bot force-pushed the release-please--branches--main--components--yargs branch 3 times, most recently from f8f57d1 to 3341e05 Compare January 3, 2025 14:59
@github-actions github-actions bot force-pushed the release-please--branches--main--components--yargs branch 3 times, most recently from e39ca2a to badc1cf Compare April 9, 2025 15:54
@bcoe bcoe added ci and removed ci labels Apr 9, 2025
@bcoe
Copy link
Copy Markdown
Member

bcoe commented Apr 9, 2025

Candidate version installed to npm i yargs@18.0.0-candidate.1 try it out.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--yargs branch 2 times, most recently from 637916e to 22d6b95 Compare April 11, 2025 18:56
@bcoe
Copy link
Copy Markdown
Member

bcoe commented Apr 11, 2025

Latest beta build + yargs@18.0.0-candidate.3.

bcoe
bcoe requested changes Apr 15, 2025
View reviewed changes
Copy link
Copy Markdown
Member

@bcoe bcoe left a comment

Choose a reason for hiding this comment

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

I'm thinking, wait until some time after April 19th when Node 18 goes EOL.

@shadowspawn
Copy link
Copy Markdown
Member

shadowspawn commented Apr 16, 2025

Are you planning any other announcement about prerelease available now? I was thinking I could create and pin an issue pointing here for further details and promoting npm install yargs@next?

@bcoe
Copy link
Copy Markdown
Member

bcoe commented Apr 16, 2025 •
edited
Loading

Are you planning any other announcement about prerelease available now?

That's a good idea.

I was thinking I could create and pin an issue pointing here for further details and promoting npm install yargs@next?

Yes, please do 👏

Perhaps we wait longer than April 19th 30th, to give folks a chance to see this. My concern is less the Node 18 EOL, and more the fact that our version range asks for specific versions of 20 and 22.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--yargs branch from 22d6b95 to 76ba2ad Compare April 16, 2025 13:39
@shadowspawn
Copy link
Copy Markdown
Member

shadowspawn commented Apr 18, 2025 •
edited
Loading

(Not the critical date but to clarify, Node 18 goes EOL on 2025-04-30 according to https://github.com/nodejs/release#release-schedule)

@shadowspawn shadowspawn mentioned this pull request Apr 18, 2025
Closed
@github-actions github-actions bot force-pushed the release-please--branches--main--components--yargs branch 6 times, most recently from 6d9eb9d to dcbecc5 Compare April 25, 2025 20:43
@github-actions github-actions bot force-pushed the release-please--branches--main--components--yargs branch from dcbecc5 to ebde0f5 Compare May 6, 2025 12:45
@github-actions github-actions bot force-pushed the release-please--branches--main--components--yargs branch from ebde0f5 to a855e7b Compare May 26, 2025 20:40
@bcoe bcoe added ci and removed ci labels May 26, 2025
@bcoe
Copy link
Copy Markdown
Member

bcoe commented May 26, 2025

@shadowspawn are there any other changes you'd like to land on upstream libraries before we ship this? I'm feeling like it's time to land this?

@shadowspawn
Copy link
Copy Markdown
Member

shadowspawn commented May 27, 2025

Nothing I want to land first, thanks. Node 18 is EOL, yargs prereleases have been available for a while, no reason to wait longer.

:shipit: ( <-- I had to look up what this was for. 😄 )

bcoe
bcoe approved these changes May 27, 2025
View reviewed changes
Copy link
Copy Markdown
Member

@bcoe bcoe left a comment

Choose a reason for hiding this comment

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

:shipit:

@bcoe bcoe merged commit 0bc7255 into main May 27, 2025
6 checks passed
@bcoe bcoe deleted the release-please--branches--main--components--yargs branch May 27, 2025 14:26
@github-actions
Copy link
Copy Markdown
Contributor Author

github-actions bot commented May 27, 2025

🤖 Release is at https://github.com/yargs/yargs/releases/tag/v18.0.0 🌻

@michaelfaith michaelfaith mentioned this pull request Jan 3, 2026
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@bcoe bcoe bcoe approved these changes

Assignees

No one assigned

Labels

autorelease: tagged ci

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@bcoe @shadowspawn