Merge main into v1 #913
Merged
Merge main into v1 #913
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Bumps [trim-off-newlines](https://github.com/stevemao/trim-off-newlines) from 1.0.2 to 1.0.3. - [Release notes](https://github.com/stevemao/trim-off-newlines/releases) - [Commits](stevemao/trim-off-newlines@v1.0.2...v1.0.3) --- updated-dependencies: - dependency-name: trim-off-newlines dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
…newlines-1.0.3 Bump trim-off-newlines from 1.0.2 to 1.0.3
Bumps [long](https://github.com/dcodeIO/long.js) from 4.0.0 to 5.2.0. - [Release notes](https://github.com/dcodeIO/long.js/releases) - [Commits](dcodeIO/long.js@4.0.0...v5.2.0) --- updated-dependencies: - dependency-name: long dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Mergeback v1.0.31 refs/heads/v1 into main
Ensure that all workflows are able to write security events.
Co-authored-by: Andrew Eisenberg <aeisenberg@github.com>
Bump long from 4.0.0 to 5.2.0
Bumps [@ava/typescript](https://github.com/avajs/typescript) from 2.0.0 to 3.0.1. - [Release notes](https://github.com/avajs/typescript/releases) - [Commits](avajs/typescript@v2.0.0...v3.0.1) --- updated-dependencies: - dependency-name: "@ava/typescript" dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
This is not necessary.
Move a couple of entries for #889 that should have been in the unreleased section but were inadvertently moved into the 1.0.31 release.
Fix changelog
Fix typo in error message
…cript-3.0.1 Upgrade AVA to v4
We report this information in the `init` status report rather than the `analyze` status report so we can gather data about timeouts.
Declare the merge base as base for code scanning comparisons
When multiple ML-powered JS packs are in scope (an unsupported scenario), the status report is "multiple".
Update default CodeQL version to 2.8.0
Some platforms that ingest this status report charge based on the cardinality of the fields, so here we restrict the version strings we support to a fixed set.
Also be more explicit about which version strings are reportable in the code.
…ry-enablement Report ML-powered query enablement in the `init` status report
cklin
approved these changes
Feb 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merging 4eb03fb into v1
Conductor for this PR is @cklin
Contains the following pull requests:
initstatus report #907 - Report ML-powered query enablement in theinitstatus report (@henrymercer)Contains the following commits not from a pull request:
security-events: writefrom tests (@aeisenberg)Please review the following: