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.

Sign up for GitHub

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

Infrastructure: Bump @octokit/rest from 18.12.0 to 21.0.2 #3099

Closed
wants to merge 1 commit into from
+187 −171
Closed

Infrastructure: Bump @octokit/rest from 18.12.0 to 21.0.2 #3099

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
356 changes: 186 additions & 170 deletions package-lock.json
View file
2 changes: 1 addition & 1 deletion package.json
View file
Original file line number Diff line number Diff line change
@@ -89,7 +89,7 @@
]
},
"dependencies": {
"@octokit/rest": "^18.12.0",
"@octokit/rest": "^21.0.2",
"dotenv": "^16.4.5",
"node-html-parser": "^5.2.0"
}

Unchanged files with check annotations Beta

View file
content/patterns/treeview/examples/treeview-navigation.html
If the scope of the header element were body, browsers would automatically treat the header as an ARIA banner,
so the header would not need the role="banner". -->
<div class="page">
<header role="banner">

Check warning on line 75 in content/patterns/treeview/examples/treeview-navigation.html

GitHub Actions / lint-html 

The “banner” role is unnecessary for element “header”.
<div class="title" id="id_website_title">Mythical University</div>
<div class="tagline">Using a Tree widget pattern for navigation links</div>
</header>
<!-- NOTE: In a real website the following SECTION element should be MAIN element -->
<section class="main" aria-labelledby="id_website_title id_page_title">
<h1 class="page_title" id="id_page_title">Mythical University</h1>

Check warning on line 296 in content/patterns/treeview/examples/treeview-navigation.html

GitHub Actions / lint-html 

Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).
<div class="content">
<p></p>
</div>
<!-- NOTE: In a real website the footer element would be a top level element, i.e., it would have the body as its scope.
If the scope of the footer element were body, browsers would automatically treat the header as an ARIA contentinfo,
so the footer would not need the role="contentinfo". -->
<footer role="contentinfo">Mythical University footer information</footer>

Check warning on line 305 in content/patterns/treeview/examples/treeview-navigation.html

GitHub Actions / lint-html 

The “contentinfo” role is unnecessary for element “footer”.
</div>
</div>
<div role="separator" id="ex_end_sep" aria-labelledby="ex_end_sep ex_label" aria-label="End of"></div>
View file
content/patterns/menubar/examples/menubar-navigation.html
<!-- NOTE: In an actual website, the header element would be a top level element, i.e., it would have the body as its scope.
If the scope of the header element were body, browsers would automatically treat the header as an ARIA banner,
so the header would not need the role="banner". -->
<header role="banner">

Check warning on line 69 in content/patterns/menubar/examples/menubar-navigation.html

GitHub Actions / lint-html 

The “banner” role is unnecessary for element “header”.
<div class="title">Mythical University</div>
<div class="tagline">Using a Menubar for navigation links</div>
</header>
<!-- NOTE: The following SECTION element would be a MAIN element in an actual website -->
<div class="main">
<section aria-labelledby="id-page-title">
<h1 id="id-page-title" class="page_title">Mythical University</h1>

Check warning on line 217 in content/patterns/menubar/examples/menubar-navigation.html

GitHub Actions / lint-html 

Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).
<div class="content">
<p></p>
</div>
NOTE: In an actual website, the footer element would be a top level element, i.e., it would have the body as its scope.
If the scope of the footer element were body, browsers would automatically treat the footer as an ARIA contentinfo landmark, so the footer would not need the role="contentinfo".
-->
<footer role="contentinfo">Mythical University footer information</footer>

Check warning on line 227 in content/patterns/menubar/examples/menubar-navigation.html

GitHub Actions / lint-html 

The “contentinfo” role is unnecessary for element “footer”.
</div>
</div>
<div role="separator" id="ex_end_sep" aria-labelledby="ex_end_sep ex_label" aria-label="End of"></div>