chore: switch to dist.ipfs.tech
Part of https://github.com/protocol/bifrost-infra/issues/2018 ensures the domain used for fetching migrations is not impacted by ipfs.io being blocked at DNS level by some ISPs.
Marcin Rataj committed
Aug 12, 2022 at 23:03 UTC
837f6ee92b6ee00e7c7e364084fa93959073c8c7
20 files changed
+55
-55
.github/ISSUE_TEMPLATE/bug-report.yml
+2
-2
@@ -22,7 +22,7 @@ body:
22
required: true
23
- label: I have searched on the [issue tracker](https://github.com/ipfs/kubo/issues?q=is%3Aissue) for my bug.
24
required: true
25
- - label: I am running the latest [kubo version](https://dist.ipfs.io/#kubo) or have an issue updating.
25
+ - label: I am running the latest [kubo version](https://dist.ipfs.tech/#kubo) or have an issue updating.
26
required: true
27
- type: dropdown
28
id: install
@@ -33,7 +33,7 @@ body:
33
description: Please select your installation method
34
options:
35
- ipfs-desktop
36
- - ipfs-update or dist.ipfs.io
36
+ - ipfs-update or dist.ipfs.tech
37
- third-party binary
38
- built from source
39
- type: textarea
.github/workflows/sync-release-assets.yml
+7
-7
@@ -1,4 +1,4 @@
1
-name: Sync github release assets with dist.ipfs.io
1
+name: Sync github release assets with dist.ipfs.tech
2
3
on:
4
workflow_dispatch:
@@ -10,7 +10,7 @@ concurrency:
10
cancel-in-progress: true
11
12
jobs:
13
- sync-github-and-dist-ipfs-io:
13
+ sync-github-and-dist.ipfs.tech:
14
if: github.repository == 'ipfs/kubo' || github.event_name == 'workflow_dispatch'
15
runs-on: "ubuntu-latest"
16
steps:
@@ -50,8 +50,8 @@ jobs:
50
github_assets.add(asset.name)
51
}
52
53
- // fetch asset info from dist.ipfs.io
54
- p = '/ipns/dist.ipfs.io/kubo/' + release.tag_name
53
+ // fetch asset info from dist.ipfs.tech
54
+ p = '/ipns/dist.ipfs.tech/kubo/' + release.tag_name
55
let stdout = ''
56
const options = {}
57
options.listeners = {
@@ -74,7 +74,7 @@ jobs:
74
}
75
}
76
77
- // if dist.ipfs.io has files not found in github, copy them over
77
+ // if dist.ipfs.tech has files not found in github, copy them over
78
for (const file of missing_files) {
79
file_sha = file + ".sha512"
80
file_cid = file + ".cid"
@@ -82,12 +82,12 @@ jobs:
82
// skip files that don't have .cid and .sha512 checksum files
83
if (!dist_assets.has(file_sha) || !dist_assets.has(file_cid)) {
84
if (!file.endsWith('.cid') && !file.endsWith('.sha512')) { // silent skip of .sha512.sha512 :)
85
- console.log(`skipping "${file}" as dist.ipfs.io does not provide .cid and .sha512 checksum files for it`)
85
+ console.log(`skipping "${file}" as dist.ipfs.tech does not provide .cid and .sha512 checksum files for it`)
86
}
87
continue
88
}
89
90
- console.log("fetching", file, "from dist.ipfs.io")
90
+ console.log("fetching", file, "from dist.ipfs.tech")
91
await exec.exec('ipfs', ['get', p + '/' + file])
92
await exec.exec('ipfs', ['get', p + '/' + file_sha])
93
await exec.exec('ipfs', ['get', p + '/' + file_cid])
README.md
+16
-16
@@ -31,7 +31,7 @@ Before opening an issue, consider using one of the following locations to ensure
31
- Documentation issues in [ipfs/docs issues](https://github.com/ipfs/ipfs-docs/issues).
32
- IPFS _design_ in [ipfs/specs issues](https://github.com/ipfs/specs/issues).
33
- Exploration of new ideas in [ipfs/notes issues](https://github.com/ipfs/notes/issues).
34
- - Ask questions and meet the rest of the community at the [IPFS Forum](https://discuss.ipfs.io).
34
+ - Ask questions and meet the rest of the community at the [IPFS Forum](https://discuss.ipfs.tech).
35
- Or [chat with us](https://docs.ipfs.tech/community/chat/).
36
37
[](https://www.youtube.com/channel/UCdjsUXJ3QawK4O5L1kqqsew) [](https://twitter.com/IPFS)
@@ -244,16 +244,16 @@ PS> scoop install go-ipfs
244
245
### Install prebuilt binaries
246
247
-[](https://dweb.link/ipns/dist.ipfs.io#kubo)
247
+[](https://dweb.link/ipns/dist.ipfs.tech#kubo)
248
249
From there:
250
- Click the blue "Download kubo" on the right side of the page.
251
- Open/extract the archive.
252
- Move kubo (`ipfs`) to your path (`install.sh` can do it for you).
253
254
-If you are unable to access [dist.ipfs.io](https://dist.ipfs.io#kubo), you can also download kubo (go-ipfs) from:
254
+If you are unable to access [dist.ipfs.tech](https://dist.ipfs.tech#kubo), you can also download kubo (go-ipfs) from:
255
- this project's GitHub [releases](https://github.com/ipfs/kubo/releases/latest) page
256
-- `/ipns/dist.ipfs.io` at [dweb.link](https://dweb.link/ipns/dist.ipfs.io#kubo) gateway
256
+- `/ipns/dist.ipfs.tech` at [dweb.link](https://dweb.link/ipns/dist.ipfs.tech#kubo) gateway
257
258
### Build from Source
259
@@ -329,34 +329,34 @@ dependencies as well.
329
330
IPFS has an updating tool that can be accessed through `ipfs update`. The tool is
331
not installed alongside IPFS in order to keep that logic independent of the main
332
-codebase. To install `ipfs update`, [download it here](https://ipfs.io/ipns/dist.ipfs.io/#ipfs-update).
332
+codebase. To install `ipfs update`, [download it here](https://dist.ipfs.tech/#ipfs-update).
333
334
#### Downloading builds using IPFS
335
336
-<!-- TODO: rename this section after we figure out if dist.ipfs.io sgould produce both /go-ipfs/ and /kubo/ -->
336
+<!-- TODO: rename this section after we figure out if dist.ipfs.tech sgould produce both /go-ipfs/ and /kubo/ -->
337
338
List the available versions of kubo (go-ipfs) implementation:
339
340
```
341
-$ ipfs cat /ipns/dist.ipfs.io/go-ipfs/versions
341
+$ ipfs cat /ipns/dist.ipfs.tech/go-ipfs/versions
342
```
343
344
Then, to view available builds for a version from the previous command ($VERSION):
345
346
```
347
-$ ipfs ls /ipns/dist.ipfs.io/go-ipfs/$VERSION
347
+$ ipfs ls /ipns/dist.ipfs.tech/go-ipfs/$VERSION
348
```
349
350
To download a given build of a version:
351
352
```
353
-$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_darwin-386.tar.gz # darwin 32-bit build
354
-$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_darwin-amd64.tar.gz # darwin 64-bit build
355
-$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_freebsd-amd64.tar.gz # freebsd 64-bit build
356
-$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_linux-386.tar.gz # linux 32-bit build
357
-$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_linux-amd64.tar.gz # linux 64-bit build
358
-$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_linux-arm.tar.gz # linux arm build
359
-$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_windows-amd64.zip # windows 64-bit build
353
+$ ipfs get /ipns/dist.ipfs.tech/go-ipfs/$VERSION/go-ipfs_$VERSION_darwin-386.tar.gz # darwin 32-bit build
354
+$ ipfs get /ipns/dist.ipfs.tech/go-ipfs/$VERSION/go-ipfs_$VERSION_darwin-amd64.tar.gz # darwin 64-bit build
355
+$ ipfs get /ipns/dist.ipfs.tech/go-ipfs/$VERSION/go-ipfs_$VERSION_freebsd-amd64.tar.gz # freebsd 64-bit build
356
+$ ipfs get /ipns/dist.ipfs.tech/go-ipfs/$VERSION/go-ipfs_$VERSION_linux-386.tar.gz # linux 32-bit build
357
+$ ipfs get /ipns/dist.ipfs.tech/go-ipfs/$VERSION/go-ipfs_$VERSION_linux-amd64.tar.gz # linux 64-bit build
358
+$ ipfs get /ipns/dist.ipfs.tech/go-ipfs/$VERSION/go-ipfs_$VERSION_linux-arm.tar.gz # linux arm build
359
+$ ipfs get /ipns/dist.ipfs.tech/go-ipfs/$VERSION/go-ipfs_$VERSION_windows-amd64.zip # windows 64-bit build
360
```
361
362
## Getting Started
@@ -385,7 +385,7 @@ Basic proof of 'ipfs working' locally:
385
386
If you have previously installed IPFS before and you are running into problems getting a newer version to work, try deleting (or backing up somewhere else) your IPFS config directory (~/.ipfs by default) and rerunning `ipfs init`. This will reinitialize the config file to its defaults and clear out the local datastore of any bad entries.
387
388
-Please direct general questions and help requests to our [forum](https://discuss.ipfs.io) or our IRC channel (freenode #ipfs).
388
+Please direct general questions and help requests to our [forums](https://discuss.ipfs.tech).
389
390
If you believe you've found a bug, check the [issues list](https://github.com/ipfs/kubo/issues) and, if you don't see your problem there, either come talk to us on [Matrix chat](https://docs.ipfs.tech/community/chat/), or file an issue of your own!
391
cmd/ipfs/daemon.go
+1
-1
@@ -292,7 +292,7 @@ func daemonFunc(req *cmds.Request, re cmds.ResponseEmitter, env cmds.Environment
292
293
if !domigrate {
294
fmt.Println("Not running migrations of fs-repo now.")
295
- fmt.Println("Please get fs-repo-migrations from https://dist.ipfs.io")
295
+ fmt.Println("Please get fs-repo-migrations from https://dist.ipfs.tech")
296
return fmt.Errorf("fs-repo requires migration")
297
}
298
core/corehttp/hostname.go
+1
-1
@@ -324,7 +324,7 @@ func isKnownHostname(hostname string, knownGateways gatewayHosts) (gw *config.Ga
324
func knownSubdomainDetails(hostname string, knownGateways gatewayHosts) (gw *config.GatewaySpec, gwHostname, ns, rootID string, ok bool) {
325
labels := strings.Split(hostname, ".")
326
// Look for FQDN of a known gateway hostname.
327
- // Example: given "dist.ipfs.io.ipns.dweb.link":
327
+ // Example: given "dist.ipfs.tech.ipns.dweb.link":
328
// 1. Lookup "link" TLD in knownGateways: negative
329
// 2. Lookup "dweb.link" in knownGateways: positive
330
//
core/corehttp/hostname_test.go
+1
-1
@@ -261,7 +261,7 @@ func TestKnownSubdomainDetails(t *testing.T) {
261
// dnslink in subdomain
262
{"en.wikipedia-on-ipfs.org.ipns.localhost:8080", gwLocalhost, "localhost:8080", "ipns", "en.wikipedia-on-ipfs.org", true},
263
{"en.wikipedia-on-ipfs.org.ipns.localhost", gwLocalhost, "localhost", "ipns", "en.wikipedia-on-ipfs.org", true},
264
- {"dist.ipfs.io.ipns.localhost:8080", gwLocalhost, "localhost:8080", "ipns", "dist.ipfs.io", true},
264
+ {"dist.ipfs.tech.ipns.localhost:8080", gwLocalhost, "localhost:8080", "ipns", "dist.ipfs.tech", true},
265
{"en.wikipedia-on-ipfs.org.ipns.dweb.link", gwDweb, "dweb.link", "ipns", "en.wikipedia-on-ipfs.org", true},
266
// edge case check: public gateway under long TLD (see: https://publicsuffix.org)
267
{"foo.dweb.ipfs.pvt.k12.ma.us", nil, "", "", "", false},
core/node/groups.go
+1
-1
@@ -139,7 +139,7 @@ func LibP2P(bcfg *BuildCfg, cfg *config.Config) fx.Option {
139
if cfg.Swarm.EnableRelayHop {
140
logger.Fatal("The `Swarm.EnableRelayHop` config field was removed.\n" +
141
"Use `Swarm.RelayService` to configure the circuit v2 relay.\n" +
142
- "If you want to continue running a circuit v1 relay, please use the standalone relay daemon: https://dist.ipfs.io/#libp2p-relay-daemon (with RelayV1.Enabled: true)")
142
+ "If you want to continue running a circuit v1 relay, please use the standalone relay daemon: https://dist.ipfs.tech/#libp2p-relay-daemon (with RelayV1.Enabled: true)")
143
}
144
145
peerChan := make(libp2p.AddrInfoChan)
docs/PATCH_RELEASE_TEMPLATE.md
+3
-3
@@ -10,17 +10,17 @@ This process handles patch releases from version `vX.Y.Z` to `vX.Y.Z+1` assuming
10
- [ ] Make a PR merging `release-vX.Y.Z+1` into the release branch
11
- This may be unnecessary, e.g. for backports
12
- [ ] Tag the merge commit in the `release` branch with `vX.Y.Z+1` (ensure the tag is signed)
13
-- [ ] Upload to dist.ipfs.io
13
+- [ ] Upload to dist.ipfs.tech
14
1. Build: https://github.com/ipfs/distributions#usage.
15
2. Pin the resulting release.
16
3. Make a PR against ipfs/distributions with the updated versions, including the new hash in the PR comment.
17
- 4. Ask the infra team to update the DNSLink record for dist.ipfs.io to point to the new distribution.
17
+ 4. Ask the infra team to update the DNSLink record for dist.ipfs.tech to point to the new distribution.
18
- [ ] cut a release on [github](https://github.com/ipfs/kubo/releases) and upload the result of the ipfs/distributions build in the previous step.
19
- Announce the Release:
20
- [ ] On IRC/Matrix (both #ipfs and #ipfs-dev)
21
- [ ] On discuss.ipfs.io
22
- [ ] Release published
23
- - [ ] to [dist.ipfs.io](https://dist.ipfs.io)
23
+ - [ ] to [dist.ipfs.tech](https://dist.ipfs.tech)
24
- [ ] to [npm-go-ipfs](https://github.com/ipfs/npm-go-ipfs)
25
- [ ] to [chocolatey](https://chocolatey.org/packages/ipfs)
26
- [ ] to [snap](https://snapcraft.io/ipfs)
docs/RELEASE_ISSUE_TEMPLATE.md
+4
-4
@@ -24,11 +24,11 @@ For each RC published in each stage:
24
25
- version string in `version.go` has been updated (in the `release-vX.Y.Z` branch).
26
- tag commit with `vX.Y.Z-rcN`
27
-- upload to dist.ipfs.io
27
+- upload to dist.ipfs.tech
28
1. Build: https://github.com/ipfs/distributions#usage.
29
2. Pin the resulting release.
30
3. Make a PR against ipfs/distributions with the updated versions, including the new hash in the PR comment.
31
- 4. Ask the infra team to update the DNSLink record for dist.ipfs.io to point to the new distribution.
31
+ 4. Ask the infra team to update the DNSLink record for dist.ipfs.tech to point to the new distribution.
32
- cut a pre-release on [github](https://github.com/ipfs/kubo/releases) and upload the result of the ipfs/distributions build in the previous step.
33
- Announce the RC:
34
- [ ] On Matrix (both #ipfs and #ipfs-dev)
@@ -79,13 +79,13 @@ Checklist:
79
- [ ] Merge `release-vX.Y.Z` into the `release` branch.
80
- [ ] Tag this merge commit (on the `release` branch) with `vX.Y.Z`.
81
- [ ] Release published
82
- - [ ] to [dist.ipfs.io](https://dist.ipfs.io)
82
+ - [ ] to [dist.ipfs.tech](https://dist.ipfs.tech)
83
- [ ] to [npm-go-ipfs](https://github.com/ipfs/npm-go-ipfs)
84
- [ ] to [chocolatey](https://chocolatey.org/packages/go-ipfs)
85
- [ ] Manually run [the release workflow](https://github.com/ipfs/choco-go-ipfs/actions/workflows/main.yml)
86
- [ ] to [snap](https://snapcraft.io/ipfs)
87
- [ ] to [github](https://github.com/ipfs/go-ipfs/releases)
88
- - [ ] use the artifacts built in CI for dist.ipfs.io: `wget "https://ipfs.io/api/v0/get?arg=/ipns/dist.ipfs.io/kubo/$(curl -s https://dist.ipfs.io/kubo/versions | tail -n 1)"`
88
+ - [ ] reuse signed artifacts from https://dist.ipfs.tech/kubo (run [sync-release-assets.yml workflow](https://github.com/ipfs/kubo/actions/workflows/sync-release-assets.yml))
89
- [ ] to [arch](https://www.archlinux.org/packages/community/x86_64/go-ipfs/) (flag it out of date)
90
- [ ] Cut a new ipfs-desktop release
91
- [ ] Submit [this form](https://airtable.com/shrNH8YWole1xc70I) to publish a blog post, linking to the GitHub release notes
docs/changelogs/v0.11.md
+1
-1
@@ -73,7 +73,7 @@ Switching to v2 of the relay spec means removal or deprecation of configuration
73
- `Swarm.DisableRelay` is deprecated, relay transport can be now disabled globally (both client and service) by setting `Swarm.Transports.Network.Relay` to `false`
74
- Relay v1 service provider was replaced by v2:
75
- `Swarm.EnableRelayHop` no longer starts an unlimited v1 relay. If you have it set to `true` the node will refuse to start and display an error message.
76
- - Existing users who choose to continue running a v1 relay should migrate their setups to relay v1 based on js-ipfs running in node, or the standalone [libp2p-relay-daemon](https://dist.ipfs.io/#libp2p-relay-daemon) [configured](https://github.com/libp2p/go-libp2p-relay-daemon/#configuration) with `RelayV1.Enabled` set to `true`. Be mindful that v1 relays are unlimited, and one may want to set up some ACL based either on PeerIDs or Subnets.
76
+ - Existing users who choose to continue running a v1 relay should migrate their setups to relay v1 based on js-ipfs running in node, or the standalone [libp2p-relay-daemon](https://dist.ipfs.tech/#libp2p-relay-daemon) [configured](https://github.com/libp2p/go-libp2p-relay-daemon/#configuration) with `RelayV1.Enabled` set to `true`. Be mindful that v1 relays are unlimited, and one may want to set up some ACL based either on PeerIDs or Subnets.
77
78
#### 🕳 Decentralized Hole Punching (DCUtR protocol client)
79
docs/changelogs/v0.12.md
+3
-3
@@ -58,7 +58,7 @@ As usual, this release includes important fixes, some of which may be critical f
58
59
- `ipfs refs local` will now list all blocks as if they were [raw]() CIDv1 instead of with whatever CID version and IPLD codecs they were stored with. All other functionality should remain the same.
60
61
-Note: This change also effects [ipfs-update](https://github.com/ipfs/ipfs-update) so if you use that tool to mange your go-ipfs installation then grab ipfs-update v1.8.0 from [dist](https://dist.ipfs.io/#ipfs-update).
61
+Note: This change also effects [ipfs-update](https://github.com/ipfs/ipfs-update) so if you use that tool to mange your go-ipfs installation then grab ipfs-update v1.8.0 from [dist](https://dist.ipfs.tech/#ipfs-update).
62
63
Keep reading to learn more details.
64
@@ -127,7 +127,7 @@ It is also possible to revert the migration after it has succeeded, for example
127
128
The revert process does not delete any blocks--it only makes sure that blocks that were accessible with CIDv1s before the migration are again keyed with CIDv1s. This may result in a datastore becoming twice as large (i.e. if all the blocks were CIDv1-addressed before the migration). This is however done this way to cover corner cases: user can add CIDv1s after migration, which may reference blocks that existed as CIDv0 before migration. The revert aims to ensure that no data becomes unavailable on downgrade.
129
130
-While go-ipfs will auto-run the migration for you, it will not run the reversion. To do so you can download the [latest migration binary](https://dist.ipfs.io/fs-repo-11-to-12) or use [ipfs-update](https://dist.ipfs.io/#ipfs-update).
130
+While go-ipfs will auto-run the migration for you, it will not run the reversion. To do so you can download the [latest migration binary](https://dist.ipfs.tech/fs-repo-11-to-12) or use [ipfs-update](https://dist.ipfs.tech/#ipfs-update).
131
132
###### Custom datastores
133
@@ -140,7 +140,7 @@ For this migration, if your datastore has fast renames you may want to consider
140
- github.com/ipfs/go-ipfs:
141
- Release v0.12.0
142
- docs: v0.12.0 release notes
143
- - chore: bump migrations dist.ipfs.io CID to contain fs-repo-11-to-12 v1.0.2
143
+ - chore: bump migrations dist.ipfs.tech CID to contain fs-repo-11-to-12 v1.0.2
144
- feat: refactor Fetcher interface used for downloading migrations (#8728) ([ipfs/go-ipfs#8728](https://github.com/ipfs/go-ipfs/pull/8728))
145
- feat: log multifetcher errors
146
- Release v0.12.0-rc1
docs/changelogs/v0.14.md
+2
-2
@@ -51,13 +51,13 @@ We've renamed Go-IPFS to Kubo ([details](https://github.com/ipfs/go-ipfs/issues/
51
52
Published artifacts use `kubo` now, and are available at:
53
54
-- https://dist.ipfs.io/kubo/
54
+- https://dist.ipfs.tech/kubo/
55
- https://hub.docker.com/r/ipfs/kubo/
56
57
To minimize the impact on infrastructure that autoupdates on a new release,
58
the same binaries are still published under the old name at:
59
60
-- https://dist.ipfs.io/go-ipfs/
60
+- https://dist.ipfs.tech/go-ipfs/
61
- https://hub.docker.com/r/ipfs/go-ipfs/
62
63
The libp2p identify useragent of Kubo has also been changed from `go-ipfs` to `kubo`.
docs/changelogs/v0.4.md
+4
-4
@@ -1237,7 +1237,7 @@ To initialize a go-ipfs instance with a randomly chosen port, run:
1237
#### 👂 Gateway Directory Listing
1238
1239
IPNS (and/or DNSLink) directory listings on the gateway, e.g.
1240
-https://ipfs.io/ipns/dist.ipfs.io/go-ipfs/, will now display the _ipfs_ hash of
1240
+https://ipfs.io/ipns/dist.ipfs.tech/go-ipfs/, will now display the _ipfs_ hash of
1241
the current directory. This way users can more easily create permanent links to
1242
otherwise mutable data.
1243
@@ -3705,7 +3705,7 @@ This is the first Release Candidate. Unless there are vulnerabilities or regress
3705
- Security Vulnerability
3706
3707
- The `master` branch if go-ipfs suffered from a vulnerability for about 3 weeks. It allowed an attacker to use an iframe to request malicious HTML and JS from the API of a local go-ipfs node. The attacker could then gain unrestricted access to the node's API, and e.g. extract the private key. We fixed this issue by reintroducing restrictions on which particular objects can be loaded through the API (@lgierth, [ipfs/go-ipfs#2949](https://github.com/ipfs/go-ipfs/pull/2949)), and by completely excluding the private key from the API (@Kubuxu, [ipfs/go-ipfs#2957](https://github.com/ipfs/go-ipfs/pull/2957)). We will also work on more hardening of the API in the next release.
3708
- - **The previous release 0.4.2 is not vulnerable. That means if you're using official binaries from [dist.ipfs.io](https://dist.ipfs.io) you're not affected.** If you're running go-ipfs built from the `master` branch between June 17th ([ipfs/go-ipfs@1afebc21](https://github.com/ipfs/go-ipfs/commit/1afebc21f324982141ca8a29710da0d6f83ca804)) and July 7th ([ipfs/go-ipfs@39bef0d5](https://github.com/ipfs/go-ipfs/commit/39bef0d5b01f70abf679fca2c4d078a2d55620e2)), please update to v0.4.3-rc1 immediately.
3708
+ - **The previous release 0.4.2 is not vulnerable. That means if you're using official binaries from [dist.ipfs.tech](https://dist.ipfs.tech) you're not affected.** If you're running go-ipfs built from the `master` branch between June 17th ([ipfs/go-ipfs@1afebc21](https://github.com/ipfs/go-ipfs/commit/1afebc21f324982141ca8a29710da0d6f83ca804)) and July 7th ([ipfs/go-ipfs@39bef0d5](https://github.com/ipfs/go-ipfs/commit/39bef0d5b01f70abf679fca2c4d078a2d55620e2)), please update to v0.4.3-rc1 immediately.
3709
- We are grateful to the group of independent researchers who made us aware of this vulnerability. We wanna use this opportunity to reiterate that we're very happy about any additional review of pull requests and releases. You can contact us any time at security@ipfs.io (GPG [4B9665FB 92636D17 7C7A86D3 50AAE8A9 59B13AF3](https://pgp.mit.edu/pks/lookup?op=get&search=0x50AAE8A959B13AF3)).
3710
3711
- Notable changes
@@ -3860,12 +3860,12 @@ There are also a few other nice improvements.
3860
* Update gx and gx-go. (@chriscool)
3861
* Make blocks.Block an interface. (@kevina)
3862
* Silence check for Docker existance. (@chriscool)
3863
- * Add dist_get script for fetching tools from dist.ipfs.io. (@whyrusleeping)
3863
+ * Add dist_get script for fetching tools from dist.ipfs.tech. (@whyrusleeping)
3864
* Add proper defaults to all `ipfs` commands. (@richardlitt)
3865
* Remove dead `count` option from `ipfs pin ls`. (@richardlitt)
3866
* Initialize pin mode strings only once. (@chriscool)
3867
* Add changelog for v0.4.2. (@lgierth)
3868
- * Specify a dist.ipfs.io hash for tool downloads instead of trusting DNS. (@lgierth)
3868
+ * Specify a dist.ipfs.tech hash for tool downloads instead of trusting DNS. (@lgierth)
3869
3870
* CI
3871
* Fix t0170-dht sharness test. (@chriscool)
docs/changelogs/v0.5.md
+1
-1
@@ -514,7 +514,7 @@ In general, migrations should not require significant manual intervention. Howev
514
* If you update go-ipfs with `ipfs update`, `ipfs update` will run the migration for you. Note: `ipfs update` will refuse to run the migrations while ipfs itself is running.
515
* If you start the ipfs daemon with `ipfs daemon --migrate`, ipfs will migrate your repo for you on start.
516
517
-Otherwise, if you want more control over the repo migration process, you can manually install and run the [repo migration tool](http://dist.ipfs.io/#fs-repo-migrations).
517
+Otherwise, if you want more control over the repo migration process, you can manually install and run the [repo migration tool](http://dist.ipfs.tech/#fs-repo-migrations).
518
519
##### Bootstrap Peer Changes
520
docs/changelogs/v0.7.md
+2
-2
@@ -51,9 +51,9 @@ Size: 30362191, NumBlocks: 346
51
52
#### Plugin build changes
53
54
-We have changed the build flags used by the official binary distributions on dist.ipfs.io (or `/ipns/dist.ipfs.io`) to use the simpler and more reliable `-trimpath` flag instead of the more complicated and brittle `-asmflags=all=-trimpath="$(GOPATH)" -gcflags=all=-trimpath="$(GOPATH)"` flags, however the build flags used by default in go-ipfs remain the same.
54
+We have changed the build flags used by the official binary distributions on dist.ipfs.tech (or `/ipns/dist.ipfs.tech`) to use the simpler and more reliable `-trimpath` flag instead of the more complicated and brittle `-asmflags=all=-trimpath="$(GOPATH)" -gcflags=all=-trimpath="$(GOPATH)"` flags, however the build flags used by default in go-ipfs remain the same.
55
56
-The scripts in https://github.com/ipfs/go-ipfs-example-plugin have been updated to reflect this change. This is a breaking change to how people have been building plugins against the dist.ipfs.io binary of go-ipfs and plugins should update their build processes accordingly see https://github.com/ipfs/go-ipfs-example-plugin/pull/9 for details.
56
+The scripts in https://github.com/ipfs/go-ipfs-example-plugin have been updated to reflect this change. This is a breaking change to how people have been building plugins against the dist.ipfs.tech binary of go-ipfs and plugins should update their build processes accordingly see https://github.com/ipfs/go-ipfs-example-plugin/pull/9 for details.
57
58
### Changelog
59
docs/changelogs/v0.9.md
+1
-1
@@ -136,7 +136,7 @@ This means faster download times for upgrades, a much easier time building migra
136
137
##### Configurable migration downloads enable downloading over IPFS
138
139
-Previously the migration downloader built into go-ipfs downloaded the migrations from [dist.ipfs.io](https://dist.ipfs.io). While users could use tools like [ipfs-update](https://github.com/ipfs/ipfs-update) to download the migrations over IPFS or manually download the migrations (over IPFS or otherwise) themselves, this is now automated and configurable. Users can choose to download the migrations over IPFS or from any specified IPFS Gateway.
139
+Previously the migration downloader built into go-ipfs downloaded the migrations from [dist.ipfs.tech](https://dist.ipfs.tech). While users could use tools like [ipfs-update](https://github.com/ipfs/ipfs-update) to download the migrations over IPFS or manually download the migrations (over IPFS or otherwise) themselves, this is now automated and configurable. Users can choose to download the migrations over IPFS or from any specified IPFS Gateway.
140
141
The configurable migration options are described in the config file [documentation](https://github.com/ipfs/go-ipfs/blob/master/docs/config.md#migration), although most users should not need to change the default settings.
142
docs/windows.md
+1
-1
@@ -1,7 +1,7 @@
1
# Building on Windows
2
3
4
-If you just want to install kubo, please download it from https://dist.ipfs.io/#kubo. This document explains how to build it from source.
4
+If you just want to install kubo, please download it from https://dist.ipfs.tech/#kubo. This document explains how to build it from source.
5
6
## Install Go
7
`kubo` is built on Golang and thus depends on it for all building methods.
repo/fsrepo/migrations/fetch.go
+1
-1
@@ -173,7 +173,7 @@ func osWithVariant() (string, error) {
173
174
// makeArchivePath composes the path, relative to the distribution site, from which to
175
// download a binary. The path returned does not contain the distribution site path,
176
-// e.g. "/ipns/dist.ipfs.io/", since that is know to the fetcher.
176
+// e.g. "/ipns/dist.ipfs.tech/", since that is know to the fetcher.
177
//
178
// Returns the archive path and the base name.
179
//
repo/fsrepo/migrations/fetcher.go
+1
-1
@@ -13,7 +13,7 @@ const (
13
// Current distribution to fetch migrations from
14
CurrentIpfsDist = "/ipfs/QmdaCHYBDHEhXCMoynH5UcohEay6m1XayZCcxWZzKAHNVN" // fs-repo-11-to-12 v1.0.2
15
// Latest distribution path. Default for fetchers.
16
- LatestIpfsDist = "/ipns/dist.ipfs.io"
16
+ LatestIpfsDist = "/ipns/dist.ipfs.tech"
17
18
// Distribution environ variable
19
envIpfsDistPath = "IPFS_DIST_PATH"
test/sharness/t0066-migration.sh
+2
-2
@@ -58,7 +58,7 @@ test_expect_success "ipfs daemon --migrate=false fails" '
58
'
59
60
test_expect_success "output looks good" '
61
- grep "Please get fs-repo-migrations from https://dist.ipfs.io" false_out
61
+ grep "Please get fs-repo-migrations from https://dist.ipfs.tech" false_out
62
'
63
64
# The migrations will succeed, but the daemon will still exit with 1 because
@@ -81,7 +81,7 @@ test_expect_success "'ipfs daemon' prompts to auto migrate" '
81
test_expect_success "output looks good" '
82
grep "Found outdated fs-repo" daemon_out > /dev/null &&
83
grep "Run migrations now?" daemon_out > /dev/null &&
84
- grep "Please get fs-repo-migrations from https://dist.ipfs.io" daemon_out > /dev/null
84
+ grep "Please get fs-repo-migrations from https://dist.ipfs.tech" daemon_out > /dev/null
85
'
86
87
test_expect_success "ipfs repo migrate succeed" '