Skip to content

Commit be02864

Browse files
authored
Copyedit
1 parent 8c92d92 commit be02864

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

go/ql/lib/CHANGELOG.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -9,13 +9,13 @@
99

1010
* When a function or type has more than one anonymous type parameters, they were mistakenly being treated as the same type parameter. This has now been fixed.
1111
* Local source models for reading and parsing environment variables have been added for the following libraries:
12-
* os
13-
* syscall
14-
* github.com/caarlos0/env
15-
* github.com/gobuffalo/envy
16-
* github.com/hashicorp/go-envparse
17-
* github.com/joho/godotenv
18-
* github.com/kelseyhightower/envconfig
12+
* `os`
13+
* `syscall`
14+
* `github.com/caarlos0/env`
15+
* `github.com/gobuffalo/envy`
16+
* `github.com/hashicorp/go-envparse`
17+
* `github.com/joho/godotenv`
18+
* `github.com/kelseyhightower/envconfig`
1919
* Local source models have been added for the APIs which open files in the `io/fs`, `io/ioutil` and `os` packages in the Go standard library. You can optionally include threat models as appropriate when using the CodeQL CLI and in GitHub code scanning. For more information, see [Analyzing your code with CodeQL queries](https://docs.github.com/code-security/codeql-cli/getting-started-with-the-codeql-cli/analyzing-your-code-with-codeql-queries#including-model-packs-to-add-potential-sources-of-tainted-data>) and [Customizing your advanced setup for code scanning](https://docs.github.com/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning#extending-codeql-coverage-with-threat-models).
2020

2121
### Bug Fixes

javascript/ql/src/CHANGELOG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
### Major Analysis Improvements
44

5-
- Added a new query (`js/actions/actions-artifact-leak`) to detect GitHub Actions artifacts that may leak the GITHUB_TOKEN token.
5+
- Added a new query (`js/actions/actions-artifact-leak`) to detect GitHub Actions artifacts that may leak the `GITHUB_TOKEN` token.
66

77
## 1.1.3
88

0 commit comments

Comments
 (0)