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

Publish v1 #303

Closed
silverwind opened this issue Apr 12, 2024 · 2 comments
Closed

Publish v1 #303

silverwind opened this issue Apr 12, 2024 · 2 comments

Comments

@silverwind
Copy link

Any reason why this tool is still at v0? It's widely used so I would recommend going to v1 to show that some stability guarantees can be given.
@silverwind silverwind mentioned this issue Apr 12, 2024
Merged
@mvdan
Copy link
Owner

mvdan commented Apr 12, 2024

Maybe at some point but not right now. The CLI is mostly stable, but the Go API and the features are in flux. See for instance #78 or #2.

@mvdan mvdan closed this as not planned Won't fix, can't repro, duplicate, stale Apr 12, 2024
@silverwind
Copy link
Author

silverwind commented Apr 12, 2024 •
edited
Loading

Ok, I hope it's still a goal to have v1 eventually. I really despise software that stays at v0 forever 😆.

silverwind added a commit to go-gitea/gitea that referenced this issue Apr 12, 2024
@silverwind
Lock a few tool dependencies to major versions (#30439)
487b127 
It's better having to update these less often, so unlock a few
dependencies that I trust enough to not break to their latest major
versions. This excludes any tool still at major version 0 and
golangci-lint can't really be unlocked either because new versions
almost always break there.

For the v0 packages, I've opened
golangci/misspell#14 and
mvdan/gofumpt#303.
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
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@silverwind @mvdan