Release config issues

[curtis-h]

Is this a regression?

No

Description

Description

There are some problems around our release process vs the release configuration.
As a process we are using release branches, but the tool (semantic-release) expects a specific setup that revolves around releasing from master.
This conflict adds required knowledge to the release process and can cause issues that slow down or even prevent a release.

Notes

The current setup allows us to release from any branch titled release/x.y.z - which works to some degree.
But the tool only allows there to be two of these branches, so after running a couple of releases you can't run another.
You also need to manually add tags, to enable the tool to derive the correct version number.

Ideas

• delete release branch on successful release
  • fix for the worst problem, but retains the custom process issue
  • quickest
• change process to release from master
  • introduces problems around releasing unwanted commits (why we moved to release branches)
  • quick
• change process & config to handle release differently (ie: RC on every merge)
  • new things = new problems
  • unknown = slow
• new tool to match release branches process
  • more unknown = more unknown

Please provide the exception or error you saw

https://github.com/hyperledger/identus-edge-agent-sdk-ts/actions/runs/11701614857/job/32588082474

Please provide the environment you discovered this bug in

No response

Anything else?

No response