You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We report the deployed version of the bootstrapper on the dashboard:
It's always one version behind the latest npm release, because publishing the docker container takes place in a different GH workflow to publishing the npm module, and you can't make one workflow depend on another.
We solved this problem ages ago for js-ipfs - the js-test-and-release workflow logs us in to a docker registry before calling npm run release, and then we'd do the npm release and the docker push from npm scripts, e.g.:
{
"scripts": {
"release": "npm run release:npm && npm run release:docker",
"release:npm": "... do npm things",
"release:docker": "... do docker things"
}
}
Perhaps we should do something similar here?
The text was updated successfully, but these errors were encountered:
We report the deployed version of the bootstrapper on the dashboard:
It's always one version behind the latest npm release, because publishing the docker container takes place in a different GH workflow to publishing the npm module, and you can't make one workflow depend on another.
We solved this problem ages ago for js-ipfs - the js-test-and-release workflow logs us in to a docker registry before calling
npm run release
, and then we'd do the npm release and the docker push from npm scripts, e.g.:Perhaps we should do something similar here?
The text was updated successfully, but these errors were encountered: