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.

Sign up for GitHub

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

Jump to bottom

Why bump to version 5.0? Can't ask a question as discord link is broken #39

Closed
gruckionvit opened this issue Jun 9, 2021 · 2 comments
Closed

Why bump to version 5.0? Can't ask a question as discord link is broken #39

gruckionvit opened this issue Jun 9, 2021 · 2 comments

Comments

@gruckionvit
Copy link

gruckionvit commented Jun 9, 2021 •
edited

What version of this package are you using?

4.1.0

What operating system, Node.js, and npm version?

N/A

What happened?

Releases not tag properly so hard to know what's changed

620b262

This commit just shows the version bump nothing else. What gives?

What did you expect to happen?

To know why a major version bump has occured and what breaking changes this will have on my project.

Are you willing to submit a pull request to fix this bug?

No
@gruckionvit
Copy link
Author

Hi peeps, it's been many months and this PR is still queued to go in as we haven't had any clarification on why version 5 was created. @feross

@pascalwengerter pascalwengerter mentioned this issue Feb 9, 2022
Open
@voxpelli
Copy link
Member

voxpelli commented Jun 2, 2022

It was created as a way to deprecate the module without causing noise for those who were on the older version / using an older version of standard.

See: #38

@voxpelli voxpelli closed this as completed Jun 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
The Standard Project
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@voxpelli @gruckionvit