Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CI: pin CIDs on release #91

Open
lidel opened this issue Jul 25, 2022 · 1 comment
Open

CI: pin CIDs on release #91

lidel opened this issue Jul 25, 2022 · 1 comment
Labels
effort/days Estimated to take multiple days, but less than a week exp/intermediate Prior experience is likely helpful kind/maintenance Work required to avoid breaking changes or harm to project's status quo P1 High: Likely tackled by core team if no one steps up

Comments

@lidel
Copy link
Member

lidel commented Jul 25, 2022

There should be CI set up that pins both CIDs (DATA_HASH and GEOIP_ROOT) to at least two pinning services.

This way we avoid issues like ipfs/ipfs-webui#1992
@lidel lidel added P1 High: Likely tackled by core team if no one steps up kind/maintenance Work required to avoid breaking changes or harm to project's status quo exp/intermediate Prior experience is likely helpful effort/days Estimated to take multiple days, but less than a week labels Jul 25, 2022
@lidel lidel pinned this issue Jul 25, 2022
@lidel lidel mentioned this issue Jul 25, 2022
Closed
@lidel lidel unpinned this issue Oct 19, 2022
@lidel lidel mentioned this issue Oct 19, 2022
Merged
@lidel lidel mentioned this issue Nov 18, 2023
Merged
1 task
@SgtPooki
Copy link
Member

SgtPooki commented Dec 2, 2023

FYI that I added w3cli pinning support to ipfs-webui with ipfs/ipfs-webui#2182 and we could do similar here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort/days Estimated to take multiple days, but less than a week exp/intermediate Prior experience is likely helpful kind/maintenance Work required to avoid breaking changes or harm to project's status quo P1 High: Likely tackled by core team if no one steps up
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lidel @SgtPooki