Automate release process with a GitHub action

[Ebonsignori]

Adds the option for people who use this template to push version tags to automate (nearly) every part of a standard Obsidian release.

When pushing a valid tag, e.g. 1.2.3 this action:

1. Updates manifest.json, package.json, and package-lock.json with the version from the tag.
2. Commit the updates to your repo (that will need to be pulled down locally before making further changes).
3. Creates a new GitHub release for the tag.

[mwoz123]

Build output artifacts (main.js, manifest.json nor styles.css) doesn't seem to be available anywhere on github.

[wonderbird]

Does moving the release.yml file into the (new) folder .github/workflows/ resolve the issue you have in mind, @mwoz123 ?

See commits from Nov. 21 in my fork of the obsidian-sample-plugin and corresponding release 0.0.1 there and my pull request to @Ebonsignori 's fork

[mwoz123]

Could you make usage of this GH action on your your fork? to illustrate what it does - cause your fork doesn't have any tags ;)

[Ebonsignori]

You can see examples in these repos. All of the releases are auto generated by the action

• https://github.com/Ebonsignori/obsidian-at-symbol-linking/tags
• https://github.com/Ebonsignori/obsidian-auto-journal/tags

[mwoz123]

Is there a way to trigger it directly from GH UI? or it has to be done manually in the console by creating a tag and then pushing it to remote?

[Ebonsignori]

The workflow could be modified to accept a manual dispatch with the tag as the argument if you think this is a sufficient use case.

As it is I don't know that this PR will ever be merged so I might not put forth the effort to support this

[chaintng]

Hi @mwoz123 , I recently create a new MR to do the CI automated for release, bump version also

Can u check is it okay to merge ?

Thanks

MR: #124

[mwoz123]

@chaintng I'm not the owner of the repo nor GitHub DevOps expert.

@Ebonsignori asked me close my PR in favour of this, improved PR, so I agreed and put some comments here.