-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Comparing changes
Open a pull request
base repository: tink-crypto/tink
base: v1.2.1
head repository: tink-crypto/tink
compare: v1.2.2
- 12 commits
- 21 files changed
- 4 contributors
Commits on Jan 18, 2019
-
PiperOrigin-RevId: 221460179 GitOrigin-RevId: 0b64b34572e19a62458b323642e624dae6e53fff (cherry picked from commit c0223fb)
Configuration menu - View commit details
-
Copy full SHA for e87615a - Browse repository at this point
Copy the full SHA e87615aView commit details -
Add missing ABSL build dependencies to tink
PiperOrigin-RevId: 221498755 GitOrigin-RevId: 0de9d8cd8e5eb2bef7aecf72ec57d2e1198b4edb (cherry picked from commit 63ab7c4)
Configuration menu - View commit details
-
Copy full SHA for ca930d3 - Browse repository at this point
Copy the full SHA ca930d3View commit details -
Making the build work with Bazel >= 0.20.0.
PiperOrigin-RevId: 223663565 GitOrigin-RevId: 0fdf549d913bf6ca4e4c84e046280a98a2a18a42 (cherry picked from commit d5f7514)
Configuration menu - View commit details
-
Copy full SHA for 8cdb052 - Browse repository at this point
Copy the full SHA 8cdb052View commit details -
Update the javalite proto archive.
The javalite archive was updated on December 19: https://github.com/protocolbuffers/protobuf/commits/javalite This means that the branch given by javalite.zip updates, so the hash changes. In principle, I would like to be able to check on my corp machine that this changes are exactly what I now have in the new machine. Unfortunately, I don't know how to download the previous archive with the sha256 hash to create a diff. In order to make sure this works in the future, I suggest we download the archive by commit. For this, if you continue from the above link to the topmost commit, you get that the id of the link is 384...16 -- we copy this as the url and then we can get the corresponding sha256 sum on the local machine. If the branch updates, we need to manually update it. The disadvantage is that we don't get cherry picks automatically. This fixes issue 166. PiperOrigin-RevId: 227678791 GitOrigin-RevId: cceb31b558c4fa9ca7613287cd69a8bad5f60798 (cherry picked from commit cd94de6)
Configuration menu - View commit details
-
Copy full SHA for 2deb7ff - Browse repository at this point
Copy the full SHA 2deb7ffView commit details -
Update protobuf library to v.3.6.1.2.
This is required to make the build work with the newest bazel binary. See protocolbuffers/protobuf#5418 PiperOrigin-RevId: 227681358 GitOrigin-RevId: 1df09b7dbe849a527f2da882e96483f3e967a26b (cherry picked from commit dc53e5e)
Configuration menu - View commit details
-
Copy full SHA for d57a415 - Browse repository at this point
Copy the full SHA d57a415View commit details -
Use the KeyFactory from the same provider as the KeyAgreement.
PiperOrigin-RevId: 229476935 GitOrigin-RevId: dad4536a60155fa36a98e7bfc398384daae56694 (cherry picked from commit 5e0aabf)
Configuration menu - View commit details
-
Copy full SHA for 59943c6 - Browse repository at this point
Copy the full SHA 59943c6View commit details
Commits on Jan 19, 2019
-
Configuration menu - View commit details
-
Copy full SHA for df98956 - Browse repository at this point
Copy the full SHA df98956View commit details -
Update to the newest version of googletest to enable cl/229243192.
PiperOrigin-RevId: 229349991 GitOrigin-RevId: 2aa804f1e5d093cb633864b7228c56918931eb21 (cherry picked from commit edc4dbc)
Configuration menu - View commit details
-
Copy full SHA for e32864b - Browse repository at this point
Copy the full SHA e32864bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 4c48663 - Browse repository at this point
Copy the full SHA 4c48663View commit details -
Upgrade absl to the newest version
PiperOrigin-RevId: 218484337 GitOrigin-RevId: 255faba2d79cea1f16d3f0e57e4aeac02644172f (cherry picked from commit b3b26b7)
Configuration menu - View commit details
-
Copy full SHA for 42ca576 - Browse repository at this point
Copy the full SHA 42ca576View commit details
Commits on Jan 22, 2019
-
Undo a change I mistakenly introduced in cl/227678791.
PiperOrigin-RevId: 228127467 GitOrigin-RevId: 7f5b5d4ca8ce8bfea88bf5bfd39712717c52df9f (cherry picked from commit 5c2ad63)
Configuration menu - View commit details
-
Copy full SHA for de56db8 - Browse repository at this point
Copy the full SHA de56db8View commit details
Commits on Jan 24, 2019
-
Bumping version number to 1.2.2.
PiperOrigin-RevId: 230785575 GitOrigin-RevId: b9a858a2c74ef3d7a5e9d6adca72d4b02b6ff621 (cherry picked from commit 621b573)
Configuration menu - View commit details
-
Copy full SHA for 6f073f1 - Browse repository at this point
Copy the full SHA 6f073f1View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.2.1...v1.2.2