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.

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

Snap publishing broken again #1814

Closed
lidel opened this issue May 4, 2021 · 1 comment
Closed

Snap publishing broken again #1814

lidel opened this issue May 4, 2021 · 1 comment
Labels
effort/hours Estimated to take one or several hours exp/intermediate Prior experience is likely helpful kind/bug A bug in existing code (including security flaws) 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 May 4, 2021

https://github.com/ipfs/ipfs-desktop/runs/2504696837

Would be cool to also tackle #1774, but that could be a separate PR.

@lidel lidel added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization kind/maintenance Work required to avoid breaking changes or harm to project's status quo labels May 4, 2021
@lidel lidel added effort/hours Estimated to take one or several hours exp/expert Having worked on the specific codebase is important P1 High: Likely tackled by core team if no one steps up exp/intermediate Prior experience is likely helpful and removed exp/expert Having worked on the specific codebase is important need/triage Needs initial labeling and prioritization labels May 14, 2021
@lidel
Copy link
Member Author

lidel commented Jun 17, 2021

Fixed in #1845, v0.15.1 is at https://snapcraft.io/ipfs-desktop

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/hours Estimated to take one or several hours exp/intermediate Prior experience is likely helpful kind/bug A bug in existing code (including security flaws) 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
Development

No branches or pull requests

1 participant