[X] Fix update-develop only got changes in package.py
[X] Add .zip from source
[X] Discuss develop version bumping
[ ] Create first workflow release
Is there an existing issue for this?
[X] I have searched the existing issues.
Please describe the feature you have in mind and explain what the current shortcomings are?
Since release are curretnly created completly manual a release trigger workflow is in development.
Right not it looks pretty much like the scope of implementing all the requests and ideas at once is just too big since it's still not finished.
It would make sense to strip out some of the still buggy behavior, release a basic version to test the whole infrastructure on github first. See if adjustements are needed rgiht away.
Afterwards move on to a rolling release cycle to update the feature set step by step while the general structure for roll outs is in place already.
How would you imagine the implementation of the feature?
Features for the Basic version
Query GitHub release information
Increment version
Update tag
Merge to main
Build from main
Update develop
Create release
verify release (based on tag)
Missing features for basic version
Query PR information
Convert PR information to usable strings
Include PR information in release
Implement PR format check workflow
Are there any labels you wish to add?
[X] I have added the relevant labels to the feature request.
Describe alternatives you've considered:
No response
Additional context:
Developing such complex automations in one go doesn't seem so usefull since adjsutements will be neccessary down th eline anyway.
A rolling release just makes way more sense here.
Checklist
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
Since release are curretnly created completly manual a release trigger workflow is in development. Right not it looks pretty much like the scope of implementing all the requests and ideas at once is just too big since it's still not finished.
It would make sense to strip out some of the still buggy behavior, release a basic version to test the whole infrastructure on github first. See if adjustements are needed rgiht away. Afterwards move on to a rolling release cycle to update the feature set step by step while the general structure for roll outs is in place already.
How would you imagine the implementation of the feature?
Features for the Basic version
Missing features for basic version
Are there any labels you wish to add?
Describe alternatives you've considered:
No response
Additional context:
Developing such complex automations in one go doesn't seem so usefull since adjsutements will be neccessary down th eline anyway. A rolling release just makes way more sense here.