-
Notifications
You must be signed in to change notification settings - Fork 3
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
Bump octokit from 1.7.2 to 3.1.2 #28
Conversation
d8dd362
to
e4104fa
Compare
Bumps [octokit](https://github.com/octokit/octokit.js) from 1.7.2 to 3.1.2. - [Release notes](https://github.com/octokit/octokit.js/releases) - [Commits](octokit/octokit.js@v1.7.2...v3.1.2) --- updated-dependencies: - dependency-name: octokit dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
e4104fa
to
c0fbd7b
Compare
@ravinderk sounds good, will leave this for anyone on @10up/open-source-practice that wants to pick up that change |
@@ -23,7 +23,7 @@ | |||
"dependencies": { | |||
"execa": "^6.1.0", | |||
"meow": "^10.1.2", | |||
"octokit": "^1.7.2" | |||
"octokit": "^3.1.2" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
npm audit
reports 2 high vulnerability, 1 of which is for octokit < 3.1.2
and 3.1.2
has support for node 18 and 20 only.
I just checked that Gutenberg's development environment is set to node v20. Should we start discussing around the topic of updating node version across our repo to v18 at least?
cc: @10up/open-source-practice
Bumps octokit from 1.7.2 to 3.1.2.
Release notes
Sourced from octokit's releases.
... (truncated)
Commits
b59da80
fix: updates app.js for the handling of an error being thrown by the verify m...f514e4b
build(deps): lock file maintenance (#2574)fdc9bba
chore(deps): update dependency prettier to v3.1.0d3a9984
build(deps): lock file maintenance870d89d
build(deps): lock file maintenance (#2565)78735dd
build(deps): lock file maintenance (#2562)72ea679
chore(deps): update dependency@types/node
to v20692f7db
ci(action): update actions/setup-node action to v4 (#2560)5b47b84
build(deps): lock file maintenance (#2558)941c584
docs: fixing typos in README (#2557)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@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)You can disable automated security fix PRs for this repo from the Security Alerts page.