Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump github/codeql-action from 1 to 2 #43

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Apr 25, 2022

Bumps github/codeql-action from 1 to 2.

Changelog

Sourced from github/codeql-action's changelog.

2.1.8 - 08 Apr 2022

  • Update default CodeQL bundle version to 2.8.5. #1014
  • Fix error where the init action would fail due to a GitHub API request that was taking too long to complete #1025

2.1.7 - 05 Apr 2022

  • A bug where additional queries specified in the workflow file would sometimes not be respected has been fixed. #1018

2.1.6 - 30 Mar 2022

  • [v2+ only] The CodeQL Action now runs on Node.js v16. #1000
  • Update default CodeQL bundle version to 2.8.4. #990
  • Fix a bug where an invalid commit_oid was being sent to code scanning when a custom checkout path was being used. #956
Commits
  • 2c03704 Allow the version of the ML-powered pack to depend on the CLI version
  • dd6b592 Simplify ML-powered query status report definition
  • a90d8bf Merge pull request #1011 from github/henrymercer/ml-powered-queries-pr-check
  • dc0338e Use latest major version of actions/upload-artifact
  • 57096fe Add a PR check to validate that ML-powered queries are run correctly
  • b0ddf36 Merge pull request #1012 from github/henrymercer/update-actions-major-versions
  • 1ea2f2d Merge branch 'main' into henrymercer/update-actions-major-versions
  • 9dcc141 Merge pull request #1010 from github/henrymercer/stop-running-ml-powered-quer...
  • ea751a9 Update other Actions from v2 to v3
  • a2949f4 Update actions/checkout from v2 to v3
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

tsandall and others added 3 commits April 20, 2022 07:13
This is a follow-on to aeda97e so
that users can declare multiple rules with the same name using ":=".

The original purpose of the check was to reduce the chance that
someone would write a rule that generates conflicts. The problem w/
this check is that doesn't remove conflicts completely--it only
removes a class of conflict errors that are trivial to diagnose. For
example:

	package foo

	p := 7
	p := 8

If the user asks for `p`, previously they'd receive a type error; now
they're receive an eval error. This example is a bit contrived
though. In reality, conflicts are a more likely to occur due to
iteration and assignment to a single variable... for example:

	package foo

	p := x { some x in input }

Of course, this rule will pass the check because the check cannot
determine whether there _will_ be multiple assignments to `p`.

Since the check fails to prevent a class of errors that is difficult
to debug AND it would be beneficial to use := and == everywhere
instead of =, we're opting to disable it going forward.

Signed-off-by: Torin Sandall <torinsandall@gmail.com>
This partially addresses open-policy-agent#4599.

Signed-off-by: Torin Sandall <torinsandall@gmail.com>
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 1 to 2.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@v1...v2)

---
updated-dependencies:
- dependency-name: github/codeql-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Apr 25, 2022
@tsandall tsandall force-pushed the main branch 2 times, most recently from 0997f8f to d500466 Compare March 20, 2023 21:07
@tsandall tsandall force-pushed the main branch 5 times, most recently from fbbaf2e to 9f1c380 Compare April 12, 2024 23:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant