Skip to content

Tags: simtsc/omnigent

Tags

v0.3.0

Toggle v0.3.0's commit message

Unverified

This tag is not signed, but one or more authors requires that any tag attributed to them is signed.
release: v0.3.0

v0.3.0rc1

Toggle v0.3.0rc1's commit message

Unverified

This tag is not signed, but one or more authors requires that any tag attributed to them is signed.
release: v0.3.0rc1

v0.2.0

Toggle v0.2.0's commit message
release: v0.2.0

Drop the rc suffix — promote the validated 0.2.0rc1 to the final 0.2.0 across
the three lockstep packages (versions + cross-pins + uv.lock).

Co-authored-by: Isaac

v0.2.0rc1

Toggle v0.2.0rc1's commit message
release: v0.2.0rc1

Bump the three lockstep packages (and their cross-pins + uv.lock) to the
0.2.0rc1 release candidate. Cut on release/v0.2.0; the final v0.2.0 will be
tagged on this same branch.

Co-authored-by: Isaac

v0.1.1

Toggle v0.1.1's commit message
release: v0.1.1

v0.1.1rc2

Toggle v0.1.1rc2's commit message
fix(oss): add READMEs to the SDK packages so twine check --strict pas…

…ses (omnigent-ai#201)

The secure-release pipeline runs `twine check --strict`, which failed
omnigent-client and omnigent-ui-sdk with "long_description missing" — the
core omnigent package sets readme = "README.md" but the two SDKs never
did. Add a README to each SDK and point `readme` at it (also gives them a
rendered PyPI page). Verified: twine check --strict PASSES for all four
SDK distributions.

Co-authored-by: Isaac
(cherry picked from commit b049d3a)

v0.1.1rc1

Toggle v0.1.1rc1's commit message
release: v0.1.1rc1

Bump all three packages + lockstep pins to 0.1.1rc1 to validate the
secure-publishing pipeline end-to-end against TestPyPI.

Co-authored-by: Isaac

v0.1.0

Toggle v0.1.0's commit message
Welcome to omnigent

v0.1.0rc4

Toggle v0.1.0rc4's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Sync 🌊: 8 upstream changes (omnigent-ai#8)

* Sync: re-export latest main (source + CI workflows)

* chore(oss): regenerate public lockfiles against public PyPI/npm

* chore(oss): regenerate public lockfiles against public PyPI/npm

* Add public uv config (P7D cooldown) + record span in uv.lock (test ahead of  internal omnigent-ai#3249)

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>