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

Merge main into releases/v2 #1303

Closed
wants to merge 50 commits into from
Closed

Conversation

github-actions[bot]
Copy link
Contributor

Merging 297ec80 into releases/v2

Conductor for this PR is @alexet.

Contains the following pull requests:

Please do the following:

  • Ensure the CHANGELOG displays the correct version and date.
  • Ensure the CHANGELOG includes all relevant, user-facing changes since the last release.
  • Check that there are not any unexpected commits being merged into the releases/v2 branch.
  • Ensure the docs team is aware of any documentation changes that need to be released.
  • Approve and merge this PR. Make sure Create a merge commit is selected rather than Squash and merge or Rebase and merge.
  • Merge the mergeback PR that will automatically be created once this PR is merged.
  • Merge the v1 release PR that will automatically be created once this PR is merged.

github-actions[bot] and others added 30 commits September 29, 2022 17:46
Mergeback v2.1.26 refs/heads/releases/v2 into main
TRAP Caching: Add timeouts to upload/download operations
It's possible to determine this otherwise, but this makes it easier to
spot.
The user config parser in the CLI doesn't yet support it.
Add logging statements declaring state of the cli_config_file_enabled
* Correctly report CodeQL version when using cache

* Add JS generated files

* Add test for return value of `setupCodeQL`

* Fill in missing return value comment
This commit centralizes how feature flags are handled. All feature flags
must now add an entry in the `featureFlagConfig` dictionary. This
dictionary associates the flag with an environment variable name and
optionally a minimum version for CodeQL.

The new logic is:

- if the environment variable is set to false: disabled
- if the minimum version requirement specified and met: disabled
- if the environment variable is set to true: enable
- Otherwise check feature flag enablement from the server
Convert "Invalid source root" errors to UserErrors
- Change env var name for `MlPoweredQueriesEnabled`
- Throw error if minimumVersion is specified, but CodeQL argument is not
  supplied.
- Fix failing tests. Note that I removed a config-utils test because it
  is no longer relevant since we handle codeql minimum versions in the
  `getValue` function.
* Add changelog note for Go extraction reconciliation

* Update CHANGELOG.md

Co-authored-by: Henry Mercer <[email protected]>

* Update CHANGELOG.md

Co-authored-by: Andrew Eisenberg <[email protected]>

* Tweaks from PR review

Co-authored-by: Henry Mercer <[email protected]>
Co-authored-by: Andrew Eisenberg <[email protected]>
Internal refactoring so that `GitHubFeatureFlags` is
private only. The public facing class is `Features`.
* Merge main into releases/v2 (#1287)

* Update changelog and version after v2.1.26

* Update checked-in dependencies

* Don't check for Go logs on failure (#1279)

* Update supported GitHub Enterprise Server versions. (#1275)

Co-authored-by: GitHub <[email protected]>

* TRAP Caching: Add timeouts to upload/download operations

* Add logging statements declaring state of the cli_config_file_enabled

It's possible to determine this otherwise, but this makes it easier to
spot.

* Avoid using single value as array

The user config parser in the CLI doesn't yet support it.

* Extract logging statements to separate function

* Correctly report CodeQL version when using cache (#1259)

* Correctly report CodeQL version when using cache

* Add JS generated files

* Add test for return value of `setupCodeQL`

* Fill in missing return value comment

* Convert "Invalid source root" errors to UserErrors

* Add changelog note for Go extraction reconciliation (#1286)

* Add changelog note for Go extraction reconciliation

* Update CHANGELOG.md

Co-authored-by: Henry Mercer <[email protected]>

* Update CHANGELOG.md

Co-authored-by: Andrew Eisenberg <[email protected]>

* Tweaks from PR review

Co-authored-by: Henry Mercer <[email protected]>
Co-authored-by: Andrew Eisenberg <[email protected]>

* Update changelog for v2.1.27

Co-authored-by: github-actions[bot] <[email protected]>
Co-authored-by: Chuan-kai Lin <[email protected]>
Co-authored-by: Angela P Wen <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: GitHub <[email protected]>
Co-authored-by: Edoardo Pirovano <[email protected]>
Co-authored-by: Edoardo Pirovano <[email protected]>
Co-authored-by: Andrew Eisenberg <[email protected]>
Co-authored-by: Henry Mercer <[email protected]>

* Update changelog and version after v2.1.27

* Update checked-in dependencies

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <[email protected]>
Co-authored-by: Chuan-kai Lin <[email protected]>
Co-authored-by: Angela P Wen <[email protected]>
Co-authored-by: GitHub <[email protected]>
Co-authored-by: Edoardo Pirovano <[email protected]>
Co-authored-by: Edoardo Pirovano <[email protected]>
Co-authored-by: Andrew Eisenberg <[email protected]>
Co-authored-by: Henry Mercer <[email protected]>
Avoid usage of "Feature Flag" unless we are talking specifically about
the response from github features api. Otherwise, use terms like
"Toggleable features".

Note both "toggleable" and "togglable" appear to be valid spellings of
the word. I chose the first for no good reason.
* Clarify merging with merge commit

* Add merge commit message to mergeback PRs
This version has the fix applied
henrymercer and others added 17 commits October 11, 2022 11:52
…er-versions

Update supported GitHub Enterprise Server versions.
TRAP Caching: Disable on self-hosted runners
Bumps [@octokit/types](https://github.com/octokit/types.ts) from 7.1.1 to 8.0.0.
- [Release notes](https://github.com/octokit/types.ts/releases)
- [Commits](octokit/types.ts@v7.1.1...v8.0.0)

---
updated-dependencies:
- dependency-name: "@octokit/types"
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
…types-8.0.0

Bump @octokit/types from 7.1.1 to 8.0.0
For more information see
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

This change bumps a bunch of the internal actions packages. Note that
the only required version change is `actions/core` to 1.10.0. The others
are not required, but seem like a reasonable idea.

It also changes all of the workflows that use `set-output`.
Co-authored-by: Aditya Sharad <[email protected]>
@aeisenberg
Copy link
Contributor

Closing this. After merging #1304, you can restart the process.

@aeisenberg aeisenberg closed this Oct 14, 2022
@henrymercer henrymercer reopened this Oct 17, 2022
@henrymercer henrymercer force-pushed the update-v2.1.28-297ec80a branch from 01dde39 to 07cf610 Compare October 17, 2022 09:27
@henrymercer
Copy link
Contributor

#1304 is conflicting with main. Perhaps your local main was stale? This branch merges cleanly into both releases/v2 and main, so I think this ought to work for the release.

@henrymercer
Copy link
Contributor

We decided to merge #1308 instead. Once we've merged that back into main we can restart the release process.

@henrymercer henrymercer deleted the update-v2.1.28-297ec80a branch October 17, 2022 19:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants