Skip to content
This repository has been archived by the owner on Aug 1, 2023. It is now read-only.

aegir release broken by TS errors #389

Closed
lidel opened this issue Oct 25, 2021 · 1 comment
Closed

aegir release broken by TS errors #389

lidel opened this issue Oct 25, 2021 · 1 comment
Labels
need/triage Needs initial labeling and prioritization

Comments

@lidel
Copy link
Member

lidel commented Oct 25, 2021

@achingbrain fysa I had to make a patch release of ipfs-interop with (#388) but release and build failed on aegir ts -p check and if I disable TS it fails later on docs' generation.

As this is an internally consumed project, I ended up running npx aegir release --type patch --types false --lint false --docs false and the release push was successful.
Then I realized that aegir was not used for a while in this repo 🙃 hopefully it's not a big deal, but filled this issue for visibility.

@lidel lidel added the need/triage Needs initial labeling and prioritization label Oct 25, 2021
@lidel
Copy link
Member Author

lidel commented Oct 25, 2021

nvm, I realized go-ipfs needs entire root to be on NPM and published v7.0.5 that follows that convention.
Closing this. I clarified release process in README (1d52b9e)

@lidel lidel closed this as completed Oct 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

1 participant