Add workaround for weird CodeQL releasing schema #72

Activity

1. mirabilos

   added 2 commits that reference this issue on Mar 26, 2023

   revert to an older version of codeql-bundle

   ...

   21efd98

   until saadmk11/github-actions-version-updater#72 is fixed

   e644409
2. mirabilos

   added a commit that references this issue on Apr 6, 2023

   until saadmk11/github-actions-version-updater#72 is fixed

   dacaa7a
3. mirabilos commented on Apr 17, 2023

   

   mirabilos

   on Apr 17, 2023

   Author

   More actions

   I put github/codeql-action/init@v2 into the files now, and when I run the updater, it throws an exception (though it’s not clear from the context it’s the codeql one, I just ran the updater on an almost-copy of the .github/workflows/ directory in another repo that had all but the codeql one, and it worked fine):

   2023-04-17T02:42:06.7521618Z     return _run_code(code, main_globals, None,
   2023-04-17T02:42:06.7521932Z   File "/usr/local/lib/python3.10/runpy.py", line 86, in _run_code
   2023-04-17T02:42:06.7522221Z     exec(code, run_globals)
   2023-04-17T02:42:06.7522489Z   File "/app/src/main.py", line 473, in <module>
   2023-04-17T02:42:06.7522765Z     actions_version_updater.run()
   2023-04-17T02:42:06.7523035Z   File "/app/src/main.py", line 59, in run
   2023-04-17T02:42:06.7523296Z     self._update_workflow(workflow_path)
   2023-04-17T02:42:06.7523603Z   File "/app/src/main.py", line 149, in _update_workflow
   2023-04-17T02:42:06.7523917Z     new_version, new_version_data = self._get_new_version(
   2023-04-17T02:42:06.7524233Z   File "/app/src/main.py", line 360, in _get_new_version
   2023-04-17T02:42:06.7524547Z     latest_release_data = self._get_latest_version_release(
   2023-04-17T02:42:06.7524884Z   File "/app/src/main.py", line 290, in _get_latest_version_release
   2023-04-17T02:42:06.7525152Z     latest_release = next(
   2023-04-17T02:42:06.7525414Z   File "/app/src/main.py", line 292, in <lambda>
   2023-04-17T02:42:06.7525740Z     lambda r: self._release_filter_function(r, parsed_current_version),
   2023-04-17T02:42:06.7526069Z   File "/app/src/main.py", line 271, in filter_func
   2023-04-17T02:42:06.7526395Z     return any(check(release_tag, current_version) for check in checks)
   2023-04-17T02:42:06.7526713Z   File "/app/src/main.py", line 271, in <genexpr>
   2023-04-17T02:42:06.7527035Z     return any(check(release_tag, current_version) for check in checks)
   2023-04-17T02:42:06.7527344Z   File "/app/src/main.py", line 255, in <lambda>
   2023-04-17T02:42:06.7527723Z     checks.append(lambda r, c: parse(r["tag_name"]).major > c.major)
   2023-04-17T02:42:06.7528161Z AttributeError: 'LegacyVersion' object has no attribute 'major'
   

   The beginning is cut off, perhaps earlier in the log, but unsure.
4. saadmk11 commented on Aug 5, 2023

   

   saadmk11

   on Aug 5, 2023

   Owner

   More actions

   The action now displays warning messages in such cases and will suggest the latest release instead of crashing. You can also skip github/codeql-action/init@v2 update by using ignore option.
5. saadmk11

   added

   bugSomething isn't workingSomething isn't working

   on Aug 5, 2023
6. mirabilos commented on Aug 6, 2023

   

   mirabilos

   on Aug 6, 2023

   Author

   More actions

   OK, not crashing, and ignoring it is one thing, but maybe have a whitelist of actions for which to not look at the releases but at tags instead would make sense?
7. mirabilos

   added a commit that references this issue on Aug 12, 2023

   ignore "github/codeql-action/init@v2"

   ...

   22fc8ce