Skip to content

--lts returns no version #17

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

Closed
RedGlow opened this issue Dec 15, 2024 · 2 comments
Closed

--lts returns no version #17

RedGlow opened this issue Dec 15, 2024 · 2 comments
Assignees
Labels
bug Something isn't working released

Comments

@RedGlow
Copy link

RedGlow commented Dec 15, 2024

Describe the bug
Latest (2.3.0) version of unity-changeset, used as a command line, returns nothing with the --lts flag.

To Reproduce
Steps to reproduce the behavior:

  1. Run the command:
npx unity-changeset@2.3.0 list --lts
  1. The command outputs nothing.

Expected behavior
It should output all the LTS versions.

Environment:

  • OS: Windows 11
  • Node: 20.10.0
  • Npm: 9.2.0
  • Version: 2.3.0

Additional context
Running the same command without the --lts flag correctly prints all the versions:

> npx unity-changeset@2.3.0 list
6000.0.31f1     a206c360e2a8
6000.0.30f1     62b05ba0686a
6000.0.29f1     9fafe5c9db65
6000.0.28f1     f336aca0cab5
6000.0.27f1     27c554a2199c
6000.0.26f1     ccb7c73d2c02
6000.0.25f1     4859ab7b5a49
6000.0.24f1     11fa355cd605
6000.0.23f1     1c4764c07fb4
...
@RedGlow RedGlow added the bug Something isn't working label Dec 15, 2024
@mob-sakai
Copy link
Owner

Thank you for your reporting!

@mob-sakai
Copy link
Owner

🎉 This issue has been resolved in version 2.3.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working released
Projects
None yet
Development

No branches or pull requests

2 participants