Closed
Bug 670619
Opened 14 years ago
Closed 14 years ago
Update jetpack hashes in the amo-validator
Categories
(addons.mozilla.org Graveyard :: Code Quality, defect)
addons.mozilla.org Graveyard
Code Quality
Tracking
(Not tracked)
RESOLVED
FIXED
Q3 2011
People
(Reporter: clouserw, Unassigned)
Details
Made a pull request here with some open questions: https://github.com/mattbasta/amo-validator/pull/21
r? basta
Comment 1•14 years ago
|
||
This is updated. Not sure I want to link to the commit(s) because of their sheer ugliness, but it's there. Promise.
Also, open questions in the pull were answered via comment.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 2•14 years ago
|
||
So the 10000 line file has hashes for every file for every tag? or for the latest tag? or?
Comment 3•14 years ago
|
||
It's all of the unique hashes for every file for every tag. If there are two of the same hashes, the earlier version number is saved. This is semi-useful because if a Jetpack add-on says that it uses version 1.0, all of the hash values should be <= v1.0.
| Assignee | ||
Updated•10 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•