chore(release): publish retroactive v0.1.0 tag to upstream

[akindoyinabraham0-collab]

Tracking issue for the upstream push of the retroactive v0.1.0 tag.

Background

PR #138 (chore/release-discipline-87 branch) introduces a release-checklist and a git-cliff configuration that align the api crate's version field in api/Cargo.toml with CHANGELOG.md. As a one-time cleanup aligned with that PR, an annotated v0.1.0 git tag has been created locally and pushed to the fork (akindoyinabraham0-collab/stellar-rwa-api-docs), pointing at commit bdaa8e38899ace47b42e92d6609f7489b949448e (docs: add CHANGELOG for the 0.1.0 release).

A direct git push upstream refs/tags/v0.1.0 from the fork's checkout returned HTTP 403 — the proposer (akindoyinabraham0-collab) has PR-creation rights on this repo but not tag-write or release-create.

What's needed

A maintainer with upstream tag-write on RWA-ToolKit/stellar-rwa-api-docs should run one of:

# Option A — minimal: just transfer the existing tag object
git push upstream refs/tags/v0.1.0

# Option B — transfer + cut a GitHub Release at the same time
git push upstream refs/tags/v0.1.0 && gh release create v0.1.0 \
  --repo RWA-ToolKit/stellar-rwa-api-docs \
  --target bdaa8e38899ace47b42e92d6609f7489b949448e \
  --title 'v0.1.0' \
  --notes-file <(sed -n '/## \[0.1.0\]/,/## \[/p' CHANGELOG.md | sed '$d')

The tag already carries the correct commit, message, and (annotated) metadata, so this is a one-shot ref transfer — not a code change.

Refs #87, #138.

[joyyakubu41]

@joyyakubu41 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I will like to work on this issue please

ℹ️ Repo Maintainers: To accept this application, review their application or assign @joyyakubu41 to this issue.

[willy-de7]

@willy-de7 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi Maintainer, can I solve this issue please

ℹ️ Repo Maintainers: To accept this application, review their application or assign @willy-de7 to this issue.