Merge branch 'develop' into fix/band-storage-mismatch

Author: DivitJain26

.github/workflows/lint_changed_files.yml

@@ -274,7 +274,7 @@ jobs:
         # Pin action to full length commit SHA
         uses: r-lib/actions/setup-r@6f6e5bc62fba3a704f74e7ad7ef7676c5c6a2590 # v2.11.4
         with:
-          r-version: '3.5.3'
+          r-version: '4.2.0'
 
       # Lint R files:
       - name: 'Lint R files'

.github/workflows/lint_random_files.yml

@@ -374,7 +374,7 @@ jobs:
         # Pin action to full length commit SHA
         uses: r-lib/actions/setup-r@6f6e5bc62fba3a704f74e7ad7ef7676c5c6a2590 # v2.11.4
         with:
-          r-version: '4.3.3'
+          r-version: '4.2.0'
 
       # Lint R files:
       - name: 'Lint R files'

.github/workflows/standalone_keepalive.yml

@@ -21,9 +21,9 @@ name: standalone_keepalive
 
 # Workflow triggers:
 on:
-  # Run the workflow on the first day of each week:
+  # Run the workflow daily:
   schedule:
-    - cron: '0 0 * * 1'
+    - cron: '0 2 * * *'
 
   # Allow the workflow to be manually run:
   workflow_dispatch:

docs/contributing/zulip_guide.md

@@ -0,0 +1,136 @@
+<!--
+
+@license Apache-2.0
+
+Copyright (c) 2026 The Stdlib Authors.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+
+-->
+
+<!-- lint disable expected-html-sections -->
+
+# Zulip Guide
+
+> Guide to the stdlib Zulip chat.
+
+This guide provides best practices and community norms for the [**stdlib Zulip chat**][stdlib-zulip], home of the stdlib community (see [announcement][zulip-announcement]). Everyone is welcome to join or browse the web-public channels (which you can see without signing up). The community norms and guidelines provided in this document are to help ensure that everyone can get the most out of this platform and, hopefully, have a positive experience.
+
+## Getting Started
+
+When you first join, a welcome bot will greet you and share some tips specific to stdlib on how to participate effectively. If you're new to Zulip, you may also want to check out [Zulip's official getting started guide][zulip-getting-started] for a quick overview of how the platform works. If you've used other chat platforms, such as Slack or Discord, things should feel pretty familiar. The one key difference is that Zulip organizes conversations into "topics" rather than "threads". This allows for more focused discussions and makes it easier to follow specific conversations without getting lost in a stream of messages. For more on this, see [Zulip's introduction to topics][zulip-intro-to-topics].
+
+We encourage you to come say hello and tell us a bit about yourself in the [**#introductions**][stdlib-introductions] channel.
+
+## Community Norms
+
+### Where to post
+
+First and foremost, whenever possible, try to post your questions **in public** (rather than sending direct messages, a.k.a. DMs). Asking questions in public is the fastest way to get a response, as more people can help, _plus_ it's likely that someone else will benefit from finding out the answer to your question. The stdlib team is active in the chat, so you shouldn't need to use **@-mentions** by default.
+
+Each channel has a description (don't worry too much about posting in the "right" channel—moderators can help [move content][zulip-move-content] if needed), and conversations are organized into [**topics**][zulip-intro-to-topics]. If you're starting a new discussion, try to pick a brief, descriptive topic name that captures the subject of your message. Topic names also help others find relevant information from past conversations (learn more about [Zulip search filters here][zulip-search-filters]). You can edit a topic name at any time, so if you realize that your original topic name isn't quite right, feel free to update it.
+
+Because it's easy to move content around, please **do NOT cross-post**. Not only can this be confusing, but you risk duplication of effort if multiple people respond to the same question in different channels.
+
+#### Channels
+
+When you first join, you'll automatically be subscribed to several "default" channels. However, there are more channels you might want to explore.
+
+The channels are roughly organized into categories in the left-hand sidebar. At the bottom, you can click on "Browse Channels" to see the full list.
+
+Some categories and channels of interest include:
+
+-   **General Interest**
+
+    -   **announcements**: Announcements everyone should see, including new releases, blog posts, and public events.
+    -   **general**: General topics.
+    -   **office-hours**: Information related to stdlib's weekly [office hours][stdlib-office-hours].
+    -   **water-cooler**: A place to discuss random topics, unrelated to stdlib and its development.
+
+-   **Feedback & Support**
+
+    -   **case-studies**: Using stdlib in your application? Got a cool new demo? Share it here!
+    -   **feedback**: Post your reactions to or feedback on using stdlib.
+    -   **problems**: For reporting and discussing issues in using stdlib.
+    -   **user-questions**: For questions about how to accomplish your goals with stdlib.
+
+-   **GSOC**
+
+    -   **gsoc-questions**: Interested in participating in Google Summer of Code? Have questions? Ask here!
+
+-   **Contributors**
+
+    -   **dev**: General development topics.
+    -   **dev-questions**: Ask questions related to developing stdlib.
+    -   **getting-started**: Are you a new contributor? Post your questions here!
+    -   **introductions**: Interested in contributing to stdlib? Please introduce yourself here!
+    -   **review-requests**: Requests for PR reviews.
+
+-   **Development**: Channels related to specific stdlib namespaces, and other areas such as documentation and tooling.
+
+-   **GitHub**: These are feeds generated from GitHub activity, such as new issues and pull requests. You can use these channels to keep up with the latest activity in the project.
+
+-   **Other**
+
+    -   **sandbox**: Experiment with Zulip here.
+    -   **zulip**: Questions and discussion about using Zulip.
+
+### Custom Linkifiers
+
+We've set up some [custom linkifiers][zulip-linkifiers] to make it easy to share links to GitHub issues and pull requests. If you type **`#1234`** in a message, it will automatically link to the issue or PR with that number in the main [stdlib GitHub repository][stdlib-github-repo]. There's also a special linkifier for the [stdlib Google Summer of Code repo][stdlib-gsoc-repo]; you simply type **`#G{id-number}`**. Note that these work for both issues and pull requests (GitHub uses the same numbering for both).
+
+### Code of Conduct
+
+The [stdlib Code of Conduct][stdlib-code-of-conduct] applies to all community spaces, including stdlib's Zulip. Should you encounter an issue, [Zulip's reporting tools][zulip-reporting] and our moderation team will be notified and available to assist.
+
+## Feedback and Suggestions
+
+If you have feedback or suggestions about improving our Zulip community, don't hesitate to share your thoughts. We have a special meta channel, [**#zulip**][stdlib-zulip-channel], for discussing community-related topics. For more general feedback, there's also the aptly-named [**#feedback**][stdlib-feedback-channel] channel.
+
+The best part of open source is the community, so we're committed to making our Zulip a welcoming and inclusive space for everyone. We look forward to chatting with you there!
+
+<section class="links">
+
+[stdlib-zulip]: https://stdlib.zulipchat.com
+
+[zulip-announcement]: https://blog.stdlib.io/announcing-zulip/
+
+[stdlib-code-of-conduct]: https://github.com/stdlib-js/stdlib/blob/develop/CODE_OF_CONDUCT.md
+
+[zulip-reporting]: https://zulip.com/help/report-a-message
+
+[zulip-getting-started]: https://zulip.com/help/getting-started-with-zulip
+
+[zulip-intro-to-topics]: https://zulip.com/help/introduction-to-topics
+
+[stdlib-introductions]: https://stdlib.zulipchat.com/#narrow/channel/546733-introductions
+
+[zulip-move-content]: https://zulip.com/help/move-content-to-another-channel
+
+[zulip-search-filters]: https://zulip.com/help/search-for-messages#search-filters
+
+[zulip-linkifiers]: https://zulip.com/help/add-a-custom-linkifier
+
+[stdlib-github-repo]: https://github.com/stdlib-js/stdlib
+
+[stdlib-gsoc-repo]: https://github.com/stdlib-js/google-summer-of-code
+
+[stdlib-zulip-channel]: https://stdlib.zulipchat.com/#narrow/channel/546662-zulip
+
+[stdlib-feedback-channel]: https://stdlib.zulipchat.com/#narrow/channel/546708-feedback
+
+[stdlib-office-hours]: https://github.com/stdlib-js/meetings/issues?q=sort:updated-desc%20is:issue%20label:%22Office%20Hours%22
+
+</section>
+
+<!-- /.links -->

etc/typescript/tsconfig.json

@@ -10,7 +10,7 @@
     "forceConsistentCasingInFileNames": true,
     "keyofStringsOnly": false,
     "lib": [
-      "es6"
+      "esnext"
     ],
     "module": "commonjs",
     "moduleResolution": "node",

lib/node_modules/@stdlib/_tools/eslint/rules/capitalized-comments/lib/main.js

@@ -22,6 +22,7 @@
 
 var isCapitalized = require( '@stdlib/assert/is-capitalized' );
 var hasOwnProp = require( '@stdlib/assert/has-own-property' );
+var uppercase = require( '@stdlib/string/base/uppercase' );
 var ltrim = require( '@stdlib/string/left-trim' );
 var copy = require( '@stdlib/utils/copy' );
 var DEFAULTS = require( './defaults.json' );
@@ -57,7 +58,7 @@ function main( context ) {
 	if ( hasOwnProp( options, 'whitelist' ) ) {
 		opts.whitelist = options.whitelist.slice();
 	}
-	source = context.getSourceCode();
+	source = context.sourceCode;
 	visited = {};
 
 	/**
@@ -89,7 +90,7 @@ function main( context ) {
 
 			str = source.getText( comment );
 			idx = str.search( /[a-zA-Z]/ );
-			ch = str.charAt( idx ).toUpperCase();
+			ch = uppercase( str.charAt( idx ) );
 			replacement = str.slice( 0, idx ) + ch + str.slice( idx+1 );
 			return fixer.replaceText( comment, replacement );
 		}
@@ -194,7 +195,7 @@ function main( context ) {
 		var i;
 
 		comments = source.getCommentsInside( node );
-		scope = context.getScope( node );
+		scope = source.getScope( node );
 		for ( i = 0; i < comments.length; i++ ) {
 			comment = comments[ i ];
 			if ( comment.type !== 'Shebang' && !visited[ comment.range ] ) {

lib/node_modules/@stdlib/_tools/eslint/rules/doctest-annotation-spacing/lib/main.js

@@ -66,7 +66,7 @@ var rule;
 * @returns {Object} validators
 */
 function main( context ) {
-	var source = context.getSourceCode();
+	var source = context.sourceCode;
 
 	/**
 	* Reports the error message.