1. 01 Nov, 2019 2 commits
  2. 30 Oct, 2019 3 commits
  3. 29 Oct, 2019 3 commits
  4. 25 Oct, 2019 10 commits
  5. 24 Oct, 2019 5 commits
  6. 22 Oct, 2019 1 commit
  7. 19 Oct, 2019 1 commit
  8. 18 Oct, 2019 6 commits
  9. 14 Oct, 2019 2 commits
  10. 13 Oct, 2019 1 commit
  11. 12 Oct, 2019 3 commits
  12. 11 Oct, 2019 3 commits
    • Improve files metadata in lock files (#1460) · b1c4c68d
      Co-authored-by: adisbladis <adisbladis@gmail.com>
      Sébastien Eustace committed
    • Resolve git refs to git revisions [#1331] (#1337) · 72806dd4
      * Check that a git dependency resolves to a revision
      
      A git dependency should be resolved to a full git revision (SHA-1).
      When dealing with a git dependency, this is the only way to lock
      the dependency in-place (because revisions are immutable).
      
      * Check that a pinned git dependency resolves to a revision
      
      There are three mutually exclusive parameters that can be used to
      pin a git dependency: `branch`, `tag`, and `rev`.  Since they all
      can be moving targets, they should be resolved to a full git
      revision (SHA-1) to ensure a proper in-place lock.
      
      This change highlights bug #1331 and currently fails.
      
      * Make sure a git reference resolves to a revision
      
      Do not lock a git dependency to a named reference but to a full
      git revision instead.  This ensures reproducibility and security
      as git revisions are immutable.
      
      Fixes: #1331
      Borjan Tchakaloff committed