Skip to content
New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

allow explicit revision update #2143

Merged
merged 1 commit into from Jun 30, 2021
Merged

allow explicit revision update #2143

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 6 additions & 0 deletions versioning/revisions.rst
View file
Open in desktop
Expand Up @@ -40,6 +40,12 @@ with ``-u, --update`` argument to :command:`conan install` command. In the clien
The revisions can be pinned when you write a reference (in the recipe requires, a reference in a
:command:`conan install` command,…) but if you don’t specify a revision, the server will retrieve the latest revision.

If you specify a pinned revision in your references, and that revision is not the one present in the Conan cache, and ``--update``
is not provided, it will fail with an error. This behavior can be change with ``core:allow_explicit_revision_update=True``
``[conf]`` configuration. It is experimental and can result in later errors (that won't be possible to fix, use it at your own risk),
for example as the cache can only host 1 revision, it might happen that multiple pinned references are competing for it, and kicking
each others revisions out of the cache while the dependency graph is computed.

You can specify the references in the following formats:

+-----------------------------------------------+--------------------------------------------------------------------+
Expand Down