Skip to content

Commit d6ae2e9

Browse files
robertagorarobertagora
authored
Merge branch 'main' into new_docs_update
2 parents ae54e28 + 2683687 commit d6ae2e9

File tree

19 files changed

+198
-41
lines changed

19 files changed

+198
-41
lines changed

‎.github/workflows/update-versions.yml

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
name: Update Lotus Version
2+
3+
on:
4+
workflow_dispatch: # Allows manual trigger
5+
pull_request:
6+
types: [opened, reopened]
7+
8+
jobs:
9+
update-version:
10+
runs-on: ubuntu-latest
11+
steps:
12+
- uses: actions/checkout@v4
13+
14+
- name: Setup Node.js
15+
uses: actions/setup-node@v4
16+
with:
17+
node-version: '18'
18+
19+
- name: Get latest Lotus version
20+
id: get-version
21+
run: |
22+
# Get all releases and find the first one starting with 'v'
23+
RELEASE_INFO=$(curl -s "https://api.github.com/repos/filecoin-project/lotus/releases" | \
24+
jq -r '[.[] | select(.tag_name | startswith("v"))] | first')
25+
26+
# Extract the tag name
27+
TAG_NAME=$(echo "$RELEASE_INFO" | jq -r .tag_name)
28+
29+
# Extract version number (remove 'v' prefix)
30+
LATEST_VERSION=$(echo $TAG_NAME | sed 's/^v//')
31+
32+
echo "LATEST_VERSION=$LATEST_VERSION" >> $GITHUB_ENV
33+
echo "TAG_NAME=$TAG_NAME" >> $GITHUB_ENV
34+
35+
- name: Run update script
36+
run: |
37+
node update-versions.js ${{ env.LATEST_VERSION }}
38+
39+
- name: Create Pull Request
40+
uses: peter-evans/create-pull-request@v5
41+
with:
42+
commit-message: 'Chore: update Lotus version references to ${{ env.LATEST_VERSION }}'
43+
title: 'Chore: update Lotus version references to ${{ env.LATEST_VERSION }}'
44+
body: |
45+
Automated PR to update Lotus version references to ${{ env.LATEST_VERSION }}
46+
47+
This PR was automatically generated by GitHub Actions.
48+
branch: update-lotus-version
49+
base: main
50+
delete-branch: true

‎builder-cookbook/dapps/chain-data-query.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -30,8 +30,8 @@ We will use `ethers.js` to establish a connection with the public Filecoin node
3030
import { ethers } from "ethers"
3131

3232
//The public Filecoin calibration URL
33-
const fielcoin_url = 'https://api.calibration.node.glif.io/rpc/v1'
34-
const provider = new ethers.JsonRpcProvider(fielcoin_url)
33+
const filecoin_url = 'https://api.calibration.node.glif.io/rpc/v1'
34+
const provider = new ethers.JsonRpcProvider(filecoin_url)
3535

3636
const blockNumber = await provider.getBlockNumber()
3737
console.log("Block height: ", blockNumber)
@@ -69,8 +69,8 @@ import { ethers } from "ethers"
6969
const wFILAddress = "0xaC26a4Ab9cF2A8c5DBaB6fb4351ec0F4b07356c4" // wFIL Contract
7070
var abi = ["event Transfer(address indexed from, address indexed to, uint amount)"]
7171

72-
const fielcoin_url = 'https://api.calibration.node.glif.io/rpc/v1'
73-
const provider = new ethers.providers.JsonRpcProvider(fielcoin_url)
72+
const filecoin_url = 'https://api.calibration.node.glif.io/rpc/v1'
73+
const provider = new ethers.providers.JsonRpcProvider(filecoin_url)
7474

7575
//listen to the Transfer events in the Token contract
7676
const wFIL = new ethers.Contract(wFILAddress, abi, provider)
@@ -110,8 +110,8 @@ import { ethers } from "ethers"
110110
const wFILAddress = "0xaC26a4Ab9cF2A8c5DBaB6fb4351ec0F4b07356c4" // wFIL Contract
111111
var abi = ["event Transfer(address indexed from, address indexed to, uint amount)"]
112112

113-
const fielcoin_url = 'https://api.calibration.node.glif.io/rpc/v1'
114-
const provider = new ethers.providers.JsonRpcProvider(fielcoin_url)
113+
const filecoin_url = 'https://api.calibration.node.glif.io/rpc/v1'
114+
const provider = new ethers.providers.JsonRpcProvider(filecoin_url)
115115

116116
// Create a filter to list all token transfers from myAddress
117117
const filter = contract.filters.Transfer("0xd388aB098ed3E84c0D808776440B48F685198498");

‎builder-cookbook/dapps/decentralized-database.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ To track all the deal aggregation/RaaS requests submitted to the smart contract,
4444

4545
```solidity
4646
uint256 private tableId;
47-
string private constant _TABLE_PREFIX = "aggregaor_table"; // Custom table prefix
47+
string private constant _TABLE_PREFIX = "aggregator_table"; // Custom table prefix
4848
4949
// Constructor that creates a table, sets the controller, and inserts data
5050
constructor() {

‎nodes/full-nodes/basic-setup.md

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -12,31 +12,29 @@ To install Lotus on your computer, follow these steps:
1212
2. Once you have downloaded the binary file, extract the contents to a directory of your choice. For example, if you are using Linux, you can extract the contents to the `/usr/local/bin directory` by running the command:
1313

1414
```sh
15-
sudo tar -C /usr/local/bin -xzf lotus-X.X.X-linux-amd64.tar.gz
15+
sudo tar -C /usr/local/bin -xzf lotus-1.31.1-linux-amd64.tar.gz
1616
```
1717

18-
3. Replace `X.X.X` with the version number of the release you downloaded.
19-
4. After extracting the contents, navigate to the `lotus` directory in your terminal. For example, if you extracted the contents to `/usr/local/bin`, you can navigate to the lotus directory by running the command:
18+
3. After extracting the contents, navigate to the `lotus` directory in your terminal. For example, if you extracted the contents to `/usr/local/bin`, you can navigate to the lotus directory by running the command:
2019

2120
```sh
22-
cd /usr/local/bin/lotus-X.X.X
21+
cd /usr/local/bin/lotus-1.31.1
2322
```
2423

25-
5. Again, replace `X.X.X` with the version number of the release you downloaded.
26-
6. Run the `lotus` binary file to start the Lotus daemon. You can do this by running the command:
24+
4. Run the `lotus` binary file to start the Lotus daemon. You can do this by running the command:
2725

2826
```sh
2927
./lotus daemon
3028
```
3129

32-
7. This will start the Lotus daemon, which will connect to the Filecoin network and start synchronizing with other nodes on the network.
33-
8. Optionally, you can also run the lotus-miner binary file if you want to participate in the Filecoin mining process. You can do this by running the command:
30+
5. This will start the Lotus daemon, which will connect to the Filecoin network and start synchronizing with other nodes on the network.
31+
6. Optionally, you can also run the lotus-miner binary file if you want to participate in the Filecoin mining process. You can do this by running the command:
3432

3533
```sh
3634
./lotus-miner run
3735
```
3836

39-
9. This will start the Lotus miner, which will use your computer’s computing power to mine new blocks on the Filecoin network.
37+
7. This will start the Lotus miner, which will use your computer’s computing power to mine new blocks on the Filecoin network.
4038

4139

4240

‎nodes/lite-nodes/spin-up-a-lite-node.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -73,12 +73,12 @@ Before we can build the Lotus binaries, we need to follow a few pre-build steps.
7373
This should output something like:
7474

7575
```output
76-
v1.29.0
76+
v1.31.1
7777
```
7878
3. Using the value returned from the previous command, checkout to the latest release branch:
7979

8080
```shell
81-
git checkout v1.29.0
81+
git checkout v1.31.1
8282
```
8383
4. Done! You can move on to the [Build](https://docs.filecoin.io/nodes/lite-nodes/spin-up-a-lite-node/#build-the-binary) section.
8484
{% endtab %}
@@ -99,12 +99,12 @@ Before we can build the Lotus binaries, we need to follow a few pre-build steps.
9999
This should output something like:
100100

101101
```output
102-
v1.29.0
102+
v1.31.1
103103
```
104104
3. Using the value returned from the previous command, checkout to the latest release branch:
105105

106106
```shell
107-
git checkout v1.29.0
107+
git checkout v1.31.1
108108
```
109109
4. Create the necessary environment variables to allow Lotus to run on M1 architecture:
110110

@@ -132,12 +132,12 @@ Before we can build the Lotus binaries, we need to follow a few pre-build steps.
132132
This should output something like:
133133

134134
```output
135-
v1.29.0
135+
v1.31.1
136136
```
137137
3. Using the value returned from the previous command, checkout to the latest release branch:
138138

139139
```shell
140-
git checkout v1.29.0
140+
git checkout v1.31.1
141141
```
142142
4. If your processor was released later than an AMD Zen or Intel Ice Lake CPU, enable SHA extensions by adding these two environment variables. If in doubt, ignore this command and move on to [the next section](https://docs.filecoin.io/nodes/lite-nodes/spin-up-a-lite-node/#build-the-binary).
143143

@@ -175,7 +175,7 @@ The last thing we need to do to get our node setup is to build the package. The
175175
This will output something like:
176176

177177
```plaintext
178-
lotus version 1.29.0+mainnet+git.1ff3b360b
178+
lotus version 1.31.1+mainnet+git.1ff3b360b
179179
```
180180
{% endtab %}
181181

@@ -200,7 +200,7 @@ The last thing we need to do to get our node setup is to build the package. The
200200
This will output something like:
201201

202202
```plaintext
203-
lotus version 1.29.0+calibnet+git.1ff3b360b
203+
lotus version 1.31.1+calibnet+git.1ff3b360b
204204
```
205205
{% endtab %}
206206
{% endtabs %}

‎package.json

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
{
2+
"name": "filecoin-docs",
3+
"version": "1.0.0",
4+
"description": "<div align=center>",
5+
"main": "update-versions.js",
6+
"scripts": {
7+
"test": "echo \"Error: no test specified\" && exit 1",
8+
"update-versions": "node update-versions.js"
9+
},
10+
"repository": {
11+
"type": "git",
12+
"url": "git+https://github.com/filecoin-project/filecoin-docs.git"
13+
},
14+
"keywords": [],
15+
"author": "",
16+
"license": "ISC",
17+
"bugs": {
18+
"url": "https://github.com/filecoin-project/filecoin-docs/issues"
19+
},
20+
"homepage": "https://github.com/filecoin-project/filecoin-docs#readme"
21+
}

‎reference/built-in-actors/protocol-api.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1181,7 +1181,7 @@ Results:
11811181

11821182
## Verified registry actor
11831183

1184-
Verified registry actor is responsible for managing verified clients. The ActorCode for the verified registry built-in actor is `hex"0006"` which will be used to call the exported methods in the verified registry built-in actor. You need to specify the method number for the method you want to invoke. Please referer to each method for its method number.
1184+
Verified registry actor is responsible for managing verified clients. The ActorCode for the verified registry built-in actor is `hex"0006"` which will be used to call the exported methods in the verified registry built-in actor. You need to specify the method number for the method you want to invoke. Please refer to each method for its method number.
11851185

11861186
### AddVerifiedClient
11871187

@@ -1273,7 +1273,7 @@ Params:
12731273
* `struct` ExtendClaimTermsParams
12741274
* `struct ClaimTerm[]` Terms
12751275
* `uint64` Provider - The provider address which stores the data.
1276-
* `uint64` CliamID - Claim ID.
1276+
* `uint64` ClaimID - Claim ID.
12771277
* `int64` TermMax - The max chain epoch to extend.
12781278

12791279
Results:

‎reference/general/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ Developer tools, API clients & storage services that developers can use to build
7575

7676
### Storage APIs for app builders
7777

78-
* [Lighthouse](https://www.lighthouse.storage/) - Lighthouse offers a suite of tools to enable builders to store data on Filecoin when biulding apps.
78+
* [Lighthouse](https://www.lighthouse.storage/) - Lighthouse offers a suite of tools to enable builders to store data on Filecoin when building apps.
7979
* [`NFT.storage`](https://nft.storage/) - Preserve your NFTs with our new low-cost, easy-to-use solution, ensuring verifiable long-term storage on Filecoin.
8080
* [`Web3.storage`](https://web3.storage/) - service from Protocol Labs for storing off-chain _dApp_ data on IPFS and Filecoin, with help from Pinata (a fast IPFS Pinning Service) to [distribute the content across IPFS](https://www.pinata.cloud/blog/protocol-labs-and-pinata)
8181
* [`Textile.io's tools`](https://docs.textile.io/) - suite of tools for interacting with IPFS and Filecoin, including [Tableland](https://tableland.xyz/) and Filecoin bridges to Polygon and NEAR.

‎reference/json-rpc/client.md

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

33
{% hint style="warning" %}
4-
The Client methods are now deprecated and have been removed from Lotus (the Filecoin reference implemenation).
4+
The Client methods are now deprecated and have been removed from Lotus (the Filecoin reference implementation).
55
{% endhint %}
66

77
Some similar functionality can be found by using the [Boostly](https://github.com/filecoin-shipyard/boostly) library, which interacts with market actors provided by [Boost](https://boost.filecoin.io/).

‎reference/json-rpc/create.md

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

33
## CreateBackup
44

5-
CreateBackup creates node backup onder the specified file name. The method requires that the lotus daemon is running with the LOTUS\_BACKUP\_BASE\_PATH environment variable set to some path, and that the path specified when calling CreateBackup is within the base path
5+
CreateBackup creates node backup under the specified file name. The method requires that the lotus daemon is running with the LOTUS\_BACKUP\_BASE\_PATH environment variable set to some path, and that the path specified when calling CreateBackup is within the base path
66

77
Perms: admin
88

0 commit comments

Comments
 (0)