chore: Update references from GCS buckets to new storage paths #537
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changelogs
https://storage.googleapis.com/graphium-public/
tohttps://storage.valencelabs.com/graphium/
https://storage.googleapis.com/datasets-public-research/
tohttps://storage.valencelabs.com/datasets-public-research/
gs
ands3
protocol URL for both buckets to usehttp
protocol insteadChecklist:
Was this PR discussed in an issue? It is recommended to first discuss a new feature into a GitHub issue before opening a PR.Add tests to cover the fixed bug(s) or the new introduced feature(s) (if appropriate).Update the API documentation is a new function is added, or an existing one is deleted.feature
,fix
ortest
(or ask a maintainer to do it for you).Both public GCS buckets (
graphium-public
anddatasets-public-research
) are being retired on May 30th 2025, and the existing links will cease to function. All the data was replicated as-is to a new public storage location, accessible using HTTP URLs with the prefixhttps://storage.valencelabs.com/
.