allow package projects to include themselves in the lockfile#2335
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
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.
Closes #2285.
Package projects can now request that the package itself be included in the lockfile, by setting the following in the package
DESCRIPTIONfile:When set:
renv.snapshot.ignore.selfoption, which still takes precedence when set);app.Rreferencing the package). This covers both implicit and explicit snapshot types.An explicit
Config/renv/snapshot/include-self: FALSEexcludes the package even in golem projects, which are otherwise auto-included.Also documents the
renv.snapshot.ignore.selfoption in?snapshot, along with the caveat that the package should be installed from a restorable remote source (e.g.renv::install("<user>/<repo>")) for deployment to work.