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

Marketplace version is outdated #104

Open
20k-ultra opened this issue Feb 10, 2022 · 5 comments · Fixed by #107
Open

Marketplace version is outdated #104

20k-ultra opened this issue Feb 10, 2022 · 5 comments · Fixed by #107

Comments

@20k-ultra
Copy link
Contributor

Marketplace shows v0.4.7 which is currently the only release but we have tags. Should we automate the release creation so that the marketplace gets new versions ?

I was hoping the tags (which work wonderfully) would updated the marketplace.

@20k-ultra
Copy link
Contributor Author

@klutchell thoughts?

@klutchell
Copy link
Collaborator

We could always add a new GH workflow to create a release whenever a tag is pushed by versionbot. Unless versionbot has this feature built in but I can't find it if it does.

Some example actions, but we could test a few and inspect the source code:

@klutchell
Copy link
Collaborator

If we fix the broken resinCI builds mentioned in #106 we can make sure the release is created by resin-deploy.
https://github.com/product-os/scripts/blob/master/github/store-github-release.sh

FD thread (restricted): https://www.flowdock.com/app/rulemotion/d-build-pipelines/threads/F2mD2ZLA0gEBC2fGhSMHtqCMxPV

@klutchell
Copy link
Collaborator

WIP to update resinCI to support GH releases for node repos (private repo):
https://github.com/product-os/balena-concourse/pull/640

@klutchell
Copy link
Collaborator

Flowzone v5.12.10 only creates GitHub releases when there are artifacts to publish. We need to consider how to enable this conditionally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants