[CI] add GitHub Actions workflow for creating package releases

[flopez7]

Issue tracking

#3726

Context behind the change

Created a new GitHub Actions workflow that runs whenever a JS or Python package tag is pushed, checks if a GitHub Release already exists for that tag, and if not automatically creates one using softprops/action-gh-release with auto‑generated release notes from recent commits

How has this been tested?

Ran locally

Release plan

None

Potential risks; What to monitor; Rollback plan

None

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
human-app	Ready	Preview, Comment	Feb 3, 2026 0:26am
human-dashboard-frontend	Ready	Preview, Comment	Feb 3, 2026 0:26am
staking-dashboard	Ready	Preview, Comment	Feb 3, 2026 0:26am

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
faucet-frontend	Ignored	Preview	Feb 3, 2026 0:26am
faucet-server	Ignored	Preview	Feb 3, 2026 0:26am

[dnechay]

Codewise lgtm, just not sure about the release notes format.

By default it includes all PRs between version tags, which brings some unnecessary commits there (e.g. from HUMAN App or release PRs) and might bring confusion.

Generating good changelog might be tricky in this monorepo, so I suppose we can start either with release name in body or some custom message (e.g. link to diff between tags of specific package)

wdyt?

[portuu3]

Codewise lgtm, just not sure about the release notes format.

By default it includes all PRs between version tags, which brings some unnecessary commits there (e.g. from HUMAN App or release PRs) and might bring confusion.

Generating good changelog might be tricky in this monorepo, so I suppose we can start either with release name in body or some custom message (e.g. link to diff between tags of specific package)

wdyt?

We can write a changelog before changeset version and then use it here.
What do you think? @dnechay @flopez7

[dnechay]

@portuu3 taking into account that we prepare a version-release PR anyway that removes all changesets, crafting changelog file manually for each package won't be a big deal, but we can also try to enable automatic changelogs by changesets. Both work for me if we have separate changelogs that we can ref in action from this PR 👍🏻