{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":519117397,"defaultBranch":"main","name":"assemblyscript","ownerLogin":"CountBleck","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2022-07-29T07:12:40.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/79281724?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1712114398.0","currentOid":""},"activityList":{"items":[{"before":"d3b06586e7e22284c7c1cd8667d2868024731d28","after":"61200f6a2e70810cdd202a3935771b7cd23ff001","ref":"refs/heads/side-effectful-compound","pushedAt":"2024-06-01T20:03:39.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Refactor assignments, property accesses, and element accesses\n\nThis commit allows the aforementioned to be compiled with precompiled\noperands, which will allow, in the next commit, unary and binary\nexpressions to avoid compiling the same this expression and element\nexpression (if any) twice (which duplicates side effects).","shortMessageHtmlLink":"Refactor assignments, property accesses, and element accesses"}},{"before":"6f6305a2cc9a7ddb29b6d791b988dca4addf3b00","after":"d3b06586e7e22284c7c1cd8667d2868024731d28","ref":"refs/heads/side-effectful-compound","pushedAt":"2024-06-01T20:03:18.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Refactor assignments, property accesses, and element accesses\n\nThis commit allows the aforementioned to be compiled with precompiled\noperands, which will allow, in the next commit, unary and binary\nexpressions to avoid compiling the same this expression and element\nexpression (if any) twice (which duplicates side effects).","shortMessageHtmlLink":"Refactor assignments, property accesses, and element accesses"}},{"before":"f0cd0da093a1dc4d4186c91fa37e4f5552930267","after":"5abcad823bdecf49e75efdeac2d4983f65de0edd","ref":"refs/heads/interface-multiple-extension","pushedAt":"2024-06-01T20:00:45.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Add a proper test for multiple interfaces\n\nWithout inspecting the resulting WAT, and instead concluding based on\nthe test compiling successfully and executing without any errors,\neverything seems to work properly.","shortMessageHtmlLink":"Add a proper test for multiple interfaces"}},{"before":"52fe306fbbde71edb0de6eddc261a88cf66b15b6","after":null,"ref":"refs/heads/empty","pushedAt":"2024-04-03T03:19:58.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"}},{"before":null,"after":"52fe306fbbde71edb0de6eddc261a88cf66b15b6","ref":"refs/heads/empty","pushedAt":"2024-04-03T02:39:17.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"fix: ignore this\n\nThis is a dummy commit to create a new release.","shortMessageHtmlLink":"fix: ignore this"}},{"before":"4465767b920eb6a14f36125382e5c853b3015bc3","after":"163a6312169af561c225258728a98af8a7d98964","ref":"refs/heads/fix-large-memory-crash","pushedAt":"2024-04-03T01:47:10.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"BREAKING CHANGE: Do not allocate buffers for memory.data(i32, i32?)\n\nMemorySegments can now hold null buffers, which signifies that memory is\nin fact used in the compiled program, for programs that only reserve\nzero-filled memories. Using null buffers avoids passing zero-filled\nbuffers to Binaryen, which isn't necessary since Wasm memories are\ninitialized with zeroes when a (data ...) segment isn't present.\n\nThis change is breaking in that modules using imported memories that\ncontain non-zero values in such memory ranges at the time of\ninstantiation will retain those values, as opposed to being filled.\nThis shouldn't affect most users, however, and it could possibly be\ndesirable.\n\nFixes #2827.","shortMessageHtmlLink":"BREAKING CHANGE: Do not allocate buffers for memory.data(i32, i32?)"}},{"before":"ed50aef9cb8632482fa99edd4e6ddfba8ee860c2","after":"4465767b920eb6a14f36125382e5c853b3015bc3","ref":"refs/heads/fix-large-memory-crash","pushedAt":"2024-04-03T01:46:17.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"BREAKING CHANGE: Do not allocate buffers for memory.data(i32, i32?)\n\nMemorySegments can now hold null buffers, which signifies that memory is\nin fact used in the compiled program, for programs that only reserve\nzero-filled memories. Using null buffers avoids passing zero-filled\nbuffers to Binaryen, which isn't necessary since Wasm memories are\ninitialized with zeroes when a (data ...) segment isn't present.\n\nThis change is breaking in that modules using imported memories that\ncontain non-zero values in such memory ranges at the time of\ninstantiation will retain those values, as opposed to being filled.\nThis shouldn't affect most users, however.\n\nFixes #2827.","shortMessageHtmlLink":"BREAKING CHANGE: Do not allocate buffers for memory.data(i32, i32?)"}},{"before":"559814d80b1c474168415945326e474449bcd47f","after":"ed50aef9cb8632482fa99edd4e6ddfba8ee860c2","ref":"refs/heads/fix-large-memory-crash","pushedAt":"2024-04-03T01:45:25.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"BREAKING CHANGE: Do not allocate buffers for memory.data(i32, i32?)\n\nMemorySegments can now hold null buffers, which signifies that memory is\nin fact used in the compiled program, for programs that only reserve\nzero-filled memories. Using null buffers avoids passing zero-filled\nbuffers to Binaryen, which isn't necessary since Wasm memories are\ninitialized with zeroes when a (data ...) segment isn't present.\n\nThis change is breaking in that modules using imported memories that\ncontain non-zero values in such memory ranges at the time of\ninstantiation will retain those values, as opposed to being filled.\n\nFixes #2827.","shortMessageHtmlLink":"BREAKING CHANGE: Do not allocate buffers for memory.data(i32, i32?)"}},{"before":"6a89a09eff0a8088811fdbc6a0e0aed8510a1557","after":"559814d80b1c474168415945326e474449bcd47f","ref":"refs/heads/fix-large-memory-crash","pushedAt":"2024-04-03T01:39:09.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"fix: Do not allocate buffers for memory.data(i32, i32?)\n\nMemorySegments can now hold null buffers, which signifies that memory is\nin fact used in the compiled program, for programs that only reserve\nzero-filled memories. Using null buffers avoids passing zero-filled\nbuffers to Binaryen, which isn't necessary since Wasm memories are\ninitialized with zeroes when a (data ...) segment isn't present.\n\nFixes #2827.","shortMessageHtmlLink":"fix: Do not allocate buffers for memory.data(i32, i32?)"}},{"before":"373166cb698c97a5560ab38bab0e9b9307f6b3b6","after":"6a89a09eff0a8088811fdbc6a0e0aed8510a1557","ref":"refs/heads/fix-large-memory-crash","pushedAt":"2024-03-25T01:49:28.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Do not allocate buffers for memory.data(i32, i32?)\n\nMemorySegments can now hold null buffers, which signifies that memory is\nin fact used in the compiled program, for programs that only reserve\nzero-filled memories. Using null buffers avoids passing zero-filled\nbuffers to Binaryen, which isn't necessary since Wasm memories are\ninitialized with zeroes when a (data ...) segment isn't present.\n\nFixes #2827.","shortMessageHtmlLink":"Do not allocate buffers for memory.data(i32, i32?)"}},{"before":null,"after":"373166cb698c97a5560ab38bab0e9b9307f6b3b6","ref":"refs/heads/fix-large-memory-crash","pushedAt":"2024-03-25T00:00:17.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Do not allocate MemorySegments for memory.data(i32, i32?)\n\nInstead of allocating a MemorySegment, the code now simply bumps the\nCompiler's memoryOffset.\n\nFixes #2827.","shortMessageHtmlLink":"Do not allocate MemorySegments for memory.data(i32, i32?)"}},{"before":null,"after":"d59621564d1cc617c89c59e6b231a3df16595c2e","ref":"refs/heads/fix-transform-types","pushedAt":"2024-03-24T15:54:13.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Fix .d.ts type for Transform#afterCompile","shortMessageHtmlLink":"Fix .d.ts type for Transform#afterCompile"}},{"before":"8b0b49840d4f04f3d17a07038ad16a0f096e463d","after":"b7afa67acf85c47967b43d37ad6073e72a4e8314","ref":"refs/heads/fix-2825","pushedAt":"2024-03-12T03:55:37.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Compile incrementors in for loops within the initializer's flow\n\nIt turns out that incrementors were compiled with the body's flow, which\nmeant that the incrementor had access to local variables declared in the\nbody. Now, incrementors no longer have access to such variables.\n\nFixes #2825.","shortMessageHtmlLink":"Compile incrementors in for loops within the initializer's flow"}},{"before":"550bbf5486724363dbb903f84930fc2012469998","after":"8b0b49840d4f04f3d17a07038ad16a0f096e463d","ref":"refs/heads/fix-2825","pushedAt":"2024-03-12T00:28:20.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Compile incrementors in for loops within the initializer's flow\n\nIt turns out that incrementors were compiled with the body's flow, which\nmeant that the incrementor had access to local variables declared in the\nbody. Now, incrementors no longer have access to such variables.\n\nFixes #2825.","shortMessageHtmlLink":"Compile incrementors in for loops within the initializer's flow"}},{"before":"6293b10244639008cc8b5c83c591ebafff7318a9","after":"550bbf5486724363dbb903f84930fc2012469998","ref":"refs/heads/fix-2825","pushedAt":"2024-03-10T02:30:51.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Compile incrementors in for loops within the initializer's flow\n\nIt turns out that incrementors were compiled with the body's flow, which\nmeant that the incrementor had access to local variables declared in the\nbody. Now, incrementors no longer have access to such variables.\n\nFixes #2825.","shortMessageHtmlLink":"Compile incrementors in for loops within the initializer's flow"}},{"before":"fa1323c509aac6eb39186924790f332fef868199","after":"6293b10244639008cc8b5c83c591ebafff7318a9","ref":"refs/heads/fix-2825","pushedAt":"2024-03-10T02:30:21.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Compile incrementors within the initializer's flow in for loops\n\nIt turns out that incrementors were compiled with the body's flow, which\nmeant that the incrementor had access to local variables declared in the\nbody. Now, incrementors no longer have access to such variables.\n\nFixes #2825.","shortMessageHtmlLink":"Compile incrementors within the initializer's flow in for loops"}},{"before":null,"after":"fa1323c509aac6eb39186924790f332fef868199","ref":"refs/heads/fix-2825","pushedAt":"2024-03-10T02:25:40.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Compile incrementors within the initializer's flow in for loops\n\nIt turns out that incrementors were compiled with the body's flow, which\nmeant that the incrementor had access to local variables declared in the\nbody. Now, code like this should no longer compile:\n\nfor (let i = 0; i < 2; j++) { let j = 0; }\n\nFixes #2825.","shortMessageHtmlLink":"Compile incrementors within the initializer's flow in for loops"}},{"before":"94a2c28d5efe177538bd04f28ebaba57eb92118c","after":"f0cd0da093a1dc4d4186c91fa37e4f5552930267","ref":"refs/heads/interface-multiple-extension","pushedAt":"2024-01-15T05:03:09.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Add a proper test for multiple interfaces\n\nWithout inspecting the resulting WAT, and instead concluding based on\nthe test compiling successfully and executing without any errors,\neverything seems to work properly.","shortMessageHtmlLink":"Add a proper test for multiple interfaces"}},{"before":"f6079de53f4a74d1d8be7f39c5531680b1d36288","after":"03cf07400349f588d4f69e51ac5c039ef330fe9f","ref":"refs/heads/fix-2810","pushedAt":"2024-01-14T18:35:38.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Update Binaryen\n\nThis version of binaryen.js has the requisite 4 GiB max memory change.\nFixes #2810.","shortMessageHtmlLink":"Update Binaryen"}},{"before":"ff03a3704bd89a498184d1fac725df89a03fc830","after":"f6079de53f4a74d1d8be7f39c5531680b1d36288","ref":"refs/heads/fix-2810","pushedAt":"2024-01-14T07:22:42.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Update Binaryen\n\nThis version of binaryen.js has the requisite 4 GiB max memory change.\nFixes #2810.","shortMessageHtmlLink":"Update Binaryen"}},{"before":null,"after":"ff03a3704bd89a498184d1fac725df89a03fc830","ref":"refs/heads/fix-2810","pushedAt":"2024-01-14T07:17:02.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Update Binaryen\n\nThis version of binaryen.js has the requisite 4 GiB max memory change.\nFixes #2810.","shortMessageHtmlLink":"Update Binaryen"}},{"before":null,"after":"6f6305a2cc9a7ddb29b6d791b988dca4addf3b00","ref":"refs/heads/side-effectful-compound","pushedAt":"2023-11-24T20:59:48.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Refactor assignments, property accesses, and element accesses\n\nThis commit allows the aforementioned to be compiled with precompiled\noperands, which will allow, in the next commit, unary and binary\nexpressions to avoid compiling the same this expression and element\nexpression (if any) twice (which duplicates side effects).","shortMessageHtmlLink":"Refactor assignments, property accesses, and element accesses"}},{"before":"8a76750fd968f32974c59744c3856cb57fa8c276","after":"4b4d68c44e23e5c18d400dbb72abba5aad00a363","ref":"refs/heads/forbid-duplicate-members","pushedAt":"2023-11-21T03:19:28.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Forbid duplicate static class and/or namespace members\n\nThis isn't fully TS compatible, but refactors targeting internal names,\nscoping, merging, etc. are needed to become more compatible. For\ninstance, if namespace members had unique separators in internal names,\nthen a non-exported namespace member would override a static class\nmember, assuming the names are the same.\n\nNote that this change doesn't prevent the compiler from attempting to\ncompile the duplicate global, and hence the previous commit is needed\nfor this to work fully.\n\nBarely fixes #2793.","shortMessageHtmlLink":"Forbid duplicate static class and/or namespace members"}},{"before":null,"after":"8a76750fd968f32974c59744c3856cb57fa8c276","ref":"refs/heads/forbid-duplicate-members","pushedAt":"2023-11-21T03:13:44.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Forbid duplicate static class and/or namespace members\n\nThis isn't fully TS compatible, but refactors targeting internal names,\nscoping, merging, etc. are needed to become more compatible. For\ninstance, if namespace members had unique separators in internal names,\nthen a non-exported namespace member would override a static class\nmember, assuming the names are the same.\n\nNote that this change doesn't prevent the compiler from attempting to\ncompile the duplicate global, and hence the previous commit is needed\nfor this to work fully.","shortMessageHtmlLink":"Forbid duplicate static class and/or namespace members"}},{"before":null,"after":"11cb13b8406ca8c91930290bdb028847013534d4","ref":"refs/heads/namespace-internal-name","pushedAt":"2023-11-20T05:06:52.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"BREAKING CHANGE: Avoid collisions between static class/namespace members\n\nThis commit changes the delimiter between namespaces and their members\nfrom \".\" to \"::\" in internal names. The new delimiter certainly feels\nvery un-JavaScript-y, but the meaning is still recognizable, and these\nnames aren't exposed to users in most cases anyway. Still, this is a\nbreaking change, as it affects the import names for `declare namespace`\nmembers (as seen in tests/compiler/declare.js), and transform authors\nwill also need to update their code accordingly.\n\nFixes #2793.","shortMessageHtmlLink":"BREAKING CHANGE: Avoid collisions between static class/namespace members"}},{"before":null,"after":"af31715a76a4ea0a1f8ba3d757e6154890ee1526","ref":"refs/heads/bump","pushedAt":"2023-11-09T18:35:25.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"fix: placeholder commit for aspublish\n\nThe commit that fixed the regression didn't start with \"fix:\" and such,\nso this commit accounts for that instead.","shortMessageHtmlLink":"fix: placeholder commit for aspublish"}},{"before":null,"after":"d22ae96cf6b588450d2dcf7c017e14fb4ed5298d","ref":"refs/heads/allow-manual-publish","pushedAt":"2023-11-09T18:11:02.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Allow manually triggered publishes\n\nThis allows #2786 (which fixes the regression from #2757) to be\npublished as soon as possible. Note that the main branch is the only\nbranch that can be published, since `ref: main` is passed to\nactions/checkout.","shortMessageHtmlLink":"Allow manually triggered publishes"}},{"before":"16e4dc5803310ba05ca80604f1675f4ae1ad6fbc","after":"dd8fd9d0c3a6b240c252be988bd249ddac763824","ref":"refs/heads/general-cleanup","pushedAt":"2023-11-04T20:27:55.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Bump the lockfile\n\nThe latest packages that were added to the lockfile when resolving a\nrebase conflict might not have survived the rest of the rebase, so\nanother bump is provided here instead.\n\nThis bump also caused TypeScript to emit an error related to an\nundici-types package due to this bump, and that is also fixed here.","shortMessageHtmlLink":"Bump the lockfile"}},{"before":"50a15c5005a150135a3184ba7230655799d52fa8","after":"16e4dc5803310ba05ca80604f1675f4ae1ad6fbc","ref":"refs/heads/general-cleanup","pushedAt":"2023-11-03T23:29:39.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Bump typescript. typescript-eslint and package-lock.json\n\npackage-lock.json might not have been updated properly through the\nrebase, and Typescript was out of date anyway. typescript-eslint was\nalso one major version behind.","shortMessageHtmlLink":"Bump typescript. typescript-eslint and package-lock.json"}},{"before":"9309a3fc6aeb95a4b4dd58e1024e9de67837f79c","after":"50a15c5005a150135a3184ba7230655799d52fa8","ref":"refs/heads/general-cleanup","pushedAt":"2023-11-03T23:19:57.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CountBleck","name":null,"path":"/CountBleck","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79281724?s=80&v=4"},"commit":{"message":"Bump typescript. typescript-eslint and package-lock.json\n\npackage-lock.json might not have been updated properly through the\nrebase, and Typescript was out of date anyway. typescript-eslint was\nalso one major version behind.","shortMessageHtmlLink":"Bump typescript. typescript-eslint and package-lock.json"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEWeBMmAA","startCursor":null,"endCursor":null}},"title":"Activity · CountBleck/assemblyscript"}