jMonkeyEngine / jMonkeyEngine/jme-testdata
Modify release logic
@jaime-jmebot is already working on this.
Since Sep 19, 2026.
- Dominant language
- GLSL
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Modify the release logic so that instead of triggering from github releases, it triggers from a manual dispatch for the github action workflow.
Upon dispatch the workflow should get the current data in YYYY-MM-DD format (it's YYYY = years, MM = month, DD = day) and uses it to push a new tag and github release with the same name. If there are multiple releases in the same day, it should append a counter as suffix.
eg. in a single day
- first release is: 2026-09-19
- second release is : 2026-09-19-2
- third release is: 2026-09-19-3
the next day the counter will reset from zero eg. - first release is: 2026-09-20
- second release is : 2026-09-20-2
and so on...
After the tag and github release are ready, the workflow will build and push the artifacts to maven central using the same YYYY-MM-DD value as version (remove the previous v* logic).
Maven central snapshots follow the same logic, but are triggered by commits
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.