Automate block publishing to balenaHub about starter-interface HOT 3 CLOSED

Is there a way to fix to a specific version when adding a Balena Cloud image to a Dockerfile

Yeah, but it would be bh.cr/maggie0002/balena-device-ui/0.0.1, more info here.

Thanks for the pointer about that PR!

from starter-interface.

Yes, great idea, thanks for adding the issue.

Is there a way to fix to a specific version when adding a Balena Cloud image to a Dockerfile (FROM bh.cr/maggie0002/balena-device-ui:0.0.1)? I had a tinker with some code over the weeks, which turned in to more than a tinker (as these things can often go). It will be significant, and likely more similar significant changes to come. Would be good if people could lock to a release to avoid breaking changes. Still going to push it of course, but if there isn't any versioning right now, will keep that in mind when pushing changes.

Might be nice to put together a GitHub repository template too for new projects. Both to kick off new projects, with the workflows added, but also for reference.

If still looking to play around, maybe better to have a nose around at the pending pull request: #80

from starter-interface.

I added the action, but at the moment it isn't working with the on tag workflow on this repo. Added an issue for it here: balena-io/deploy-to-balena-action#153

In the meantime I have done a manual push.

from starter-interface.