.changeset/fuzzy-paws-explain.md

@@ -0,0 +1,6 @@
+---
+"@nomicfoundation/hardhat-ledger": minor
+"hardhat": minor
+---
+
+Add support for the Prague hardfork

.changeset/hot-birds-cover.md

@@ -0,0 +1,5 @@
+---
+"hardhat": patch
+---
+
+Use `npm_config_user_agent` to determine what package manager to use for project creation

.changeset/metal-kings-hide.md

@@ -0,0 +1,5 @@
+---
+"@nomicfoundation/ignition-ui": patch
+---
+
+Override max-width to fix ignition graph centering

.changeset/ninety-beans-warn.md

@@ -0,0 +1,6 @@
+---
+"hardhat": patch
+---
+
+Upgraded EDR to [v0.9.0](https://github.com/NomicFoundation/edr/releases/tag/%40nomicfoundation%2Fedr%400.9.0):
+- Added support for the Prague hardfork

.changeset/selfish-horses-peel.md

@@ -0,0 +1,5 @@
+---
+"hardhat": patch
+---
+Upgraded EDR to [v0.10.0](https://github.com/NomicFoundation/edr/releases/tag/%40nomicfoundation%2Fedr%400.10.0):
+* Add Prague hardfork to the list of supported `SpecId`s

.github/ISSUE_TEMPLATE/hardhat-3-alpha.yml

@@ -0,0 +1,8 @@
+name: Hardhat 3 Alpha feedback
+description: Give feedback about the Hardhat 3 Alpha.
+labels: hardhat-3-alpha
+body:
+  - type: textarea
+    attributes:
+      label: "Feedback"
+      placeholder: "Your feedback"

.github/PULL_REQUEST_TEMPLATE.md

@@ -7,6 +7,15 @@ Please:
  - consider the checklist items below
  - keep the ones that make sense for your PR, and
  - DELETE the items that DON'T make sense for your PR.
+
+## Note about small PRs and airdrop farming
+
+We generally really appreciate external contributions, and strongly encourage meaningful additions and fixes! However, due to a recent increase in small PRs potentially created to farm airdrops, we might need to close a PR without explanation if any of the following apply:
+
+- It is a change of very minor value that still requires additional review time/fixes (e.g. PRs fixing trivial spelling errors that can’t be merged in less than a couple of minutes due to incorrect suggestions)
+- It introduces inconsequential changes (e.g. rewording phrases)
+- The author of the PR does not respond in a timely manner
+- We suspect the Github account of the author was created for airdrop farming
 -->
 
 - [ ] Because this PR includes a **bug fix**, relevant tests have been included.

.github/workflows/autoassign-issues.yml

@@ -15,8 +15,9 @@ jobs:
           script: |
             // each user has a chance of (p - (previousP ?? 0)) to be assigned
             const potentialAssignees = [
-              ["kanej", 1/3],
-              ["schaable", 2/3],
+              ["kanej", 1/4],
+              ["schaable", 2/4],
+              ["galargh", 3/4],
               ["ChristopherDedominici", 1.0],
             ];
 

CONTRIBUTING.md

@@ -139,3 +139,12 @@ When tests are run, Hardhat gets initialized multiple times, and that means unlo
 This problem is normally not present if you are monkey-patching an object that you initialized, but it is when monkey-patching a class, its prototype, or a singleton object initialized by the library itself.
 
 For an example on how to do it properly, please take a look at the `hardhat-truffle5` plugin.
+
+## Note about small PRs and airdrop farming
+
+We generally really appreciate external contributions, and strongly encourage meaningful additions and fixes! However, due to a recent increase in small PRs potentially created to farm airdrops, we might need to close a PR without explanation if any of the following apply:
+
+- It is a change of very minor value that still requires additional review time/fixes (e.g. PRs fixing trivial spelling errors that can’t be merged in less than a couple of minutes due to incorrect suggestions)
+- It introduces inconsequential changes (e.g. rewording phrases)
+- The author of the PR does not respond in a timely manner
+- We suspect the Github account of the author was created for airdrop farming

FUNDING.json

@@ -3,5 +3,8 @@
     "ethereum": {
       "ownedBy": "0xbF38a8Dac2AB41e72532c71fcF7Bd703432f3713"
     }
+  },
+  "opRetro": {
+    "projectId": "0x670a2982f6d7786b58a8399bcabc23246365b21e533a97945e055791fc235e64"
   }
 }

docs/README.md

@@ -37,7 +37,7 @@ To preview content locally, launch the app with `pnpm dev` and open http://127.0
 All content is organized by hierarchy levels and the top-level entries are layouts. The layout represents a set of folders and provides navigation within them. Currently, a folder should belong to one of the layouts. In terms of UI, the layout is equivalent to a sidebar navigation menu with two-level items. Layout settings can be found in the `src/content/layouts.yaml` file. It contains all layouts (currently "documentation" and "tutorial"). Each layout can have the following settings:
 
 - title (optional)
-- folders - the list of folders should be included in this layout
+- folders - the list of folders that should be included in this layout
 
 ### Folders
 
@@ -70,7 +70,7 @@ All documentation content is represented by `*.md` files with Markdown syntax. B
 
 ### Redirects
 
-Redirects allow you to redirect an incoming request path to a different destination path. Redirects settings are located in `redirects.config.js` file. It exports an array of objects. Each object represents a single redirect option. We utilize [NextJS Redirects](https://nextjs.org/docs/api-reference/next.config.js/redirects) API for that.
+Redirects allow you to redirect an incoming request path to a different destination path. Redirects settings are located in `redirects.config.js` file. It exports an array of objects. Each object represents a single redirect option. We utilize [NextJS Redirects](https://nextjs.org/docs/app/api-reference/config/next-config-js/redirects) API for that.
 
 ### Tabs
 
@@ -177,7 +177,7 @@ We also deploy updated storybook on each build. You can find it on https://hardh
 
 There are two relatively independent processes in the build step:
 
-1. Generating pages themselves. We get page paths directly from the files located in the content folder. Their paths are mapped to the page routes. Layout settings don't affect to page's existence.
+1. Generating pages themselves. We get page paths directly from the files located in the content folder. Their paths are mapped to the page routes. Layout settings don't affect page existence.
 2. Generating layouts and mapping layouts to pages. For that, we're checking which folders belong to what layout and assigning that layout to a page
 
 Page paths are generated in the `getStaticPaths` functions in files of the `page` folder. The result of these functions is an array of page paths. Page props are generated with the `getStaticProps` function, which is executed once per page with a page path passed as an argument and returns all required page props.
@@ -186,11 +186,11 @@ Execution of `getStaticPaths` and `getStaticProps` is handled by NextJS on a bui
 
 ## Styling
 
-We utilize [Linaria](https://github.com/callstack/linaria) for styling components. It has the "Styled Components" syntax but generates css without runtime with works fine with SSG sites.
+We utilize [Linaria](https://github.com/callstack/linaria) for styling components. It has the "Styled Components" syntax but generates css without runtime which works fine with SSG sites.
 
 ## Theming
 
-The documentation section is Themable. A user can switch between light, dark and high contrast themes for their convenience. There is also an "Auto" setting when theme is selected based on a user system settings.
+The documentation section is Themeable. A user can switch between light, dark and high contrast themes for their convenience. There is also an "Auto" setting when theme is selected based on a user system settings.
 
 Theming solution provides abilities to switch themes, keep the selected value in user's local storage, seamlessly keep selected page on navigating and page refreshing.
 
@@ -200,7 +200,7 @@ Landing pages don't support themes.
 
 ## Creating new landings
 
-Landing pages contains special "blocks" see src/components/landingBlocks. To create a new landing page start from copying `/pages/index.tsx` and `src/content/home.ts`. You can create another page by reordering existing blocks and passing another content to them. If necessary create new landing blocks.
+Landing pages contain special "blocks" see src/components/landingBlocks. To create a new landing page start from copying `/pages/index.tsx` and `src/content/home.ts`. You can create another page by reordering existing blocks and passing another content to them. If necessary create new landing blocks.
 
 ## CI/CD