feat: improve version detection #41
Merged
Conversation
This file contains 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
nhedger
force-pushed
the
nhedger/feat/improve-version-detection
branch
from
1324201
to
49c9587
Compare
nhedger
changed the title
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.
This PR introduces improvements to the automatic version detection strategy.
The action will now fall back to
package.jsonfor detecting the version if there are no lock files or if the lock file cannot be parsed (e.g., bun's binarybun.lockbfile).When reading the version from
package.json, and if the version is specified as a semver range, the action will resolve it to the highest version within that range.Here's a flow diagram that explains how the resolution works.
Closes #40