Pin @unlayer/types instead of using latest tag#481
Open
farhan523 wants to merge 1 commit into
Open
Conversation
Using the "latest" tag makes builds unreproducible: the resolved version can change at any time without notice, and a bad upstream publish breaks consumers' installs. Fixes unlayer#469
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Fixes #469.
package.jsoncurrently depends on@unlayer/types: "latest", which makes builds unreproducible — the resolved version can change at any time without notice, and a bad upstream publish immediately breaks consumers' installs (as reported in #469).This pins the dependency to
^1.448.0(the current release) and updates the lockfile accordingly.Testing
tsdx build— compiles cleanly against@unlayer/types@1.448.0tsdx test— passes