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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Based on user feedback from the Slack conversation, improve the module creation and management documentation to clarify two critical requirements for GitHub Actions cloud build:
Tag Format Requirements: Make it explicit that release tags must follow the exact pattern [0-9]+.[0-9]+.[0-9]+ (semantic versioning with exactly 3 numbers separated by periods), not just "don't prepend with v". Users were confused when tags like "0.1" didn't trigger builds.
2. Required viam module update Step: Document that users must run viam module update before cloud build will work, as this was causing build failures with the error "you must update the module with viam module update before starting a cloud build".
These clarifications will help users avoid common pitfalls when setting up automated module builds and provide better troubleshooting guidance when builds don't trigger as expected.
If you want Promptless to make further changes on this PR, feel free to leave a comment tagging Promptless (It won't show up in the user drop down but Promptless will get it!)
1 paths audited Performance: 50 (no change from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 92 (no change from production) PWA: 70 (no change from production) View the detailed breakdown and full score reports
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. 1 out of 2 committers have signed the CLA.
✅ JessamyT ❌ promptless[bot] You have signed the CLA already but the status is still pending? Let us recheck it.
Just a reminder: If you'd like me to act on any feedback you have via Github comments, just type @Promptless in your suggestion and I'll get right on it! (I won't show up in the user dropdown, but I'll process any request that has @Promptless in the comment body.)
👋 Thanks for contributing! A reviewer will look at it on the next working day!
JessamyT
changed the title
docs: Clarify GitHub Actions cloud build requirements and troubleshooting
DOCS-4068: Clarify GitHub Actions version number requirements
Jun 5, 2025
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![promptless[bot]](https://avatars.githubusercontent.com/in/979718?s=60&v=4){kind=small}
JessamyT
changed the title
Based on user feedback from the Slack conversation, improve the module creation and management documentation to clarify two critical requirements for GitHub Actions cloud build:
[0-9]+.[0-9]+.[0-9]+(semantic versioning with exactly 3 numbers separated by periods), not just "don't prepend with v". Users were confused when tags like "0.1" didn't trigger builds.2. Requiredviam module updateStep: Document that users must runviam module updatebefore cloud build will work, as this was causing build failures with the error "you must update the module withviam module updatebefore starting a cloud build".These clarifications will help users avoid common pitfalls when setting up automated module builds and provide better troubleshooting guidance when builds don't trigger as expected.
Trigger Events
If you want Promptless to make further changes on this PR, feel free to leave a comment tagging Promptless (It won't show up in the user drop down but Promptless will get it!)