Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

npm-published packages should follow semver #61

Open
cwillisf opened this issue May 14, 2021 · 0 comments
Open

npm-published packages should follow semver #61

cwillisf opened this issue May 14, 2021 · 0 comments
Labels
developer facing tech debt

Comments

@cwillisf
Copy link
Contributor

Expected Behavior

Scratch projects published to npm should use semver version numbers >= 1.0 so that dependents can control when to accept breaking changes.

Actual Behavior

This repository uses "prerelease" version numbers like 0.1.0-prerelease.YYYYMMDDhhmmss which contain no information about breaking changes.
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
developer facing tech debt
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@BryceLTaylor @cwillisf