)]}' { "log": [ { "commit": "3465e7748ad69c6c818a14c3716ce4c9904cc23d", "tree": "399c0af657ea5ffbad21945f8ae189bc9a0c429b", "parents": [ "d6cdfa7432d9b8035147d114c33c023982e3a91b" ], "author": { "name": "Adrià Vilanova Martínez", "email": "me@avm99963.com", "time": "Sun Jul 11 19:18:41 2021 +0200" }, "committer": { "name": "Adrià Vilanova Martínez", "email": "me@avm99963.com", "time": "Sun Jul 11 21:15:43 2021 +0200" }, "message": "Refactor extension to webpack\n\nThis change is the biggest in the history of the project. The entire\nproject has been refactored so it is built with webpack.\n\nThis involves:\n- Creating webpack and npm config files.\n- Fixing some bugs in the code due to the fact that webpack uses strict\nmode.\n- Merging some pieces of code which were shared throughout the codebase\n(not exhaustive, more work should be done in this direction).\n- Splitting the console_inject.js file into separate files (it had 1000+\nlines).\n- Adapting all the build-related files (Makefile, bash scripts, etc.)\n- Changing the docs to explain the new build process.\n- Changing the Zuul playbook/roles to adapt to the new build process.\n\nChange-Id: I16476d47825461c3a318b3f1a1eddb06b2df2e89\n" }, { "commit": "bbc88c6c70a84555460fd8dff88eb4b24fb43bef", "tree": "93bc8d78d7bb74e1c118baa38a75b1c299bbf66a", "parents": [ "0991c69b3300b7c1e4b833bbb226f37bac7094c2" ], "author": { "name": "avm99963", "email": "me@avm99963.com", "time": "Fri Dec 25 03:44:41 2020 +0100" }, "committer": { "name": "avm99963", "email": "me@avm99963.com", "time": "Sun Dec 27 11:42:23 2020 +0100" }, "message": "Add support for Manifest V3\n\nManifest V3 (MV3) is a new version of the manifest.json file, which also\ncomes with several API changes:\nhttps://developer.chrome.com/docs/extensions/mv3/intro/\n\nTherefore, this change does the following:\n\n- Add a new target to the Makefile and release.bash scripts called\n \"chromium-mv3-beta\"/\"CHROMIUM_MV3\" which target Chromium using\n Manifest V3.\n- Adapt the manifest.gjson template so it is compatible with Manifest\n V3 when the target is \"CHROMIUM_MV3\".\n- Adapt the source code (change the background page to a service\n worker and change chrome.browserAction.* to chrome.action.*).\n\nAlso, the following change has been done:\n\n- The \"gecko-beta\" target in the Makefile has been removed because in\n the end we never released beta versions for Firefox, due to the small\n user base there.\n\nChange-Id: Ibedcd6651cd23aa3db359a1ef7c7b96a232f39a7\n" }, { "commit": "6c35730cb602a828e5e11a625e1c1f13ce9383b1", "tree": "3c112a1b397d660f4f6d682b27bd52d3078fbb7a", "parents": [ "8b8d1de2862d1452024e720c8518ba71e699d917" ], "author": { "name": "avm99963", "email": "me@avm99963.com", "time": "Sun Aug 09 19:54:08 2020 +0200" }, "committer": { "name": "avm99963", "email": "me@avm99963.com", "time": "Sun Aug 09 20:06:51 2020 +0200" }, "message": "Add Firefox support\n\nThe release.bash script has been updated, and now depends on a helper\nscript called generateManifest.bash. A \"--browser\" flag (shorthand \"-b\")\nhas been added to the script in order to specify the target browser.\n\nNow the manifest.json file is saved as a template at\ntemplates/manifest.gjson (gjson stands for Generic JSON), which includes\nconditional clauses which indicate what parts of the manifest are\napplicable to each browser.\n\ngenerateManifest.bash generates the src/manifest.json file.\n\nChange-Id: Ib051f3d893045c1377007b9b076ffa7a702d9648\n" } ] }