Remove version field from package.json #39
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MatteoPologruto
added
type: enhancement
umbynos
approved these changes
May 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
versionfield is only needed if the package is to be published. In this project,package.jsonis used only for management of the dependencies and scripts for internal development.For this reason, having a
versionfield in the file is harmful because it increases the effort and complexity of making a release, and also is likely to get out of sync with the true version.Reference:
https://docs.npmjs.com/cli/v8/configuring-npm/package-json#version
This was done last year for the
arduino/setup-taskaction without any ill effects: arduino/setup-task#49.The same was done for the
arduino/arduino-lint-actionaction: arduino/arduino-lint-action#69