Automated Release Publishing

[ProjectHSI]

Note: For Triage, do not work on until decision is reached.

I'm just curious and putting this up for consideration. One of my projects is ProjectHSI/MobArena, which automatically publishes commits to GitHub releases.

I'm wondering if you approve of this idea or not.

Discussions could be better for this but discussions isn't enabled. It can enabled in the settings of the repository.

[nomadjimbob]

Moved to discussion

[ProjectHSI]

Even if we don't do the idea implemented in ProjectHSI/MobArena, I do recommend that we publish our releases to GitHub Releases.

[ProjectHSI]

i am getting an error.
awk: cmd. line:1: /^### refs/heads/feature/gh-actions/{flag=1; next} /^##/{flag=0} flag
awk: cmd. line:1: ^ syntax error

[nomadjimbob]

Can you paste the entire action so far and I’ll play with it

[ProjectHSI]

https://github.com/ProjectHSI/STEMCraft/blob/feature/gh-actions/extractReleaseNotes.sh

[nomadjimbob]

Looks like the current workflow in the main branch is now:

• Building the Jar using Mavin
• Extracting the version from release/x.y.z
• Pulling the content from the readme between the x.y.z heading and the next heading, removing empty spaces and adding that to the release notes
• Tagging main with the vX.Y.Z
• Attaching the built JAR to the release

[nomadjimbob]

The action has been updated to use newer action versions that no longer use depreciated components